No, sqlite is never needed to do dzvents actions.
You probably need an Domoticz json API param=graph call to get the history data https://wiki.domoticz.com/Domoticz_API/ ... 7s#History
From that data you can calculate the trend with dzvents/lua. There will probably be Lua functions for that.

I believe it is calculated by the highcharts graph module on the webgui part. So not available in dzvents.
You could ofcourse have dzvents calculate a trend based on the values in the database.

And there is only 1 device named Batterie_SOC?

When airco is off measure energy usage of airco? Trigger is only on airco device not on time. So monthly COP calculation will most likely be shipped. Or you send data at least every minute to the airco device..... The estimated heat transfer calculations as base for the COP seems to be a joke, at ...

Indeed as expected... Why not use a setpoint device as I proposed here earlier? Then also in a normal Domoticz Gui this will work.
https://wiki.domoticz.com/Dummy_for_vir ... t_Setpoint

Disable the info logging for an hardware gateway (like a python plugin) is done in the hardware gateway settings. There are 3 setting switches available for showing info, status and/or error logging per gateway.

If you are new to scripting please dig into Dzvents...
Curl is done with openURL() and asynchronous so it will not interfere with other threads.

How do you control your KAKU devices? What Domoticz Hardware gateway is used?


If your KAKU devices are zigbee devices you could consider to get rid of the KAKU bridge and use an open source Zigbee gateway.

Is a Dial in Dashticz not a rotating knob for Dimmers and Thermostats/Setpoints? Setting a Domoticz dummy Setpoint device to min 1 and max 24, step 1, UOM hours should give you a rotating knob in Dashticz with 1-24 (and do not use subtype "updown" in Dasticz block). https://dashticz.readthedocs.io ...

Setup a dummy incremental counter, change the parameters as desired and run a script, both are discussed in the following topic

viewtopic.php?t=27776

In Domoticz the setpoint (thermostat) device is now configurable in min/max, step size and Unit of Measure.

With Dzvents you can use idx too, instead of domoticz.devices('My Device') use domoticz.devices(123) I would not recommend python for event scripting. The community for Dzvents in Domoticz is way bigger. Dzvents is not that hard. Just try the examples on the forum and read the extended wiki: https ...

If you plan to use other MQTT hardware gateways then you can use Zigbee2MQTT with Domoticz MQTT AD gateway. It is the most used Zigbee gateway. If you do not need or want an extra MQTT layer you can use the Zigbee4Domoticz Python plugin. But I see you are also going to use Zwave-JS-UI with MQTT AD ...

This is an Husqvarna mowers plugin but Gardena seems to use something similar. viewtopic.php?t=39624

Perhaps use
local BAT =
This to be sure it does not get mixed up with another BAT value.

And you update every 5 minutes from the batterie but sends it to display every minutes.
It could be it is a timing issue as the updates from batterie is just milliseconds after the sending to display.

Normally you have to set it in the file
/etc/init.d/domoticz.sh
And restart the Domoticz service.

Ah, I see now that the device type is "Thermostat Mode" and "Thermostat Fan Mode". I never heard of this device type. Probably related to the old OpenZwave integration. So Indeed a good option to use these instead of the normal selector switches. I dont know if these easily can be made usable for ...

For Domoticz it are switches and put into the Switch/lights tab. This is hardcoded and needs major rework to change.

Try building on the development sources, there the fix has been done: https://www.mysensors.org/download
By the way, the website is online again.....

Googling will solve the issue: https://github.com/mysensors/MySensors/issues/1431