-
-
Notifications
You must be signed in to change notification settings - Fork 206
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bug] Notification going to Node_id topic instead of Node_name topic. #334
Comments
Related to #217 ? |
Not sure, I just read through that other issue and seems like it was happening in the homeassistant discovery topic. |
I'll close this issue if it's the same underlying problem, just let me know. |
@towerhand @larstobi FIxed on master |
Thanks @robertsLando, you are always so fast to fix issues. Really appreciate it. |
Thanks!!! 😊 |
I just noticed the lock doesn't update the state in home assistant when manually operated, I can see the state change with the debug console in zjs2m. Is there something in this fix that could have caused that? otherwise I'll create a new issue. |
Could you enable debug logging and attach the logs? With the debug logleve you should see the mqtt message sent (if any) after the state update |
I'm trying but my rp3 is struggling. The logs are growing considerably with the debug log level, over 200 MB when all nodes are completed. Below is what I was able to find by searching the manual lock operation. 2021-02-02 09:19:01.924 INFO ZWAVE: Node 22: notification: Manual lock operation here start listing all 250 user codes then:
|
Please let me know if you need anything else. Is it related to the PR fixing the notification path, or a new issue, or on my end? |
I'm going to release a new version, could be also a deivce issue btw. Open a separete log and attach all logs (both zwavejs and zwavejs2mqtt) |
Before submitting a bug please read: https://zwave-js.github.io/zwavejs2mqtt/#/troubleshooting/bug_report
Version
Build/Run method
zwavejs2mqtt version: 1.0.0 rc.1+cd11214.cd11214
zwavejs version: 6.0.1-798516f
Describe the bug
In the gateway settings I have turned on the option to use node names instead of node ids and it's working properly for all nodes except one, node 22 which is a door lock. The status, node info and CCs are getting published to the node name topic (zwave2jsmqtt/yale_door_lock) as expected, but the notifications are getting published to node_22 topic (zwave2jsmqtt/nodeID_22/notification), what a getting published there are: manual_unlock_operation, manual_lock_operation, RF_lock_operation, RF_unlock_operation.
To Reproduce
I'm checking the mqtt information and topics with MQTT explorer, I have erased the nodeID_22.
Manually locking and unlocking the lock creates the manual_unlock_operation and manual_lock_operation on nodeID_22, locking and unlocking from HA creates the RF_lock_operation and RF_unlock_operation on nodeID_22.
Expected behavior
I would assume the notification topic should be under the node name topic, like everything else. (zwave2jsmqtt/yale_door_lock/notification)
Additional context
I have refreshed values and re-interview the node.
The text was updated successfully, but these errors were encountered: