Maybe, but the discussions think that catching SIGINT might be the solution, but i’m already using SIGINT in my docker-compose file. I’ll watch that issue to see what they come up with. thanks!
I’ve got this same issue with my Fibaro Motion Sensors. Can’t get any entities in HA but I can see parameters, but those aren’t available in HA.
Those of us that are not seeing things reporting remember they do have an open issue on this with a ton of devices listed
So if you’re missing values for your devices check this issue and see if your device is on the list. If you got time to donate they’re looking for volunteers to help vet the files and get them rolled into future releases.
@GaryOkie - I believe for the web socket interface your URL should be ‘ws://IPaddress:port’, with the default port being 3000.
So for you it should be ‘ws://192.168.1.123:3000’.
Damn that’s a long list! 
1 Like
The HA Z-WaveJS add-on and the zwavejs2mqtt add-on UI configs for zwave device appear differently. I’ve used my tcp://192.168.1.101:4000 in both places now…
The zwave_js_event works fine. For 10-15 minutes.
After that, Node-RED or HA automations receive them no longer! (Tested in NR and the dev.tools)
They work again for a few minutes after a HA restart.
I’ve tried to restart only the zwave js integration, but that doesn’t work, since it says I have to restart HA to complete the integration restart.
What’s happening, and what can I do?
Sorry, could you clarify where exactly I can request for some of my unknown devices to be added on GitHub? Is it under the Zwave JS project?
The not so popular brand of devices have a lot of use locally due to local availability of them. Myself and a colleague both use them, and can provide whatever details needed about them 
You open an issue on the node-zwave-js repo, after reading this:
@dbrunt / Daniel, HASS is now connected now to the RaZberry - Thanks for the assist!
Perhaps there were some recent changes to the config flow to limit and validate the choices of USB devices to the displayed pick list. Can’t think of any other reason the Z-Wave-JS config is rejecting tcp:// now.
I followed your latest advice and installed Z-Wave-JS_MQTT instead, which had no problem accepting the tcp device setting.
I’m still learning the Z-Way way of doing things and now the HA Z-Wave-JS control. Do you add your Z-Wave devices using Z-Way control panel or through the HA Zwave-JS_MQTT control panel?
Need a quick bit of advice. How do I remove a failed node - I don’t have it anymore, I can’t exclude it.
I’ve tried options such as mark as failed, then remove failed node, but it tells me that it’s not a failed node.
1 Like
Do that part about remove node from all associations. That seems to do the trick for me
Thanks - did that and it says it was successful, but still shows up in the list of nodes for me.
Maybe I need to wait / refresh / restart?
Make sure that 
this isn’t turned on
Nope - but all of the ones I just tried the remove all associations / other actions on are now in Asleep / ProtocolInfo State rather than ‘None’
Have the same problem here… hmmm
Anybody here have any Aeotec Wallmotes?
I have about 8 of them and getting no luck with any of them so far