ZWA003 NanoMote and zwave js ui

[Eugene]

Hi Guys,

I am trying to migrate from OZW to zwave js ui and i got stuck with making my Aeotec Limited ZWA003 NanoMote Quad+ key fob work via MQTT. i am able to properly discover the key fob in Zwave js ui, the information about it is being seen in mosquito but i am straggling to find a way how can i make the key fob work in domoticz.

With Domoticz using OZW i was able to assign key fob buttons to scenes, when i attempt to do the same thing with Zwave JS UI and MQTT - nothing happens, the scene does not see a button pressed. Also when i press the key fob buttons i do not see any events being produced in MQTT/Mosquito.

Did i miss something? The rest of the devices - thermostats, switches are working with no issues so far.

Thanks.

Here is what i see in MQTT about key fob:

zwave/Eugene_Keyfob/status {"time":1706127218922,"value":true,"status":"Asleep","nodeId":68}
zwave/Eugene_keyfob/status {"time":1706127308186,"value":true,"status":"Awake","nodeId":69}
zwave/Eugene_keyfob/lastActive {"time":1706128643332,"value":1706128643331}
zwave/Eugene_keyfob/wake_up/endpoint_0/controllerNodeId {"time":1706127301504,"value":1}
zwave/Eugene_keyfob/wake_up/endpoint_0/wakeUpInterval {"time":1706127301398,"value":0}
zwave/Eugene_keyfob/configuration/endpoint_0/Level_of_Low_Battery {"time":1706127306949,"value":20}
zwave/Eugene_keyfob/configuration/endpoint_0/Multilevel_Command_Duration {"time":1706127308043,"value":255}
zwave/Eugene_keyfob/configuration/endpoint_0/Low_Battery_Buzzer {"time":1706127308123,"value":0}
zwave/Eugene_keyfob/configuration/endpoint_0/Central_Scene_Notifications {"time":1706127308168}
zwave/Eugene_keyfob/central_scene/endpoint_0/slowRefresh {"time":1706127308166}
zwave/Eugene_keyfob/manufacturer_specific/endpoint_0/manufacturerId {"time":1706127299817,"value":881}
zwave/Eugene_keyfob/manufacturer_specific/endpoint_0/productType {"time":1706127299820,"value":2}
zwave/Eugene_keyfob/manufacturer_specific/endpoint_0/productId {"time":1706127299823,"value":3}
zwave/Eugene_keyfob/battery/endpoint_0/level {"time":1706127301689,"value":72}
zwave/Eugene_keyfob/battery/endpoint_0/isLow {"time":1706127301692,"value":false}
zwave/Eugene_keyfob/version/endpoint_0/libraryType {"time":1706127300037,"value":3}
zwave/Eugene_keyfob/version/endpoint_0/protocolVersion {"time":1706127300041,"value":"4.61"}
zwave/Eugene_keyfob/version/endpoint_0/firmwareVersions {"time":1706127300045,"value":["1.3"]}
zwave/Eugene_keyfob/version/endpoint_0/hardwareVersion {"time":1706127300051,"value":1}

[gizmocuz]

Just to be sure, In ZWaveJS-UI you enabled under home assistant the MQTT Auto Discovery? (Leave all default like the Discovery prefix)
Enable MQTT Discovery and Retained discovery
In Domoticz you are using the MQTT Auto Discovery hardware (not the plain MQTT)
You do see discovery messages in Domoticz?
You enabled 'Accept new hardware devices' under settings? If not, enable this, disable the MQTT-AD hardware and enable it again
The Scenes you are making in Domoticz, not in ZWaveJS-UI I presume?

[Eugene]

gizmocuz, thanks for your help. Looks like i did everything right as you are suggesting. My comments are below

Just to be sure, In ZWaveJS-UI you enabled under home assistant the MQTT Auto Discovery? (Leave all default like the Discovery prefix)
Enable MQTT Discovery and Retained discovery

Yes, i did. Attached screenshot for your reference.

In Domoticz you are using the MQTT Auto Discovery hardware (not the plain MQTT)

Yes, the auto discovery one.

You do see discovery messages in Domoticz?

Yes, i do. here are the messages related to the dicovery of keyfob which i try to make working. Also keyfob created device in Domoticz/devices. Screenshot attached.[/img]

Spoiler: show

2024-01-25 11:18:52.739 Status: ZWave-MQTT: discovered: Eugene keyfob (Eugene keyfob_scene_state_scene_001)/Eugene keyfob (Eugene keyfob_scene_state_scene_001) (unique_id: zwavejs2mqtt_0xd3b648f3_72-91-0-scene-001)
2024-01-25 11:18:52.841 Status: ZWave-MQTT: discovered: Eugene keyfob (Eugene keyfob_scene_state_scene_002)/Eugene keyfob (Eugene keyfob_scene_state_scene_002) (unique_id: zwavejs2mqtt_0xd3b648f3_72-91-0-scene-002)
2024-01-25 11:18:52.943 Status: ZWave-MQTT: discovered: Eugene keyfob (Eugene keyfob_scene_state_scene_003)/Eugene keyfob (Eugene keyfob_scene_state_scene_003) (unique_id: zwavejs2mqtt_0xd3b648f3_72-91-0-scene-003)
2024-01-25 11:18:53.044 Status: ZWave-MQTT: discovered: Eugene keyfob (Eugene keyfob_scene_state_scene_004)/Eugene keyfob (Eugene keyfob_scene_state_scene_004) (unique_id: zwavejs2mqtt_0xd3b648f3_72-91-0-scene-004)
2024-01-25 11:18:53.147 Status: ZWave-MQTT: discovered: Eugene keyfob (Eugene keyfob_scene_state_slowrefresh)/Eugene keyfob (Eugene keyfob_scene_state_slowrefresh) (unique_id: zwavejs2mqtt_0xd3b648f3_72-91-0-slowRefresh)
2024-01-25 11:18:53.249 Status: ZWave-MQTT: discovered: Eugene keyfob (Eugene keyfob_battery_level)/Eugene keyfob (Eugene keyfob_battery_level) (unique_id: zwavejs2mqtt_0xd3b648f3_72-128-0-level)
2024-01-25 11:18:53.351 Status: ZWave-MQTT: discovered: Eugene keyfob (Eugene keyfob_battery_islow)/Eugene keyfob (Eugene keyfob_battery_islow) (unique_id: zwavejs2mqtt_0xd3b648f3_72-128-0-isLow)

You enabled 'Accept new hardware devices' under settings? If not, enable this, disable the MQTT-AD hardware and enable it again

Yes, i did.

The Scenes you are making in Domoticz, not in ZWaveJS-UI I presume?

Yep, in domoticz.

Also i noticed that there are no events generated in the ZWave JS UI debug logs when i click the button on the key fob. When i double click the key fob which is attempt to include/exclude, i see the following log messages in the Zwave JS UI logs but no matter if i double click or one click - no logs seen in Domoticz and Domoticz Scene does not react on button add attempt (times out)

Spoiler: show

2024-01-25T10:02:41.848Z DRIVER « [Node 072] [REQ] [ApplicationUpdateRequest]
payload: 0x48080418015e55989f6c
2024-01-25T10:02:41.849Z CNTRLR « [Node 072] Received updated node info

also i noticed that one click does not reflect in Mosquitto at all when i subscribe to all channels. When i double click , the following message is seen in Mosquitto

zwave/Eugene_keyfob/lastActive {"time":1706178465480,"value":1706178465480}

[gizmocuz]

I remember I had such keyfob a long time ago, and somehow you could set it in 'scene' mode. (by holding down a button combination, must be in the manual)
Also Domoticz only add the switches when you press the buttons, they should be visible in the devices overview

That high value in your status object looks a bit weird to me

Is it possible you could also post your config object?

See the following wiki topic:

https://www.domoticz.com/wiki/MQTT_AD_Report_Problems

[Eugene]

Thanks, I will dig more into possible combinations of buttons on the key fob. Strange thing is that when i use OZW device in domoticz, i make just a simple button click to add button to the Scene.

I hope this is the config object you asked for.

I have 4 of these, where only scene id is changing, posting the 1st one:

Spoiler: show

{
"state_topic": "zwave/Eugene_keyfob/central_scene/endpoint_0/scene/001",
"value_template": "{{ value_json.value | default('') }}",
"json_attributes_topic": "zwave/Eugene_keyfob/central_scene/endpoint_0/scene/001",
"device": {
"identifiers": [
"zwavejs2mqtt_0xd3b648f3_node72"
],
"manufacturer": "Aeotec Ltd.",
"model": "NanoMote Quad (ZWA003)",
"name": "Eugene keyfob",
"sw_version": "1.3"
},
"name": "Eugene keyfob_scene_state_scene_001",
"unique_id": "zwavejs2mqtt_0xd3b648f3_72-91-0-scene-001"
}

and two others which are probably less interesting considering the issue i am facing:

Spoiler: show

{
"state_topic": "zwave/Eugene_keyfob/central_scene/endpoint_0/slowRefresh",
"value_template": "{{ value_json.value | default('') }}",
"json_attributes_topic": "zwave/Eugene_keyfob/central_scene/endpoint_0/slowRefresh",
"device": {
"identifiers": [
"zwavejs2mqtt_0xd3b648f3_node72"
],
"manufacturer": "Aeotec Ltd.",
"model": "NanoMote Quad (ZWA003)",
"name": "Eugene keyfob",
"sw_version": "1.3"
},
"name": "Eugene keyfob_scene_state_slowrefresh",
"unique_id": "zwavejs2mqtt_0xd3b648f3_72-91-0-slowRefresh"
}

{
"value_template": "{{ value_json.value }}",
"unit_of_measurement": "%",
"device_class": "battery",
"state_topic": "zwave/Eugene_keyfob/battery/endpoint_0/level",
"json_attributes_topic": "zwave/Eugene_keyfob/battery/endpoint_0/level",
"device": {
"identifiers": [
"zwavejs2mqtt_0xd3b648f3_node72"
],
"manufacturer": "Aeotec Ltd.",
"model": "NanoMote Quad (ZWA003)",
"name": "Eugene keyfob",
"sw_version": "1.3"
},
"name": "Eugene keyfob_battery_level",
"unique_id": "zwavejs2mqtt_0xd3b648f3_72-128-0-level"
}

[waltervl]

I have updated the wiki page https://www.domoticz.com/wiki/MQTT_AD_Report_Problems so it should be easier to find Config and State topics and their payloads....

[Eugene]

waltervl, you made me thinking i did not share the right data in my first attempt

i feel blind, but i can't find where the payload is in MQTT explorer. On the right side i see Topic, Value, Publish and Stats fields but can't find the payload Could you cure my blindness please?

[Eugene]

Guys,

thanks for all your help. I am giving up trying to get the latest version. I tried running previous Domoticz versions and found all my devices working with 2022.1 and OZW

In 2024.x with OZW i am losing my Danfoss Thermostats, in 2024.x with Zwave JS UI i am losing my key fobs. I will stay with 2022.1 for now.

Thanks again

[Eugene]

Hi Guys,

I finally migrated to Zwave JS UI and managed to make NanoMote key fobs work with domoticz in the same manner they were working with OpenZwave. The solution is quite unexpected and i was lucky to find it - you need to include key fobs into Zwave without encryption enabled (by default Zwave JS UI tries to enable encryption). Not sure why, but when included with encryption the event from key fob is not reaching domoticz at all, perhaps some bug in the device code. I hope i will help someone who is stuck as i was

[waltervl]

Good, and please make an issue at Zwave-JS so they can check if is a bug on their side.