zwavejs2mqtt

For Z-Wave related questions in Domoticz

Moderator: leecollings

lost
Posts: 616
Joined: Thursday 10 November 2016 9:30
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: zwavejs2mqtt

Post by lost »

heggink wrote: Monday 20 December 2021 13:29 True that the name may not be unique so if it isn't, why not just error out? That would be a lot simpler than having to maintain and update idx to name tables.
On my side, for all external stuff (mostly python written services) that interface with Domoticz using http/json interface, in the get (switch state/user variable) functions, IDX/NAME coherency is checked if a name is provided. As a get for all needed devices is done at services init, if a mismatch is seen this immediately exits on error to avoid mistakes there.

That's not perfect, but using unique names as keys (as an initial development choice) with devices merging several functions/hardware would have mean other trade-offs anyway...
EddyG
Posts: 1042
Joined: Monday 02 November 2015 5:54
Target OS: -
Domoticz version:

Re: zwavejs2mqtt

Post by EddyG »

mgugu wrote: Monday 20 December 2021 12:24
jvdz wrote: Monday 20 December 2021 12:10 but other scripts/integrations (Nodered eg) that work with the IDX need to be adapted to the new IDX of the discovered devices.
In nodered I created a specific flow to create and maintain a global table idx <-> Name. This provides an abstraction layer allowing to use everywhere name instead of idx. Of course name has to be unique in the whole system
I am looking for that method for some time. Could you share the methode?
How do you maintain the table and how do you use the table in flows?
mgugu
Posts: 208
Joined: Friday 04 November 2016 12:33
Target OS: Raspberry Pi / ODroid
Domoticz version: Beta
Location: France
Contact:

Re: zwavejs2mqtt

Post by mgugu »

EddyG wrote: Monday 20 December 2021 16:50 I am looking for that method for some time. Could you share the methode?
How do you maintain the table and how do you use the table in flows?
Image

Code: Select all

[{"id":"79237bef.304494","type":"inject","z":"9581f007.eb9af","name":"1h","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"3600","crontab":"","once":true,"onceDelay":"4","topic":"","payloadType":"date","x":70,"y":80,"wires":[["e07f694d.49acf8"]]},{"id":"e07f694d.49acf8","type":"http request","z":"9581f007.eb9af","name":"","method":"GET","ret":"obj","paytoqs":"ignore","url":"http://192.168.1.200:8080/json.htm?type=devices&filter=all&used=true&displayhidden=1","tls":"","persist":false,"proxy":"","authType":"","x":210,"y":80,"wires":[["2ea5769c.9f707a"]]},{"id":"2ea5769c.9f707a","type":"function","z":"9581f007.eb9af","name":"Build Name:{idx,Type} table","func":"// objectsList = msg.payload=JSON.parse(msg.payload).result\nobjectsList = msg.payload.result\nreturnObject={}\nobjectsList.map(x => {returnObject[x.Name] =\n    {idx : x.idx, Type : x.Type}})\nmsg.payload=returnObject\nreturn msg;\n","outputs":1,"noerr":0,"initialize":"","finalize":"","libs":[],"x":420,"y":80,"wires":[["70abef6e.88497"]]},{"id":"70abef6e.88497","type":"function","z":"9581f007.eb9af","name":"Store global idxTable","func":"global.set('idxTable',msg.payload,\"memoryOnly\");\nglobal.set('idxTable',msg.payload,\"file\");//\"file\"\nnode.status({text:`idxTable: stored`,fill:'green',shape:'dot'});\nreturn msg;","outputs":1,"noerr":0,"initialize":"","finalize":"","libs":[],"x":660,"y":80,"wires":[[]]}]
In nodered settings adapt your storage configuration, mine is:

Code: Select all

contextStorage: {
	   default: "memoryOnly",
	   memoryOnly: { module: 'memory' },
	   file: { module: 'localfilesystem' }
	},
In http request adapt your domoticz address
In addition to idx, "Type" is also stored since it is usefull in some cases
To use it simply do

Code: Select all

IDX = global.get('idxTable','memoryOnly')['<your device name>'].idx;
TYPE = global.get('idxTable','memoryOnly')['<your device name>'].Type;
EddyG
Posts: 1042
Joined: Monday 02 November 2015 5:54
Target OS: -
Domoticz version:

Re: zwavejs2mqtt

Post by EddyG »

Thanks, that's is what I needed, it works.
mgugu wrote: Tuesday 21 December 2021 5:57 In nodered settings adapt your storage configuration, mine is:

Code: Select all

contextStorage: {
	   default: "memoryOnly",
	   memoryOnly: { module: 'memory' },
	   file: { module: 'localfilesystem' }
	},
The storage configuration part lead to a nodered startup problem. I changed that to

Code: Select all

    contextStorage: {
      default: {
        module:"memory",
      },
      file: {
        module:"localfilesystem",
      }
    },
Don't know yet if that is the right solution, but it works until now. Have to investigate if that should be change a bit.
mgugu
Posts: 208
Joined: Friday 04 November 2016 12:33
Target OS: Raspberry Pi / ODroid
Domoticz version: Beta
Location: France
Contact:

Re: zwavejs2mqtt

Post by mgugu »

EddyG wrote: Tuesday 21 December 2021 9:50 The storage configuration part lead to a nodered startup problem.
Strange, this should not work since "memoryOnly" is no mode defined.
Since default module is defined, you can remove all storage options in the code (,'memoryOnly)'
Last edited by mgugu on Tuesday 21 December 2021 10:15, edited 1 time in total.
EddyG
Posts: 1042
Joined: Monday 02 November 2015 5:54
Target OS: -
Domoticz version:

Re: zwavejs2mqtt

Post by EddyG »

After pasting it from the Nodered website it worked. Probably a pasting error.
End result is perfect.... Tnx....
Nautilus
Posts: 722
Joined: Friday 02 October 2015 12:12
Target OS: Raspberry Pi / ODroid
Domoticz version: beta
Location: Finland
Contact:

Re: zwavejs2mqtt

Post by Nautilus »

Hi, any hints for how to migrate battery powered devices from OZW to zwavejs2mqtt? Powered devices were shown right away in zwavejs2mqtt, I've tried waking up the battery powered ones (e.g. fibaro motion sensor, triple click b-button to wake up) and also re-interviewing nodes, but all (except two Danalock V3 locks) battery powered devices are showing as Unknowns after about 12 hours. Should I wait more - should I do something else? The locks did show up very fast, but also they haven't created any other devices to Domoticz than the status so they are currenly identified and "green" in zwavejs2mqtt, but clearly not fully discovered. Any help is appreaciated :)
User avatar
heggink
Posts: 972
Joined: Tuesday 08 September 2015 21:44
Target OS: Raspberry Pi / ODroid
Domoticz version: 12451
Location: NL
Contact:

Re: zwavejs2mqtt

Post by heggink »

I had to reinclude a couple close to the controller. Ultimately, that worked for me.

Sent from my SM-G980F using Tapatalk

Docker in Truenas scale, close to latest beta
DASHTICZ 🙃
RFXCOM, zwavejs2mqtt, zigbee2mqtt,
P1 meter & solar panel
Google home, Wifi Cams motion detection
Geofence iCloud, Bluetooth & Wifi ping
Harmony hub, Nest, lots more :-)
Nautilus
Posts: 722
Joined: Friday 02 October 2015 12:12
Target OS: Raspberry Pi / ODroid
Domoticz version: beta
Location: Finland
Contact:

Re: zwavejs2mqtt

Post by Nautilus »

Ok, did you have to exclude first or just include?
mgugu
Posts: 208
Joined: Friday 04 November 2016 12:33
Target OS: Raspberry Pi / ODroid
Domoticz version: Beta
Location: France
Contact:

Re: zwavejs2mqtt

Post by mgugu »

Nautilus wrote: Tuesday 28 December 2021 10:14 Hi, any hints for how to migrate battery powered devices from OZW to zwavejs2mqtt? Powered devices were shown right away in zwavejs2mqtt, I've tried waking up the battery powered ones (e.g. fibaro motion sensor, triple click b-button to wake up) and also re-interviewing nodes, but all (except two Danalock V3 locks) battery powered devices are showing as Unknowns after about 12 hours. Should I wait more - should I do something else? The locks did show up very fast, but also they haven't created any other devices to Domoticz than the status so they are currenly identified and "green" in zwavejs2mqtt, but clearly not fully discovered. Any help is appreaciated :)
I have some devices marked unknown (product code) but which work perfectly.If the status is green it should be OK.
Domoticz needs MQTT messages to configure new devices. Unfortunately this does not occur very often for battery powered devices (up to 24h in my case for Popp z-rain sensor).
I think you need to be patient while logging MQTT messages with MQTT explorer to check if the problem is zwave or Domoticz discovery side.
Concerning inclusion, after many unsuccessfull operations, the best is to make a factory reset then a new inclusion which has to be done very very close to the controller.
User avatar
heggink
Posts: 972
Joined: Tuesday 08 September 2015 21:44
Target OS: Raspberry Pi / ODroid
Domoticz version: 12451
Location: NL
Contact:

Re: zwavejs2mqtt

Post by heggink »

Nautilus wrote:Ok, did you have to exclude first or just include?
No need to exclude. Just include again.

Sent from my SM-G980F using Tapatalk

Docker in Truenas scale, close to latest beta
DASHTICZ 🙃
RFXCOM, zwavejs2mqtt, zigbee2mqtt,
P1 meter & solar panel
Google home, Wifi Cams motion detection
Geofence iCloud, Bluetooth & Wifi ping
Harmony hub, Nest, lots more :-)
Nautilus
Posts: 722
Joined: Friday 02 October 2015 12:12
Target OS: Raspberry Pi / ODroid
Domoticz version: beta
Location: Finland
Contact:

Re: zwavejs2mqtt

Post by Nautilus »

Thanks for the comments, now seeing some of the battery devices being properly recognized. Seeing some inconsistencies on which devices get created to Domoticz (e.g. Fibaro motion sensor - some get all needed devices right away when recognized, some get only few. Maybe the latter ones are the one that need re-inclusion).

Can anyone confirm that Danalock V3 Z-wave is supported by Domoticz autodiscovery? I can still only see the status device.
Nautilus
Posts: 722
Joined: Friday 02 October 2015 12:12
Target OS: Raspberry Pi / ODroid
Domoticz version: beta
Location: Finland
Contact:

Re: zwavejs2mqtt

Post by Nautilus »

It seems that the above is not the only problem. For quite many switch devices I am getting the following when tryin to use them:

2021-12-28 15:27:08.379 Status: User: XXX initiated a switch command (1220/Joulukuusi/On)
2021-12-28 15:27:08.380 Error: Zwave autodiscovery: Switch not found!? (zwavejs2mqtt_0xeb6dfc9c_50-37-0-currentValue/Joulukuusi)

2021-12-28 15:34:37.501 Status: User: XXX initiated a switch command (1207/nodeID_43_switch_2/On)
2021-12-28 15:34:37.502 Error: Zwave autodiscovery: Switch not found!? (zwavejs2mqtt_0xeb6dfc9c_43-37-2-currentValue/nodeID_43_switch_2

Now, when I look at the topics in mqtt explorer, I can see only one ID under discovery node, yesterday I saw several of them. I can see them under zwave node though. Why have they disappeared from discovery? Can it be the fact that I enable OZW for a while to get my old device names? Since then I've restarted the system and everything so shouldn't it recover? Can I force the discovery topics to be populated somehow again?

edit. I turned the "retained discovery" switch on in zwavejs2mqtt to "on" and now I have the nodes back under discovery topic. Not sure if this is the rights way to do as it was mentioned to best to keep it off...
Nautilus
Posts: 722
Joined: Friday 02 October 2015 12:12
Target OS: Raspberry Pi / ODroid
Domoticz version: beta
Location: Finland
Contact:

Re: zwavejs2mqtt

Post by Nautilus »

Was hoping that with zwavejs2mqtt I would have had more success in setting certain parameter e.g. for Fibaro motion sensors, but looks like they are still suffering from the same problems. E.g. illuminance report being sent almost every second even though I've set a reasonable treshold and interval. Maybe there's a bug in them. Strange thing is that I cannot find anyone else having these problems and I have the issue with few of them (not all though). The battery lasts maybe few weeks with these constant reports....
Spoiler: show
2021-12-30 17:58:33.983 Zwave autodiscovery: Lux/Lux (Ruokailualueen valomäärä)
2021-12-30 17:58:36.178 Zwave autodiscovery: Lux/Lux (Ruokailualueen valomäärä)
2021-12-30 17:58:38.387 Zwave autodiscovery: Lux/Lux (Ruokailualueen valomäärä)
2021-12-30 17:58:40.588 Zwave autodiscovery: Lux/Lux (Ruokailualueen valomäärä)
2021-12-30 17:58:42.791 Zwave autodiscovery: Lux/Lux (Ruokailualueen valomäärä)
2021-12-30 17:58:44.993 Zwave autodiscovery: Lux/Lux (Ruokailualueen valomäärä)
2021-12-30 17:58:47.195 Zwave autodiscovery: Lux/Lux (Ruokailualueen valomäärä)
2021-12-30 17:58:49.398 Zwave autodiscovery: Lux/Lux (Ruokailualueen valomäärä)
2021-12-30 17:58:51.602 Zwave autodiscovery: Lux/Lux (Ruokailualueen valomäärä)
2021-12-30 17:58:53.801 Zwave autodiscovery: Lux/Lux (Ruokailualueen valomäärä)
2021-12-30 17:58:56.001 Zwave autodiscovery: Lux/Lux (Ruokailualueen valomäärä)
2021-12-30 17:58:58.208 Zwave autodiscovery: Lux/Lux (Ruokailualueen valomäärä)
2021-12-30 17:59:00.419 Zwave autodiscovery: Lux/Lux (Ruokailualueen valomäärä)
2021-12-30 17:59:02.607 Zwave autodiscovery: Lux/Lux (Ruokailualueen valomäärä)
2021-12-30 17:59:04.819 Zwave autodiscovery: Lux/Lux (Ruokailualueen valomäärä)
2021-12-30 17:59:07.013 Zwave autodiscovery: Lux/Lux (Ruokailualueen valomäärä)
2021-12-30 17:59:09.254 Zwave autodiscovery: Lux/Lux (Ruokailualueen valomäärä)
2021-12-30 17:59:11.421 Zwave autodiscovery: Lux/Lux (Ruokailualueen valomäärä)
2021-12-30 17:59:13.625 Zwave autodiscovery: Lux/Lux (Ruokailualueen valomäärä)
2021-12-30 17:59:15.822 Zwave autodiscovery: Lux/Lux (Ruokailualueen valomäärä)
2021-12-30 17:59:18.032 Zwave autodiscovery: Lux/Lux (Ruokailualueen valomäärä)
2021-12-30 17:59:20.233 Zwave autodiscovery: Lux/Lux (Ruokailualueen valomäärä)
2021-12-30 17:59:22.434 Zwave autodiscovery: Lux/Lux (Ruokailualueen valomäärä)
2021-12-30 17:59:24.636 Zwave autodiscovery: Lux/Lux (Ruokailualueen valomäärä)
2021-12-30 17:59:26.839 Zwave autodiscovery: Lux/Lux (Ruokailualueen valomäärä)
2021-12-30 17:59:29.041 Zwave autodiscovery: Lux/Lux (Ruokailualueen valomäärä)
2021-12-30 17:59:31.245 Zwave autodiscovery: Lux/Lux (Ruokailualueen valomäärä)
2021-12-30 17:59:33.451 Zwave autodiscovery: Lux/Lux (Ruokailualueen valomäärä)
2021-12-30 17:59:35.642 Zwave autodiscovery: Lux/Lux (Ruokailualueen valomäärä)
2021-12-30 17:59:37.846 Zwave autodiscovery: Lux/Lux (Ruokailualueen valomäärä)
2021-12-30 17:59:40.053 Zwave autodiscovery: Lux/Lux (Ruokailualueen valomäärä)
2021-12-30 17:59:42.258 Zwave autodiscovery: Lux/Lux (Ruokailualueen valomäärä)
2021-12-30 17:59:44.459 Zwave autodiscovery: Lux/Lux (Ruokailualueen valomäärä)
2021-12-30 17:59:46.660 Zwave autodiscovery: Lux/Lux (Ruokailualueen valomäärä)
lost
Posts: 616
Joined: Thursday 10 November 2016 9:30
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: zwavejs2mqtt

Post by lost »

Hello,

Looks Silabs finally released their SDK (that looks targeting both z-wave and zigbee, on a on-demand github private repo for now):
https://www.silabs.com/developers/unify-sdk

Don't know if someone aware of z-wave internals already asked for access to check if this may be a better replacement for OZW than zwavejs (well, JS for driving hardware hurts me a bit!)?
Nautilus
Posts: 722
Joined: Friday 02 October 2015 12:12
Target OS: Raspberry Pi / ODroid
Domoticz version: beta
Location: Finland
Contact:

Re: zwavejs2mqtt

Post by Nautilus »

All in all I have to say I'm very impressed about some of the changes with regards to stability and overall functionality observed now after running zwavejs2mqtt together with Domoticz for about a week. Maybe someone can help me with one question. Initially when zwavejs2mqtt discovers the devices, they do not have a name (of course). After adding some names, I noticed the devices stopped working in Domoticz (sort of - some did, most did not).

I configured zwavejs2mqtt with the help of these recommendations:
https://github.com/moroen/ZWave-MQTT-pl ... avejs2mqtt
Gateway configuration:
Use node names instead of numeric nodeIDs: Off
Ignore location: On
Include Node Info: On
Note: Specifying node names and locations in zwavejs2mqtt is not required, but recommended. This will generate somewhat sane names of the devices when they are added to domoticz.
But as mentioned couple of posts above:
Now, when I look at the topics in mqtt explorer, I can see only one ID under discovery node, yesterday I saw several of them. I can see them under zwave node though. Why have they disappeared from discovery? Can it be the fact that I enable OZW for a while to get my old device names? Since then I've restarted the system and everything so shouldn't it recover? Can I force the discovery topics to be populated somehow again?

edit. I turned the "retained discovery" switch on in zwavejs2mqtt to "on" and now I have the nodes back under discovery topic. Not sure if this is the right way to do as it was mentioned to best to keep it off...
So my retained flag was on. I took it off and everything started working again. I thought this was it. But then I needed to do one more change and when testing the device in Domoticz after the change, it did not work right away. And I'm not fully sure what I did to make it start working again :)

Now I wonder which is the best practice to change device name in zwavejs2mqtt and keep everything working in Domoticz. Is it just this:
Hint: To add all devices at once, enable the plugin in domoticz, and press "Save" in zwavejs2mqtt preferences. This will generate status messages for all devices.
So do I need to save preferences once after each name update to re-generate status messages? Or something else?
PieterS
Posts: 195
Joined: Wednesday 31 May 2017 16:06
Target OS: NAS (Synology & others)
Domoticz version: 2024.7
Location: NL
Contact:

Re: zwavejs2mqtt

Post by PieterS »

waltervl wrote: Sunday 19 December 2021 11:05 Would be nice if someone writes down the procedure how to step over from Domoticz OpenZwave to Zwavejs2mqtt Autodiscover. A lot of zwave users will try to go this road when the stable version is released.
I hope there is a kind of concept somewhere?

Today I downloaded the latest version of zwavejs2mqtt in a seperate docker on my Synology. Seems to run fine as there are no problems in the log and there are passing messages in MQTT Explorer.
But:
Struggling how to implement Zwave in Domoticz (build 13872) which runs in a seperate docker container too. I see no data about Zwavejs2mqtt in the log.

Image
create animated pics

So my question is:
Is there a kind of manual or can someone give me some hints how to configure the plugin so that the data arrives in Domoticz..
Image
create animated pics
Further on I think I have to create dummy sensors? But if I accept new hardware there are no new devices..
Synology with Domoticz build (V2024.7) in Docker
User avatar
waltervl
Posts: 5149
Joined: Monday 28 January 2019 18:48
Target OS: Linux
Domoticz version: 2024.7
Location: NL
Contact:

Re: zwavejs2mqtt

Post by waltervl »

I have updated the Zwavejs2mqtt wiki as much as possible. But it is still more hints then real instructions.
https://www.domoticz.com/wiki/ZwaveJS2MQTT
Domoticz running on Udoo X86 (on Ubuntu)
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
PieterS
Posts: 195
Joined: Wednesday 31 May 2017 16:06
Target OS: NAS (Synology & others)
Domoticz version: 2024.7
Location: NL
Contact:

Re: zwavejs2mqtt

Post by PieterS »

waltervl wrote: Wednesday 05 January 2022 0:44 I have updated the Zwavejs2mqtt wiki as much as possible. But it is still more hints then real instructions.
https://www.domoticz.com/wiki/ZwaveJS2MQTT
Thanks Waltervl. I read the wiki again. Missed some hints, I guess. But now I got some data from zwavejs2mqtt in Domoticz.. :shock: But not quite ready for Domoticz:
Just a small part of it:

Code: Select all

2022-01-05 19:30:11.014  Error: MQTT client Gateway Autodiscover: MQTT_Discovery: Invalid/Unhandled data received! (Topic: in/nodeID_9/notification/endpoint_0/Power_Management/Over-load_status, Message: 0)
2022-01-05 19:30:11.115  Error: MQTT client Gateway Autodiscover: MQTT_Discovery: Invalid/Unhandled data received! (Topic: in/nodeID_9/manufacturer_specific/endpoint_0/manufacturerId, Message: 271)
2022-01-05 19:30:11.215  Error: MQTT client Gateway Autodiscover: MQTT_Discovery: Invalid/Unhandled data received! (Topic: in/nodeID_9/manufacturer_specific/endpoint_0/productType, Message: 1538)
2022-01-05 19:30:11.315  Error: MQTT client Gateway Autodiscover: MQTT_Discovery: Invalid/Unhandled data received! (Topic: in/nodeID_9/manufacturer_specific/endpoint_0/productId, Message: 4097)
2022-01-05 19:30:11.416  Error: MQTT client Gateway Autodiscover: MQTT_Discovery: Invalid/Unhandled data received! (Topic: in/nodeID_9/version/endpoint_0/libraryType, Message: 3)
2022-01-05 19:30:11.516  Error: MQTT client Gateway Autodiscover: MQTT_Discovery: Invalid/Unhandled data received! (Topic: in/nodeID_9/version/endpoint_0/protocolVersion, Message: "4.5")
2022-01-05 19:30:11.616  Error: MQTT client Gateway Autodiscover: MQTT_Discovery: Invalid/Unhandled data received! (Topic: in/nodeID_9/version/endpoint_0/firmwareVersions, Message: ["3.2","3.2"])
2022-01-05 19:30:11.716  Error: MQTT client Gateway Autodiscover: MQTT_Discovery: Invalid/Unhandled data received! (Topic: in/nodeID_9/version/endpoint_0/hardwareVersion, Message: 2)
2022-01-05 19:30:11.816  Error: MQTT client Gateway Autodiscover: MQTT_Discovery: Invalid/Unhandled data received! (Topic: in/nodeID_20/switch_binary/endpoint_0/currentValue, Message: true)
2022-01-05 19:30:11.917  Error: MQTT client Gateway Autodiscover: MQTT_Discovery: Invalid/Unhandled data received! (Topic: in/nodeID_20/switch_binary/endpoint_0/targetValue, Message: true)
2022-01-05 19:30:12.017  Error: MQTT client Gateway Autodiscover: MQTT_Discovery: Something other then 'config' received on discovery topic! (in/nodeID_20/switch_multilevel/endpoint_0/duration/{"unit":"seconds"})!
2022-01-05 19:30:12.017  Error: MQTT client Gateway Autodiscover: MQTT_Discovery: Invalid/Unhandled data received! (Topic: in/nodeID_20/switch_multilevel/endpoint_0/duration, Message: {"unit":"seconds"})
2022-01-05 19:30:12.117  Error: MQTT client Gateway Autodiscover: MQTT_Discovery: Invalid/Unhandled data received! (Topic: in/nodeID_20/switch_multilevel/endpoint_0/currentValue, Message: 99)
2022-01-05 19:30:12.217  Error: MQTT client Gateway Autodiscover: MQTT_Discovery: Invalid/Unhandled data received! (Topic: in/nodeID_20/meter/endpoint_0/value/65537, Message: 314.36)
2022-01-05 19:30:12.318  Error: MQTT client Gateway Autodiscover: MQTT_Discovery: Invalid/Unhandled data received! (Topic: in/nodeID_20/meter/endpoint_0/value/66049, Message: 0)
2022-01-05 19:30:12.418  Error: MQTT client Gateway Autodiscover: MQTT_Discovery: Invalid/Unhandled data received! (Topic: in/nodeID_20/meter/endpoint_0/value/66561, Message: 228.489)
This is how I configured the MQTT client in Domoticz:
Image
And the settings from zwavejs2mqtt:
Image

Both settings in Home Assistant are disabled.
When I accept New Hardware there is no new hardware.

Any more hints to get this working? Thanks in advance
Synology with Domoticz build (V2024.7) in Docker
User avatar
jvdz
Posts: 2189
Joined: Tuesday 30 December 2014 19:25
Target OS: Raspberry Pi / ODroid
Domoticz version: 4.107
Location: Netherlands
Contact:

Re: zwavejs2mqtt

Post by jvdz »

Dejavu ... I've explained this issue in another thread not too long ago :) : viewtopic.php?p=284027#p284027
New Garbage collection scripts: https://github.com/jvanderzande/GarbageCalendar
Post Reply

Who is online

Users browsing this forum: Google [Bot] and 1 guest