-
-
Notifications
You must be signed in to change notification settings - Fork 210
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: Named Topics missing endpoint in topic #69
Comments
Hi, I guess you might miss the endpoint in the topic: So your request: Beside the type error in I also have lots of multi level switches and this is working for me: Hope it helps! |
Thanks, I was just using the auto generated discovery values, so I kinda expected them to be correct. I may trying adding the endpoints manually and seeing if that works. |
This is actually a bug, the gateway is missing endpoints in named mode. Thanks for the issue will fix this tomorrow! |
Can someone try with #74 |
I can but not sure how, i have them inside the discovery topic already. look:
|
@ODINServ Because when endpoint is > 1 it was already added, with that fix it is always added in the topic |
I am trying out Zwavejs2mqtt and thought that this time I'd try Type: "Named Topics" in the Gateway.
It worked find for sending data to Home Assistant, but when I tried to send commands (like toggling a switch) I could see the commands being received in the console output (I am attached to the docker container and I would set "z2m:Mqtt: Message received on zwavJs2Mqtt/Patio/Shades_Ext_South_West/switch_multilevel/targeValue/set"), but no Z-wave commands would be sent and the device would not operate.
I then changed my Type to "ValueID topics" and the commands were now being received ("z2m:Mqtt: Message received on zwaveJs2Mqtt/Patio/5/38/0/targetValue/set"), and the Z-wave commands would be sent and the device responded.
I'm not sure if I was doing something wrong, or if I should be using ValueID instead of Named, but I figured I'd let you know that Named wasn't working for inbound messages from Home Assistant for me.
The text was updated successfully, but these errors were encountered: