Yes, I only edited the configuration.yaml. I did not remove it from the ui. I guess that is my mistake. Going to give it a try after removing it from the integrations.
Edit: that was it. I removed the integration, restarted HA and now it runs fine! 
Thank you!
zwavejs2mqtt only provides the entire zwave control bits and also provides an MQTT client to send the zwave data to the MQTT network.
It doesn’t provide a broker. You have to provide that yourself. And it doesn’t matter at all which broker you use.
The old zwavejs2mqtt platform uses mqtt as the communication protocol (as the name suggests).
The new zwavejs2mqtt platform has been updated to use websockets for communication. Which is also what the new zwavejs add-on uses. So you won’t need the MQTT portion of the zwavejs2mqtt platform once the integration is implemented in HA.
Any idea when ZWave JS will be support service calls for changing config parameters??
A lot of my automations (done through node red) involve changing configration parameters.
For example, when trying to turn on our “alarm”, if all doors are closed and locked, the lightstrip on my light switches turn green, if something is not right, they flash yellow. This is done through ozw.set_config_parameter calls in node red.
Thanks!
that’s clear. so I keep my dedicated MQTT HA instance for that.
Now, about publishing the Zwave states and entities to that broker:
Currently I use core Zwave + the core Mqtt integrations doing that, also using mqtt state_stream
Going forward with the new Zwave JS integration, I’d still need the mqtt transport (now the mqtt integration) and I can still use that combination?
As I understand you I can also use the new ZwaveJS2Mqtt add-on for that, and that would be both the ZwaveJS And the MQTT transport in 1? Meaning I can replace my old Zwave/Mqtt combo for the 1 new integration?
If that’s correct, I’ll go ahead and test that, deinstalling the current (old)Zwave integration and see what happens. Maybe I don’t even have to re-add everything manually (since it is all on the Aeotec stick anyways)?
Would the state_stream still work though ( I am not sure yet if the new zwaveJS2Mqtt is global for the instance, or only for the Zwave_js)
sorry if this is all too detailed, but it is rather fundamental, so better be safe than sorry…
I’m confused about the home assistant “devices” portion of each node. Are these “discovered” from Home Assistant, or discovered as devices based on what each piece of zwave hardware reports?
FWIW: I have MQTT discovery disabled in HA and the gateway disabled (ws enabled) in zwavejs console.
Trying the zWave JS add-on out today. Seems to be beginning to resolve the nodes at an extremely slow pace.
Just going to be patient and see what happens.
Both. Ha discovers them and organizes it based on what the hardware reports.
If the only thing that you ever use MQTT for is for the zwave2mqtt platform then you don’t need the MQTT broker for your new zwave js integration. All you need is a functioning zwave js server which is provided by either the zwave js add-on or the zwavejs2mqtt add-on/container.
But it sounds like you are still using your MQTT broker for the MQTT_statestream functionality. if that’s true then you can’t remove your MQTT broker because it’s still used there.
You just won’t need it if you don’t use it for zwave js - either because you are using the zwave js server add-on or you are using the zwavejs2mqtt platform and are only using the websocket functionality but not the MQTT functionality.
But only when MQTT (+MQTT discovery in HA) is enabled correct? I wasn’t able to get anything to change in zwavejs or HA with websocket only enabled.
You can have both enabled, you’ll just have double the items if you have MQTT discovery enabled.
What I’m trying to determine is what effect the Home Assistant section of each node has when MQTT is disabled. There doesn’t seem to be any if just using the websocket to zwavejs from HA, names aren’t transferred over, etc.
I just don’t get the question.
I don’t get this at all. Are you asking about switching from using ZwaveJS2MQTT’s MQTT portion to the Zwave JS Webserver? The names and ID’s will be different.
I’m using Zwave JS & the Zwave JS integration without using the ZwaveJS2MQTT.
I’m probably not describing it well, this is my first few hours with zwavejs.
Configuration:
When I change any of the json on the right and click “update”, or delete one of the devices, should I expect any change in Home Assistant?
It seems to me that you have to be using MQTT (as opposed to websocket only) for any changes in the zwavejs panel to be reflected in Home Assistant
No, that’s all for MQTT
One of my main arguments for using MQTT rather than WS is that using e.g. MQTT Explorer it’s easy to monitor traffic on the Z-Wave network. This way you can easily see a rogue node spewing out Z-Wave messages every few seconds.
Is there a way to get this functionality with Websocket connection from HA to Zwave.js?
You can turn on debug for the integration in logger configuration. Or you can view the logs in Zwave JS addon.
Ha in VM, have to change json file(enable rgb) in ZwaveJs2mqtt when the addon is stopped. Portainer do not show addon when is stopped. Any hint how to acces the stopped addon container and edit file?
Link: https://github.com/zwave-js/zwavejs2mqtt/issues/351#issuecomment-772494729
Thanks for the answer and all your work!
Don’t thank me, I only contributed a few tests. Many other developers put in WAY more time than I did.
It’s been about 4 hours now, and I’ve just got a huge list of Nodes that haven’t been resolved. I don’t know where to go from here.
