Domoticz 2024.4 MQTT Auto Discover not processing the jinja2 value_template. I have the following MQTT AD topic: domoticz/sensor/openevse/temperature/config With the value: { "value_template": "{{ float(value) / 10.0 }}", "unit_of_measurement": "°C", "state_class": "measurement", "device_class" ...

Domoticz MQTT Push will only push integer value of dummy voltage device with decimal value. In 2024.4 this function is only pushing the integer value of a Dummy Voltage device: As viewed from MQTT explorer: Topic Domoticz_Push/329/state Domoticz_Push 329 state = {"voltage":245} Value of device in ...

Counters clearly do support decimals and even the daily display shows decimals yet the decimals for the daily display are just shown as zeros (instead of the actual decimals). See below. Counter.jpg I understand if the value is scaled up by 1000 and then a divisor of 1000 is used then the display ...

In case someone else is looking to get their Auto mode thermostat working as described in this post. Follow the instructions above to add the cooling setpoint config topic and then use the following climate HASS Device JSON in z-wave-js-ui so the heating setpoint does not change when the thermostat ...

With z-wave-js-ui 9.12.0 changing the HASS Device JSON seems to be more consistent now. If you update the JSON then press the Update button then press the STORE button it seems to keep the changes now. Then you can press the Rediscover button and it will update the config topic in MQTT. Also I ...

Summer is finally here and I needed to get this working so after a lot of messing around, this is what I have come up with as a work around until the Domoticz MQTT-AD is fixed. (I wouldn't hold my breath on that as I opened an issue on this but the response was "Domoticz has no issues". Even though ...

2024 and this Z-Wave-JS-UI to Domoticz integration is still broken for many devices including climate and fan devices. Seems like the issue is on both sides as even OpenZwave thermostat setpoint devices are now broken in Domoticz 2024.4. I've been trying to figure it out in the limited time I have ...

What is the best way to store a persistent Date and Time? local Time = require('Time') return { on = { devices = { DEVICE_TEST_EVENT }, }, data = { persistentTimeObject = { initial = Time()}, -- domoticz.time does not work here use Time() which Needs local Time = require('Time') persistentDateTime ...

Well looks like thermostats in general are just broke in Domoticz now (ver 2024.4). I tried going back to OpenZWave and adding thermostats back to OpenZWave and it does not create any (heating or cooling) setpoints. This used to work just fine in older versions of Domoitcz for years. Now I can't ...

Yeah I had found those already looking for solutions. That is one of the places I got the JSON examples to add the fan mode but as I said before Domoitcz still doesn't create a device for the fan mode. Even if it did there is no Cooling setpoint and no current operating state. So not usable. At this ...

Thanks I will, but I was hoping to find a more immediate solution. Which is probably just buying a Z-Wave Thermostat that actually works. I just need to know of one that does (if there are any). So if anyone has a working Z-Wave Thermostat that works with Z-waveJSUI and Domotocz 2024.4 Please let me ...

Has anyone found and solution to ZwaveJSUI not creating all the thermostat devices in Domoticz? I migrated to ZwaveJSUI from OZW and with OZW everything worked correctly but with ZwaveJSUI most of the critical thermostat devices are missing. With ZTS-110 Thermostats only the Heating Setpoint, Mode ...

Looks like somewhere between 2024.1 and 2024.4 the Domoticz Device Sharing protocol was changed. As of 2024.1 Device sharing was working to versions as far back as 2021.1. But now device sharing produces the following error on the remote Domoitcz: Error: UNHANDLED PACKET TYPE: FS20 49 Updating the ...

I am running a Domoticz system in a Proxmox LXC and was running Z-wave JS UI V8.24.0 with no issues with the Z-Stick Gen5+ however when I tied to upgrade to V9.6.2 it would fail to open the serial port. I finally noticed that it did seem to open the port the first time but began to fail to open the ...

I see this thread seems to have diverged from the initial question. "Determine if switch was physically pressed or controlled by Domoticz". If you look at the log of a device the last column is titled User and you can see what "User" is associated with each device event. If dzVents then the User is ...

I second the request for dz.emitEvent('myEvent').cancelQueuedCommands()

Any of the workarounds are just way more complex and complex = mistakes. Simple is good. Thanks for emitEvent, now if it can be improved that would be even better.

Bumping this thread to see if there has been any progress on Elk M1 Gold panel integration with Domoticz. Usually this is done by a plugin for the host system (Domoticz in this case) that then communicates to the Elk (via a IP socket) which has a protocol that provides status updates on sensors and ...