Hi all,
Last week I went from OZW to Zwave js.
The cheapy rollershutter modules shows all the entities like they did before. (By OZW)
But the Fibaro rollershutter modules doesn’t.
The cover entity I have for the fibaromodule doesn’t work and the status is “unknown”.
By OZW I had the same entities like the cheapy rollershutter modules.
Is there anyway to get this like it used to?
This is a cheapy one:
This is a Fibaro:
What are the errors in the logs from zwavejs?
Looking at the model numbers in those screenshots they APPEAR to both be in the device database but there is insufficient information to know if those exact variants are there I hace had good success opening a discussion on the node-zwavejs GitHub repo for troubleshooting assistance…
" · RequestNodeInfo (0x60)
· RemoveFailedNode (0x61)
· IsFailedNode (0x62)
· ReplaceFailedNode (0x63)
· UNKNOWN_FUNC_UNKNOWN_0x66 (0x66)
· UNKNOWN_FUNC_UNKNOWN_0x67 (0x67)
· GetRoutingInfo (0x80)
· UNKNOWN_FUNC_LOCK_ROUTE_RESPONSE (0x90)
· UNKNOWN_FUNC_GET_PRIORITY_ROUTE (0x92)
· UNKNOWN_FUNC_SET_PRIORITY_ROUTE (0x93)
· UNKNOWN_FUNC_UNKNOWN_0x98 (0x98)
· UNKNOWN_FUNC_UNKNOWN_0xB4 (0xb4)
· UNKNOWN_FUNC_WATCH_DOG_ENABLE (0xb6)
· UNKNOWN_FUNC_WATCH_DOG_DISABLE (0xb7)
· UNKNOWN_FUNC_WATCH_DOG_KICK (0xb8)
· UNKNOWN_FUNC_UNKNOWN_0xB9 (0xb9)
· UNKNOWN_FUNC_RF_POWERLEVEL_GET (0xba)
· UNKNOWN_FUNC_GET_LIBRARY_TYPE (0xbd)
· UNKNOWN_FUNC_SEND_TEST_FRAME (0xbe)
· UNKNOWN_FUNC_GET_PROTOCOL_STATUS (0xbf)
· UNKNOWN_FUNC_UNKNOWN_0xD2 (0xd2)
· UNKNOWN_FUNC_UNKNOWN_0xD3 (0xd3)
· UNKNOWN_FUNC_UNKNOWN_0xD4 (0xd4)
· undefined (0xee)
· UNKNOWN_FUNC_UNKNOWN_0xEF (0xef)
2022-01-03T17:10:41.067Z CNTRLR Performing soft reset…
2022-01-03T17:10:41.081Z CNTRLR Waiting for the controller to reconnect…
2022-01-03T17:10:42.583Z CNTRLR Re-opening serial port…
2022-01-03T17:10:43.585Z CNTRLR Waiting for the Serial API to start…
2022-01-03T17:10:48.586Z CNTRLR Did not receive notification that Serial API has started, checking if it respo
nds…
2022-01-03T17:10:48.620Z CNTRLR Serial API responded
2022-01-03T17:10:48.642Z CNTRLR querying version info…
2022-01-03T17:10:48.664Z CNTRLR received version info:
controller type: Static Controller
library version: Z-Wave 4.54
2022-01-03T17:10:48.666Z CNTRLR supported Z-Wave features:
2022-01-03T17:10:48.666Z CNTRLR querying controller capabilities…
2022-01-03T17:10:48.696Z CNTRLR received controller capabilities:
controller role: primary
is in other network: false
is SIS present: true
was real primary: true
is a SUC: true
2022-01-03T17:10:48.697Z CNTRLR finding SUC…
2022-01-03T17:10:48.710Z CNTRLR This is the SUC
2022-01-03T17:10:48.710Z CNTRLR querying node information…
2022-01-03T17:10:48.819Z CNTRLR received node information:
controller role: primary
controller is a SUC: true
controller is a slave: false
controller supports timers: false
nodes in the network: 1, 11, 12, 13, 14, 15
2022-01-03T17:10:48.901Z CNTRLR [Node 001] Embedded device config loaded
2022-01-03T17:10:48.912Z CNTRLR [Node 011] Embedded device config loaded
2022-01-03T17:10:48.919Z CNTRLR [Node 012] Embedded device config loaded
2022-01-03T17:10:48.941Z CNTRLR [Node 013] Embedded device config loaded
2022-01-03T17:10:48.952Z CNTRLR [Node 014] Embedded device config loaded
2022-01-03T17:10:48.959Z CNTRLR setting serial API timeouts: ack = 1000 ms, byte = 150 ms
2022-01-03T17:10:48.971Z CNTRLR serial API timeouts overwritten. The old values were: ack = 1500 ms, byte = 15
0 ms
2022-01-03T17:10:48.971Z CNTRLR Interview completed
Starting server on 0.0.0.0:3000
2022-01-03T17:10:48.985Z CNTRLR [Node 001] The node is alive.
2022-01-03T17:10:48.986Z CNTRLR [Node 001] The node is ready to be used
2022-01-03T17:10:48.987Z CNTRLR » [Node 011] pinging the node…
2022-01-03T17:10:49.116Z CNTRLR » [Node 012] pinging the node…
2022-01-03T17:10:49.118Z CNTRLR » [Node 013] pinging the node…
2022-01-03T17:10:49.120Z CNTRLR » [Node 014] pinging the node…
2022-01-03T17:10:49.123Z CNTRLR [Node 015] The node is asleep.
2022-01-03T17:10:49.126Z CNTRLR [Node 015] Beginning interview - last completed stage: ProtocolInfo
2022-01-03T17:10:49.127Z CNTRLR » [Node 015] querying node info…
ZwaveJS server listening on 0.0.0.0:3000
2022-01-03T17:10:49.187Z CNTRLR [Node 011] The node is alive.
2022-01-03T17:10:49.188Z CNTRLR [Node 011] The node is ready to be used
2022-01-03T17:10:49.192Z CNTRLR « [Node 011] ping successful
2022-01-03T17:10:49.227Z CNTRLR [Node 012] The node is alive.
2022-01-03T17:10:49.228Z CNTRLR [Node 012] The node is ready to be used
2022-01-03T17:10:49.232Z CNTRLR « [Node 012] ping successful
2022-01-03T17:10:49.265Z CNTRLR [Node 013] The node is alive.
2022-01-03T17:10:49.265Z CNTRLR [Node 013] The node is ready to be used
2022-01-03T17:10:49.268Z CNTRLR « [Node 013] ping successful
2022-01-03T17:10:49.269Z CNTRLR » [Node 013] Assigning SUC return route…
2022-01-03T17:10:49.303Z CNTRLR [Node 014] The node is alive.
2022-01-03T17:10:49.304Z CNTRLR [Node 014] The node is ready to be used
2022-01-03T17:10:49.310Z CNTRLR « [Node 014] ping successful
New client
New client
Client disconnected
Code 1000:
2022-01-03T17:42:40.204Z DRIVER Dropping message with invalid payload
2022-01-03T17:48:27.144Z DRIVER Dropping message with invalid payload
2022-01-03T17:48:27.311Z DRIVER Dropping message with invalid payload
2022-01-03T17:52:28.425Z DRIVER Dropping message with invalid payload"
This is all I see.
I don’t have that much knowledge of zwave and doesn’t understand what it’s saying here.
I’ll try to ask the same question on GitHub.
Node 15 is a battery operated node that went into sleep mode before it was fully interviewed. I have sometimes seen these take ours to complete but then work fine.
What node numbers have the issue? The entities will not show in Home Assistant until a device is fully interviewed. Part of that process is where the device sends an information from with details of its model identity and supported features.
It’s about node 13 and 14. (Node 15 is a remote)
I’ve tried interviewing them again but it doesn’t make any difference.
Are both device and entities missing from HA or just the entities?
Are you using zwavejs2mqtt as a control panel? That is what I use.
Just the entities are missing.
I use the “Z-Wave JS” add-on and this is workong well with the TKB modules.
One of your screenshots was a TKB. Is that one working or not?
i use the official zwavejs2mqtt from the developers since I am running Home Assistant Container. If the device does not show up in HA then I do not know how to help troubleshoot.
Sorry.
The TKB modules are working great.
The problem is just with the Fibaro modules.
The add-on I use is a official home assistant add-on.
You mention addons. You must be using HaOS ot Home Assistant Supervised. I use Home Assistant Container which has no addons.
Sorry.
No problem.
Thanks for trying!
