In the next beta version (currently building) support has been added for the KMTronic temperature sensors. https://github.com/domoticz/domoticz/commit/ce44a1735e16f9f2790868b94e016e0ba68bc830 Not sure why people are going very complicated with complex scripts while implementing this took less then 5...

@ash77, not sure i understand, but m_events (or the database is easier to check) is correct looking at your actions You configured 4 actions (no complicated else stuff), and 4 actions are created and will be checked. No need to know it is from A or B Unless you meand that 2. condition: temp>26 was a...

Thanks, this makes sense! This patch could be accepted, as all will happen in the first IF, and it should not even go to the ELSE because the above is true. But, there can be more conditions then one if (A=1 and B=2) then ... else if (A=2 and B=1) then ... else if (A=2 and B=2) then ... else .. will...

Best to test this solution first locally... But i don't think this is the fix unfortunately, and it's the way it was designed/implemented years ago. The OP from this topic also created a github issue where i try to explain how to overcome (his/some) this issue: https://github.com/domoticz/domoticz/i...

But if you are the creator of this meter, you could always send an increasing value, so this will solve your actual meter issue ?
Just saying, it might be better to solve the hardware, then to conceal the error with frontend software.
At least, now you know for sure when things go wrong

So basically you are saying, with this patch, you do not have spikes, and all looks normal, and you have/had no idea your counter device is faulty and produces errors?
Then we should not apply this patch otherwise nobody will notice this behavior ?

Obviously a reliable counter will not take steps backwards. But if that ever happens, in my opinion reporting a negative delta is closer to truth than overflowing to billions or discarding correct data. No of course not, but it should be shown... you want to know that you have a fault counter If ne...

At the moment there is no method that is being called when a uservariable has changed, only when new sensor/device data is received. mainworker::sOnDeviceReceived MQTT::on_connect, sOnDeviceReceived.connect(boost::bind(&MQTT::SendDeviceInfo, this, _1, _2, _3, _4)); This needs to be implemted in the ...

This all can be done without scripting and using a scene In the scene you can specify delays Also how i use it, first turn on the bedroom light, next turn off all ground floor lights one by one (with a delay) the one closest to the stair last If you do not trust your RF then you better connect a goo...