CRASH|DOWN

Eigentlich für mich selbst aber vieleicht findet jemande eine Inspiration darin;

Gipfel	Datum	Kommentar
Heuberg / Wasserwand (1338m)	13.04.2017 31.12.2022
Soinwand (1756m)	10.07.2021
Hirschberg (1668m)	2017/18?
Wildalpjoch (1720m)	10.07.2021
Seewandköpfl (1664m)	10.07.2021
Kesselwand (1721m)	10.07.2021
Lacherspitz	todo
Brecherpitze	16.05.2020 12.09.2019
Blomberg	21.08.2022 11.04.2021 09.06.2018 01.04.2016 30.03.2014
Roßstein / Buchstein	10.07.2018
Rotwandkopf	14.06.2017 04.08.2019 16.07.2022
Wendelstein (1838m)	31.05.2021
Breitenstein (1622m) + Fensterl	01.10.2021
Käserwand Wildalpjoch Seewandköpfl Lacherspitze Bärenstein	10.07.2021
Rohnberg /Schliersberg	30.12.2016
Taubenstein	14.06.2017 04.08.2019
Stümpfling	todo
Wallberg (1722m)	todo
Baumgartenscheid	01.06.2014 31.12.2021
Kreuzbergköpfl	01.06.2014
Gindelamlschneid	01.06.2014
Hochries (1569m)	03.05.2021
Farrenpoint	06.2020
Rampoldplatte	20.07.2020 01.06.2022
Hochsalwand	01.06.2022
Reehleitenkopf	26.05.2021
Kirchspitze (2312m /AT)	29.08.2017
Isskogel (2263m /AT)	21.08.2017 23.08.2017
Kreuzjoch (2558m /AT)	24.08.2017
Riesenkopf	26.06.2021
Zugspitze	20.10.2012
Höllental Anger Hütte	02.10.2021 16.07.2017 16.08.2016 20.10.2012	(von Eibsee über Riffelscharte)
Wank	21.08.2015
Kreuzeck	16.07.2017 28.09.2013
Eckbauer	21.06.2015
Osterfelderkopf	16.07.2017 28.09.2013
Eichenberg	27.05.2017
Brocken	28.05.2016
Bärenkopf (1991m / AT)	todo
Hinterunnütz / Hochunnütz / Vorderunnütz (2007m /2075m / 2078m)	todo
Dalfazer Joch (2233m)	todo
Seekarspitze (2053m)	todo
Ehrenbachhöhe (1802m)	06.09.2010
Hahnenkamm (1712m)	07.09.2008 06.09.2010
Walmendinger Horn (1996m)	09.09.2011 1.10.2012
Söllereck (1706m)	10.09.2011 2.10.2012
Hoher-Ifen (2230m)	3.10.2012
Nebelhorn (2224m)	11.10.2011 4.10.2012
Brünnstein	todo
Hochgern	04.03.2023
Spitzstein	13.07.2022 20.02.2023
Jägerkamp	28.07.2022
Guffert	03.07.2022
Hochalm	25.08.2022
Lamsenjoch Hütte (über Faule Eng)	12.09.2022
Gedererwand	19.09.2022
Taubenberg	07.10.2022
Kampenwand	25.06.2022
Herzogstand	30.10.2021

Today i´ve reactivated my VS Code + PlatformIO setup to create new binary of Tasmota with the actual releas 9.5.0.1 2022.01.1 for my AHT10 Sensors and the MAX44009 Lux Sensors i use in some devices.

I started first by updating all regular devices with normal and sensors firmware and while only 4 devices was left i decide to give them also an all new version.

So pulled the new version from github, update the platformIO plugins, chang the 3 lines of code i also showed in a previous post and run the build.

And here it is the all new Tasmota 9.5.0.1 2022.01.1 binary with AHT10 and MAX44009 included.
Already tested on some Wemos D1 Mini.

Build with framework-arduinoespressif8266@2.7.4+9

https://github.com/crashdown79/tasmota-aht10/blob/main/tasmota.bin

https://github.com/crashdown79/tasmota-aht10/blob/main/tasmota.bin.gz

Hope you enjoy it and don´t forget to visit original Tasmota site and donate to https://github.com/arendst

Updated due to new version 2022.01.1 which is used now.

;-)

Today i want to share my way how i monitor my Mosquitto MQTT Broker.

The change function:

What topic is for what: https://mosquitto.org/man/mosquitto-8.html

The Output of this function i forward direct in a influxdb object:

This results in a new measurement table in influx:

The Result in my Grafana Dashboard:

If you´ve questions or want to comment on one of my project please contact me on twitter: https://twitter.com/jarodw79

Starting with the flow…

Prerequisits:

I assume that you´ve already installed node-red and connected it with your influxdb.
You should also have installed tasmota on your device. I´ve a Tuya device flashed with a actual Tasmota version by tuya-convert

I´ve used a Gosund SP111 for this, but you can basicaly use it with every device giving you SENSOR data. So it doesn´t matter whether you want to monitor temperature, gas, energy or other. You´ve just adapt where i used the $..ENERGY by chosing what ever your sensor provides. Other examples i use are „$..Illuminance“, „$..Pressure“, „$..Pressure“ and „$..Temperature“

Used elements:

• MQTT in

With the MQTT in i subscribe to tele/+/SENSOR which is the default topic of tasmota for sensor values, here i make no selection what sensor values i will use so it gets every sensor type you have in your mqtt network

• JSONPath -> node-red-contrib-jsonpath

Here i use the JSONPath expression „$..ENERGY“ to filter only on JSON messages which includes ENERGY as a element.

• Switch

I use the switch element to identifiy whether the supplyed element from JSONPath is empty or not.

• Function

The function is where i add the source name within the JSON String to have that information afterwards available also in the influx measurements.

• InfluxDB

After all i write the whole string in the influxDB in my statisitcs database in a measuremnt called „energy1“

• DebugMsg

The DebugMsg element is to controll the output of the chain. In my environemnt this is a typical output:

[{„TotalStartTime“:“2020-05-21T19:09:01″,“Total“:1.591,“Yesterday“:0.208,“Today“:0.054,“Period“:0,“Power“:0,“ApparentPower“:17,“ReactivePower“:17,“Factor“:0.02,“Voltage“:228,“Current“:0.073″,“Name“:“energy2″}]

As you see there is the NAME added at the end of the object.

CODE:

[
{
„id“: „3a60f610.f66632“,
„type“: „jsonpath“,
„z“: „2c0c97dc.300d7“,
„expression“: „$..ENERGY“,
„split“: false,
„name“: „“,
„x“: 630,
„y“: 2080,
„wires“: [
[
„d5a418c2.d9bda8“
]
]
},
{
„id“: „d5a418c2.d9bda8“,
„type“: „switch“,
„z“: „2c0c97dc.300d7“,
„name“: „“,
„property“: „payload“,
„propertyType“: „msg“,
„rules“: [
{
„t“: „nempty“
},
{
„t“: „cont“,
„v“: „topic“,
„vt“: „msg“
},
{
„t“: „else“
}
],
„checkall“: „true“,
„repair“: false,
„outputs“: 3,
„x“: 790,
„y“: 2080,
„wires“: [
[
„e78d6b7c.6767c“
],
[],
[]
]
},
{
„id“: „e78d6b7c.6767c“,
„type“: „function“,
„z“: „2c0c97dc.300d7“,
„name“: „add name“,
„func“: „msg.payload[0].emname = msg.topic.split(\“/\“)[1];\nmsg.payload[0].Name = msg.topic.split(\“/\“)[1];\n\nreturn msg;“,
„outputs“: 1,
„noerr“: 0,
„x“: 940,
„y“: 2080,
„wires“: [
[
„76d65968.6c1568“,
„a78d055d.d1ea3“
]
]
},
{
„id“: „76d65968.6c1568“,
„type“: „influxdb out“,
„z“: „2c0c97dc.300d7“,
„influxdb“: „306f62ed.836df6“,
„name“: „Statistics“,
„measurement“: „energy1“,
„precision“: „“,
„retentionPolicy“: „“,
„x“: 1140,
„y“: 2080,
„wires“: []
},
{
„id“: „a78d055d.d1ea3“,
„type“: „debug“,
„z“: „2c0c97dc.300d7“,
„name“: „energy.raw“,
„active“: false,
„tosidebar“: true,
„console“: false,
„tostatus“: false,
„complete“: „true“,
„targetType“: „full“,
„x“: 1150,
„y“: 2040,
„wires“: []
},
{
„id“: „306f62ed.836df6“,
„type“: „influxdb“,
„z“: „“,
„hostname“: „influxdb“,
„port“: „8086“,
„protocol“: „http“,
„database“: „statistics“,
„name“: „“,
„usetls“: false,
„tls“: „“
}
]

Actual there are plenty of tutorials for thousands of sensors in IoT environment.
Due to the fact i´ve never found one for the AHT10 Sensor with Tasmota, i wrote one to share my experience with you.

Hardware preparation:

Connect AHT10 Sensor with the Wemos D1

Sensor – Wemos [color]
VIN – 3.3 V
GND – GND
SCL – D1 (GPIO5)
SDA – D2 (GPIO4)

---

I will directly jump to the specific task to activate the AHT10 Sensor in Tasmota.

I expect you have already installed and configured Arduino IDE oder platformIO

download Tasmota: https://github.com/arendst/Tasmota/archive/development.zip

Extract the ZIP file and open tasmota.ino in Arduino or platformIO  

Next is valid for acutal Tasmota 8.2.0.x
[Optional] Edit config:  my_user_config.h to have your wifi environment and mqtt setting directly set in the binary. If you don´t want to configure it here you can do it with a laptop or mobiel via the integrated wifi manager after booting the esp8266 the first time.

– set wifi settings
– set mqtt settings

Uncomment my_user_config.h line 496 to activate the AHT10 Sensor

Comment the following lines in the my_user_config.h out to prevent device drivers with the same ID 0x38 being active the same time.  

Now you can compile and transfer tasmota to your esp8266

Connect to Tasmota Page of device with http by typing the IP in your Browser:
– choose: Configuration
– than choose: Configure Module
– Module Type -> Generic
– Select SDA and SCL IO from the list
– D2 GPIO4 –> I2C SDA (6) 
– D1 GPIO5 –> I2C SCL (5)

Now if you reboot your Wemos you should see actual measurements.

If your settings are correct you should also get the measurements on mqtt if activated.
So you can use your newly installed AHT10 sensor in your smart home environment.