No, this is type General, Percentage. It is actually the charge % for mye EV.
But I observe the same behavior for type Temp, LaCrosseTX3 and for type General, Custom Sensor.
I think this comes from a global setting, but can't find which setting.
Which setting determine the Y range in a graph? I have two different domoticz servers, one is showing the daily graph of temperature and percentage with the lower Y value determined by the min value of the data whereas the other always is relative to 0 (zero).
Idea for plugin enhancement: This plugin gives a vast number of devices, some of them will be of no interest for all users. Would be nice to have options in the setup to select the different APIs available.
Besides, links in Features in README.md needs updates :)
Idea for plugin enhancement:
This plugin gives a vast number of devices, some of them will be of no interest for all users. Would be nice to have options in the setup to select the different APIs available.
Besides, links in Features in README.md needs updates
I made a workaround, by choosing another mqtt option (raw) in the power probe, doing some processing in node-red, and setting up virtual devices in Domoticz.
Thanks for giving all these details.
In the value field for in the events view I can only see two values (picture)
Maybe the home assistant auto discovery is not the best thing to do here. Seems to be some mismatch between the received mqtt and what Domoticz is expecting.
The actual sensor is a power probe, reporting power consumption in my home. I use home assistant autodiscovery in Domoticz to get the sensors into Domoticz. The problem is with the Utility widget showing a different value from that in the device view (se pictures).