Berry: Getting individual sensor values to variables

[boozeman]

With 10.1.0.1 Berry Console I can command

somevar = tasmota.read_sensors() To get various sensor values to variable.

somevar
{"Time":"2021-12-09T17:49:37","ANALOG":{"A1":232},"BME280": {"Temperature":23.1,"Humidity":21.2,"DewPoint":-0.3,"Pressure":1013.6},"SHT3X":{"Temperature":20.0,"Humidity":25.0,"DewPoint":-0.7},"ESP32":{"Temperature":53.3},"PressureUnit":"hPa","TempUnit":"C"}

I want to get BME280 Pressure, SHT3X humidity and temperature to variables (for calculation of Equivalent sea level pressure, Absolute Humidity, Vapour Pressure Deficit, etc)

Do I have to mangle that somevar with example string.split(somevar,"whatever you want to use split")
Or is there any easier way to get those single sensor readings out?

Next step is to add extra values on the SENSOR or equivalent MQTT payload, but that's different story ;-)

For now those extras are generated with Home Assistant templating.

[sfromis]

Certainly no need for splitting....

import json
sensors=json.load(tasmota.read_sensors())
print(sensors['BME280']['Temperature'])

To add your own sensor data to the usual places for sensors (including MQTT), you can create a driver in berry, where you can have methods to create JSON data in exactly the same way as built-in sensors.

Note: If you set Altitude, Tasmota will automatically include SeaPressure when the sensor delivers Pressure.

[boozeman]

You are both right for this.

I managed to get it work. there's the link to gist GhData.be

Thanks for your help.

[s-hadinger]

Thanks for your contribution. Actually your class does not need to derive from Driver anymore. You can create a plain class instead with no superclass.

[barbudor]

I wonder if by doing this:

GhData = GhData()

you are not erasing the class itself.

@s-hadinger what's your opinion ?

[sfromis]

As I see it, that assignment does not "erase the class", but replacing the variable content it with an instance reference means that you can no longer directly refer to the class as such. With the class still in scope, no real loss.

You could also assign GhData to another variable and still have the class reference there, as name of the variable holding a class reference does not matter, outside of the circumstance that class creation by default also creates a variable with the same name as the class.

[s-hadinger]

If it's meant to create a singleton then it is a good way to do it. Although generally speaking I wouldn't recommended it, this is ok for a singleton.

The class still exists but is no more accessible through a global name. You can still get it with classof(GhData)