zwavejs2mqtt

[heggink]

In terms of removing the plugin name from the device name, please file that separately as an enhancement and we'll look into that as well.

I've written a python script to rename the devices, based on the names in zwavejs2mqtt + some rules (that could be changed in the script)
I'm not a coder and it's my 2nd python script, so perhaps not perfect.
Anyway I've renamed all the devices and I have less to do manually
Screenshot 2021-08-29 122618.png

the NODES is the extract of zwavejs2mqtt
the DEVICES is the list of the devices to rename
When I use a device, I remove the number (unit) at the end of the name and eventually add something; easier for me to change the end than the beginning

Very nice!

[heggink]

I've 2 issues with FIBARO FGRGBWM441 RGBW Controller
1/ there is no longer a device to change the color
Screenshot 2021-08-29 124643.png
2/ with OZW in dz, I have a script to launch a LED animation based on the "zwave hardware" and there is no longer an hardware inside dz

Code: Select all

http://localhost:8080/json.htm?type=command&param=applyzwavenodeconfig&idx=10&valuelist=72_Ng%3D%3D

Is Domoticz able to activate RGBW animation programs?
Perhaps it is possible to do it directly on zwavejs2mqtt? How?

OK, so on the first issue, I suspect that this is something we have not added since I don't own anything rgbw based and, probably, neither did moroen.

In order to get it added, we need to know what messages are being sent by zwavejs2mqtt (you can use either the snooper utility or mosquitto_sub as described in previous entrie)s. We then need to add a mapping for it and there may be a need for some incremental coding.

Please submit a ticked on the plugin github page.

Wrt the animation, Since I don't know what messages are being sent, I also don't know whether we could create a device that supports the animation (it would probably have to be one of those selector switches). Assuming zwavejs2mqtt supports this, you can always send a message via mqtt that triggers the effect (mosquitto_pub ...) and should already work.

[hestia]

Issue opened on the 1st part
https://github.com/moroen/ZWave-MQTT-plugin/issues/19
I'll give more info in the issue, don't know what to give!
On the 2nd part, this could be done with Home Assistant, but how?

you can always send a message via mqtt that triggers the effect (mosquitto_pub ...) and should already work.

how?

[heggink]

Issue opened on the 1st part
https://github.com/moroen/ZWave-MQTT-plugin/issues/19
I'll give more info in the issue, don't know what to give!
On the 2nd part, this could be done with Home Assistant, but how?

you can always send a message via mqtt that triggers the effect (mosquitto_pub ...) and should already work.

how?

in the tools folder, there is a utility called mqtt-snooper.py. Run that with the IP of the system that runs your mqtt broker as argument.

Code: Select all

./mqtt-snooper.py <host-ip>

. If mqtt runs on the same system, localhost will work as well.
If your mqtt broker uses passwords you need a different command:

Code: Select all

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

You should see messages for the RGB Controller (look up the node number in zwavejs2mqtt, is it 95 below?) and provide these with the github ticket.

Then I will take a look at what needs to happen.

In terms of sending messages to zwavejs2mqtt, that can be done with

Code: Select all

mosquitto_pub -h <host-ip> -q 1 -v -u <username> -P <password> -t <TOPIC> -m <PAYLOAD> 

topics and payloads can be found here: https://zwave-js.github.io/zwavejs2mqtt/#/guide/mqtt
I have not tried this so would need to do some digging as well to see what the correct topic and message needs to be.

H

[Varazir]

Is it just me or is it a bug that I don't get the kwh data ?

[hestia]

You should see messages for the RGB Controller (look up the node number in zwavejs2mqtt, is it 95 below?) and provide these with the github ticket.

When doing what? As the feature is not present?

is it 95 below?

Yes, I've got 2 on them
"95": { "name": "LED Terrasse"
"119": { "name": "LED s/ Balcon

[heggink]

Is it just me or is it a bug that I don't get the kwh data ?

I've not found the time to look into this. Been away.

Sent from my SM-G980F using Tapatalk

[hestia]

Is it just me or is it a bug that I don't get the kwh data ?

I've not found the time to look into this. Been away.

Sent from my SM-G980F using Tapatalk

It seems to be the same for me

Screenshot 2021-08-29 171051.png (122.34 KiB) Viewed 1755 times

Also when on the Log to get the history, the browser alert on performance issue

Screenshot 2021-08-29 170432.png (85.28 KiB) Viewed 1755 times

[hestia]

One device doesn't update the status in dz, neither in zwavejs2mqtt
Qubino ZMNHDD
To On, it is ok
To Off, no change

Screenshot 2021-08-29 172452.png (35.73 KiB) Viewed 1755 times

The network seems ok

Screenshot 2021-08-29 163527.png (60.84 KiB) Viewed 1755 times

Something to do?
Any documentation on the GUI for ZWave To MQTT?

[Varazir]

Is it just me or is it a bug that I don't get the kwh data ?

I've not found the time to look into this. Been away.

Sent from my SM-G980F using Tapatalk

That's cool, just checking of anyone else having the same issue so we can expand the TS from being my setup.

[hestia]

Some results of the testing, almost finish for the first part: basic testing: on/off, get: temp, lux, movement, Watt, kWh

Screenshot 2021-08-29 184800.png (57.61 KiB) Viewed 1746 times

21 different products, 17 with OKs
The issues:
1/FGRGBWM441 RGBW Controller: see above, not implemented totally
2/ Unknown product: wakeup issue?
3/ No update status: see above (on switch on/off the switch in the wall, the status in dz is not updated. Things to do on the network?
4/ No kWh in dz for all devices, Watt ok
5/ Perf issue with the log GUI for kWh
Next steps, solve the issues ; see the stability on a long period
For the stability: better than with OZW for the moment, because I did a lot off things w/o any outage, or freeze of the server (with OZW, I would have to restart dz several times!)
That's a very good start!

[hestia]

...FIBARO FGRGBWM441 RGBW Controller ... animation

...Wrt the animation, Since I don't know what messages are being sent, I also don't know whether we could create a device that supports the animation (it would probably have to be one of those selector switches). Assuming zwavejs2mqtt supports this, you can always send a message via mqtt that triggers the effect (mosquitto_pub ...) and should already work.

I've found this with Home Assistant
https://community.home-assistant.io/t/f ... rams/37235

Code: Select all

action:
  service: zwave.set_config_parameter
  data_template: {
    "node_id": 5,
    "parameter": 72,
    "value": 6,
    "size": 1
           } 

But I don't know what to do with it

[hestia]

I think, I removed a device by mistake because I have a gap in the #

Screenshot 2021-08-30 075253.png (20.3 KiB) Viewed 1720 times

Is there any way to get it again?

[heggink]

Any device that gets reported (through a mqtt device) will ALWAYS be recreated by the plugin. The moment it sees a message for a supported device type/attribute, it will create a device for it if that device is missing from domoticz.

[waltervl]

Perhaps an idea to now make separate zwavejs2mqtt issue topics in the Zwave sub forum if something rises up or someone has specific questions? Now you have to go to 8 pages of information.....

[heggink]

Is it just me or is it a bug that I don't get the kwh data ?

I've not found the time to look into this. Been away.

Sent from my SM-G980F using Tapatalk

That's cool, just checking of anyone else having the same issue so we can expand the TS from being my setup.

Hi @varazir, in order to understand what's going on, can you:
- create an issue on github
- switch on debugging and post the log in the ticket?
That way, I know what messages are being sent and find a fix.
I did just update the plugin myself (I was still a few versions behind myself ) and my devices are working so something must be different with yours. I need to understand what that is.

[heggink]

You should see messages for the RGB Controller (look up the node number in zwavejs2mqtt, is it 95 below?) and provide these with the github ticket.

When doing what? As the feature is not present?

is it 95 below?

Yes, I've got 2 on them
"95": { "name": "LED Terrasse"
"119": { "name": "LED s/ Balcon

This is only part of the message being sent. Please post the entire message. As an example, here's what I see:

Code: Select all

09:57:55 zwave/89/50/0/value/65537 b'{"time":1630310275262,"value":945.74,"nodeName":"NEO Study HE Plug","nodeLocation":"Garage"}'
09:57:56 zwave/89/50/0/value/66049 b'{"time":1630310276161,"value":70.76,"nodeName":"NEO Study HE Plug","nodeLocation":"Garage"}'
09:57:57 zwave/89/50/0/value/66561 b'{"time":1630310277245,"value":227.37,"nodeName":"NEO Study HE Plug","nodeLocation":"Garage"}'
09:57:58 zwave/89/50/0/value/66817 b'{"time":1630310278154,"value":0.42,"nodeName":"NEO Study HE Plug","nodeLocation":"Garage"}'

Also, if you can switch on debug and post the log (just the zigbee2mqtt plugin messages) on githup as well then that's even better.

H

[heggink]

Perhaps an idea to now make separate zwavejs2mqtt issue topics in the Zwave sub forum if something rises up or someone has specific questions? Now you have to go to 8 pages of information.....

Good idea: viewtopic.php?f=24&t=36906

[EddyG]

It sounds promising. I have a few questions.
I have several Thermostats: EUR_SPIRITZ Wall Radiator Thermostat+ EUROtronic 0x0001 0x0003
I suppose that they work with zwavejs2mqtt. Currently I have 17 devices created per thermostat of which there are 4 used.
I also suppose that those 17 devices are present in zwavejs2mqtt, is that the case?
How many devices will be present in Domoticz via the plugin?
Is it simply possible to add (from the remaining 13) more devices to Domoticz via the plugin?

[heggink]

I have one of those devices and it works but I don't have 17 subdevices. Zwavejs2mqtt supports them. The plugin only implements part of your 17 devices. I will look it up when I am at home again and pm you with the details. In terms of the autodiscovery, this is the next item on the list to implement. Hope to be able to test it soon.

Sent from my SM-G980F using Tapatalk