Triggered Blocky events clogg system Topic is solved

[joostvanderlinde]

I prefer to use Blocky events as long as what I want to acgieve is do-able in blocky....
This weekend I noticed some unexpected behaviour:
I have a virtual switch that (when Ón, used to register if there is anyone 'in the room') should enable switching on/off a heater based on a Thermostat Setpoint.
The switch that controls the heater is a Sonoff/Tasmota switch connected to Domoticz via MQTT

Blocky.png (42.06 KiB) Viewed 1512 times

Nothing soecial I think.
I have the blocky triggered on 'Device'
But as some of the devices in my setup (at least a Mitsubishi AircoWithMe ) sends a status update more than once a minute (with all variables) my Blocky seems to be triggered so much (more than once a second!!) that the flow between MQTT and Domoticz get clogged so much that it takes quite a while before ANY command via MQTT is actually effectuated. Also, my logfiles become sluggish . . .

Screenshot from 2023-12-18 13-58-12.png (258.03 KiB) Viewed 1511 times

When I disdable my blocky event after some time everything came back to a normal state and command effectuation was back to nomal again.

Probably limiting the frequency of status updates of the Airco should be limited, but I do not see how to do that.

But can´t I configure stuff in a way that my event is only triggered by specific devices (in my case a temperature change and/or the virtual switch) status change (instead of 'a status change of any device')?[

[waltervl]

If you want to keep using blockly you have to slow down device updates from other hardware. Normally there are polling time parameters in the hardware setup.

Device triggers on specific devices is implemented in DzVents.

[joostvanderlinde]

Thx for clarifying and advice !
I think I just have to drop my general approach here and do more in dzVents because it simply is capable of doing more things and doing thins better....

[solarboy]

Thx for clarifying and advice !
I think I just have to drop my general approach here and do more in dzVents because it simply is capable of doing more things and doing thins better....

Dzvents is much better but would suffer the same issue with that hardware as it is. What I do in a situation when you cannot change the polling time of the hardware (for example at one point my APC UPS hardware had this issue) , is to create a much smaller streamlined script that checks for changes and then only triggers the main script if there is a change.