Domoticz

Did you restart the Zwave-JS-UI container as indicated in the manual?
Else share your findings in the forum of Zwave-JS-UI https://github.com/zwave-js/zwave-js-ui/discussions

Hello,

I managed to sort out the issue.

I do not check the HTTPS feature in Zwave JS UI general settings.

1 - I created a new proxi location in the nginx sites available configuration Mysite.tld by adding
location /zwave/ {
proxy_pass http://192.168.0.112:8091/;
}

2 - then created a new template Zwave.html in /home/pi/domoticz/www/templates

<iframe id="Zwave"style="width:100%;height:800px;overflow:scroll;">
</iframe>

<script>
document.getElementById('Zwave').src = "https://mydomain" + "/zwave/";
</script>

3 - and finally created a port redirection on my router for the port 8091

I can now access to Zwave JS UI remotely via https://mydomain/zwave/

BR

meal wrote: ↑Sunday 10 September 2023 23:13 Hello,

I can now access to Zwave JS UI remotely via https://mydomain/zwave/

BR

Ah, that is not what you asked before.
For using the ZWave UI behind a proxy see also https://zwave-js.github.io/zwave-js-ui/ ... erse-proxy

But I am glad you have figured it out yourself.

Hello,

Formerly when using openzwave I used the JSON API /json.htm?type=openzwavenodes&idx=MYZWAVEID to collect the status of the ZWAVE devices (Dead, Ready, ...) and notify a message whenever a device is dead or ready again

Does anyone have a hint to get the status of Zwave devices from ZWave JS UI ?

BR

meal wrote: ↑Monday 11 September 2023 9:56 Hello,

Formerly when using openzwave I used the JSON API /json.htm?type=openzwavenodes&idx=MYZWAVEID to collect the status of the ZWAVE devices (Dead, Ready, ...) and notify a message whenever a device is dead or ready again

Does anyone have a hint to get the status of Zwave devices from ZWave JS UI ?

BR

You can see them in MQTT https://zwave-js.github.io/zwave-js-ui/ ... ode-status

Hello,

@waltervl : Where could I find an example of accessing MQTT via python 3 ?

Many thanks in advance
BR

meal wrote: ↑Monday 11 September 2023 16:49 Hello,

@waltervl : Where could I find an example of accessing MQTT via python 3 ?

Many thanks in advance
BR

I think google "accessing MQTT via python" will do

Hello,
@waltervl : I came across the web site http://www.steves-internet-guide.com/in ... on-client/

Context:
MQTT GAteway prefix : zwave
MQTT Name : zwave-js-ui

I wrote a simple python script to get the MQTT info using api getInfo :

import paho.mqtt.client as mqtt #import the client
import time

def on_message(client, userdata, message):
print("message received " ,str(message.payload.decode("utf-8")))
print("message topic=",message.topic)
print("message qos=",message.qos)
print("message retain flag=",message.retain)

def on_publish(client,userdata,result): #create function for callback
print("begin data published \n")
print(result)
print("end data published \n")

def on_disconnect(client, userdata, rc):
print("client disconnected ok")

def on_log(client, userdata, level, buf):
print("log: ",buf)


broker_address="192.168.0.112"
client = mqtt.Client("zwave") #create new instance
client.on_publish = on_publish #assign function to callback
client.on_disconnect = on_disconnect
client.on_log=on_log
client.on_message=on_message #attach function to callback
client.connect(broker_address,1883) #connect to broker
publish_result=client.publish("zwave/_CLIENTS/ZWAVE_GATEWAY-zwave-js-ui/api/getInfo/set","payload")
print(publish_result.rc)
print(publish_result.is_published())
publish_result.wait_for_publish()
print(publish_result.is_published())

I do not get the Gatevay info and get stuck in the line publish_result.wait_for_publish()

Has anyone developed a python script to access to zwave-js-ui via MQTT or could help me ?

BR

meal wrote: ↑Tuesday 12 September 2023 6:45 Hello,
@waltervl : I came across the web site http://www.steves-internet-guide.com/in ... on-client/

I wrote a simple python script to get the MQTT info using api getInfo :


Has anyone developed a python script to access to zwave-js-ui via MQTT or could help me ?

BR

I think you better start a new topic for this else it will disappear in the mist of this big topic.
Next to that, please put code into code brackets as that will read much easier. app.php/help/bbcode#f2r1

d3smo wrote: ↑Thursday 01 June 2023 16:00

thomasbaetge wrote: ↑Thursday 01 June 2023 12:54 Your stick can connect to one instance at a time only.
So while OZW is running, zwJS can not access it (and vice versa)

I've try disable OZW in Domoticz devices and stop domoticz service from terminal, the result is the same stick is not visible from command

Code: Select all

sudo snap interface serial-port

Same problem over here!
What I have learned up to now:
I manage to get Zwave-JS-UI working on a freshly installed RPI (Debian Bullseye from 2023-05-03) in the "Snap-way" perfectly explained above,
but as soon as I update Bullseye (“sudo apt update” && “sudo apt upgrade”) Zwave-JS-UI can no longer connect to my Zwave stick (“Driver: Failed to open the serial port” in Zwave-JS-UI and “sudo snap interface serial-port” no longer shows a “core”…).
very frustrating… looks like a bug in a fully updated Bullseye

see also: https://community.home-assistant.io/t/i ... u=heisitje

solved the issue

heistje wrote: ↑Friday 15 September 2023 22:27

d3smo wrote: ↑Thursday 01 June 2023 16:00

thomasbaetge wrote: ↑Thursday 01 June 2023 12:54 Your stick can connect to one instance at a time only.
So while OZW is running, zwJS can not access it (and vice versa)

I've try disable OZW in Domoticz devices and stop domoticz service from terminal, the result is the same stick is not visible from command

Code: Select all

sudo snap interface serial-port

Same problem over here!
What I have learned up to now:
I manage to get Zwave-JS-UI working on a freshly installed RPI (Debian Bullseye from 2023-05-03) in the "Snap-way" perfectly explained above,
but as soon as I update Bullseye (“sudo apt update” && “sudo apt upgrade”) Zwave-JS-UI can no longer connect to my Zwave stick (“Driver: Failed to open the serial port” in Zwave-JS-UI and “sudo snap interface serial-port” no longer shows a “core”…).
very frustrating… looks like a bug in a fully updated Bullseye

see also: https://community.home-assistant.io/t/i ... u=heisitje

solved the issue with this:
https://www.reddit.com/r/debian/comment ... are_button

Hello

Context:
Version: 2023.2
Build Hash: 19efd039c
Compile Date: 2023-07-21 17:23:44
dzVents Version: 3.1.8
Python Version: 3.9.2 (default, Mar 12 2021, 04:06:34) [GCC 10.2.1 20210110]

Zwave Configuration :

OZW up and running successfully for several years with the following Zwave devices
- FGDW002 Door Opening Sensor 2+
- FGFS101 Zwave+ Flood Sensor+
- FGSD002 Smoke Sensor+
- FGWPE/F Wall Plug Gen5+
- FGS222 Double Relay Switch 2x1.5kW
- FGBS001 Universal Binary Sensor
- ZW095 Home Energy Meter Gen5+
- ZW117 Range Extender 6+
- ZW090 Z-Stick Gen5 EU

Question :
Prior to migrating from OZW to Zwave-JS-UI is there a way to ensure that all these devices are well supported by Zwave-JS-UI and especially that the battery managed devices (Door Sensor, Flood Sensor, Smoke Sensor) update the battery level in Domoticz ?

Is there a Zwave-JS-UI reference document stating the zwave supported devices in Domoticz ?

Many thanks for your reply.

BR

There is the Zwave-JS device configuration database where all the supported devices are listed. https://devices.zwave-js.io/

Hello,

@waltervl : many thanks for your helpful reply.

I have 3 more questions prior to migrating from ozw to zwave JS UI

1 - AEOTEC devices compatibility

I do not see in the AEOTEC list in the Zwave-JS device configuration database the following devices :
- ZW095 Home Energy Meter Gen5+
- ZW117 Range Extender 6+
- ZW090 Z-Stick Gen5 EU
Are they compatible with zwave JS UI ?
I would appreciate if anyone is currently using these devices with zwave JS UI to let me know

2 - Zwave-JS device configuration database
What is the meaning of the information "Compatibility" shown at the top right corner of the screen displaying the settings of each device ?
For the Fibaro devices it is set to 0

3 - Battery managed devices
Regarding the following fibaro devices:
- FGDW002 Door Opening Sensor 2+
- FGFS101 Zwave+ Flood Sensor+
- FGSD002 Smoke Sensor+
- FGWPE/F Wall Plug Gen5+
I would appreciate if anyone is currently using these devices with zwave JS UI to let me know if the battery level is correctly updated in Domoticz

Many thanks for your help and replies.
BR

The missing aeotec devices are listed in aeon labs. Seems to be the same manufacturer.

The rest I have no answer on.

meal wrote: ↑Friday 29 September 2023 11:06
1 - AEOTEC devices compatibility

- ZW090 Z-Stick Gen5 EU
Are they compatible with zwave JS UI ?
I would appreciate if anyone is currently using these devices with zwave JS UI to let me know

Have a look here: viewtopic.php?p=303964#p303964
This is the old ZWAVE stick it is running just fine I even managed to update the firmware.

I am preparing the migration from OpenZwave to Z-Wave JS UI and am using the tutorial from 09 June 2023 as a basis.
@d3smo - many thanks for this. Is it still up to date or are there any updates?

I have an installation with about 50 nodes. But I will only start the adventure with a test environment.
Now I have to realise that I am already stuck with the first task: "Backup security Network Key" Where do I find the key, or are there several keys, one per node?

Same question here. It is not clear or obvious to me what is meant by security key and where to find it.

It is set in the Hardware click on the Setup on the ZWAVE Hardware item ... then you click on the ZWAVE Controller device and scroll down to the details where you will find "4. Security Network Key:" defined.