Argh, you're right. My browser cache fooled me. Still, Alexa is able to authenticate using basic-auth with my setup.

To harden security I'm running an Apache reverse proxy on the same server that runs Domoticz. I'm using a subdomain (az.<mydomain.nl>) that can only be accessed by Alexa (amazonaws.com) using https and is proxied to Domoticz (port 8088) using http on the local network. Besides I'm running fail2ban ...

Used Alexicz 3 hours ago to switch off my home office heater and audio amplifier. Worked fine.

I'm in the same boat. Have been using Controlicz since the early days with great satisfaction. I've followed the excellent Alexicz Howto (R3 version) but noticed that one important instruction was missing (change the Lambda handler function to lambda.event_handler). After the handler change it works ...

I would like to upload my weather station data to OpenWeather using openURL postData but I wonder if this is possible with the OpenWeather API where square brackets are used. The following example works when using curl: curl -X POST -H "Content-Type: application/json" http://api.openweathermap.org ...

Recent versions of the Hue Bridge firmware are exposing a new API version for the Hue system. The API v2 does support "push" style notifications for every change in the system, without the need for polling the Bridge.

Any plans to support this with Domoticz?

Can you remove the semi-colon on the line "sValue: ;value" in the file device_types.yml and restart domoticz?
Or try: sValue: value;

JS interpreted code as a plugin being more responsive than OZW compiled/native in domoticz raise some questions: Migration to zwavejs needed a full rebuild of your zwave network (exclusion/reinclusion of all modules) I presume? Maybe doing so at once resulted in a better topology than adding ...

All my Z-wave devices are now working smoothly with zwavejs2mqtt, mosquitto broker and the ZWave-MQTT-plugin. Performance is much better, especially when switching multiple devices at once. I was already looking for an alternative home automation solution but dzVents and many other good things of ...

Got it working. Previously I've overlooked that I had to add the sensor type after state (/0 general purpose alarm): I've added this to devices_types.yml /156/: state/0: DeviceType: 244 Enabled: true Primary_device: true SubType: 62 SwitchType: 8 Type: DeviceType nValue: 1 sValue: OnOff

If I publish the same topic with exactly the same payload using a modified version of the tools/mqtt-device utility it works fine. What could be the difference with zwavejs2mqtt? publish.single( "zwave/10/156/0/state", payload='{"time":1629554437529,"value":true,"nodeName":"MS Overloop ...

I have a couple of Fibaro FGMS001 motion sensors with older firmware version 2.6 that still use the deprecated Alarm Sensor Command Class (/156) to send a tamper alarm. If I trigger the tamper alarm I see the following MQTT messages: zwave/10/156/0/state/0 {"time":1629475609629,"value":true ...

If Domoticz registers this device as a separate dimmer (/38) and switch (/37) you will not be able to use them as a single devicename (dimmer) in dzVents. Use the names as you gave to each of them.

Instead of the bundled mqtt-snooper you can use mosquitto_sub which supports username/password :

mosquitto_sub -h <host-ip> -q 1 -v -u <username> -P <password> -t zwave/#

It works when assigning "nValue : value" in the devices_types.yml file. I've kept "sValue : value" but don't know if that is needed. Where would I find this kind of domoticz device requirements (which Type, SubType, value field to use, etc.)? Screenshot from 2021-08-17 19-19-40.png

CO2 device is added but it does not communicate the value in PPM to Domoticz when using the correct type "Air Quality". If I change the type to "Usage" or "Illuminance" the value is communicated to the Domoticz UI correctly. device_types.yml Carbon_dioxide_CO_level: Enabled: true Primary_device ...

Thanks. Sure, I will create a pull request after some decent testing to not break the solid base

CO2 is also recognized. Just wondering why all my previously excluded nodes ( /28, /32, /33) are still being send through zwavejs2mqtt? In the Control Panel they are not present any more.

Got it working. In api/devices.py I've added " or val == "8" elif typedef["sValue"] == "OnOff": val = str(payload["value"]) if val == "True" or val == "22" or val == "8": sValue = "On" nValue = 1 else: sValue = "Off" nValue = 0 I think this code should be more generic following the rule: # sValue ...

@heggink, I did as you suggested. The devices are added when a motion is triggered but no motion events are passed on to Domoticz. The "Last Seen" gets never updated. I tried changing SubType from 62 to 73 but that did not help. Below the logs when a motion starts and ends after 10 seconds. Notice ...

Thanks @heggink, Will further investigate how to modify device_types.yml when I have more time and contribute if I'm succesfull. If I set the zwavejs2mqtt log level to Debug I see this: 2021-08-16 13:18:20.730 DEBUG MQTT: Publishing to zwave/31/113/0/Home_Security/Motion_sensor_status: { time ...