I reset the thermostat today and it appears to work perfectly.
1 Like
Hi,
Did anyone figure this out?
I migrated from the deprecated “Z-Wave 1.4” integration to the “Z-Wave JS” integration and “Z-Wave JS to MQTT” addon approximately 2 weeks ago, and so far I am really happy with it. (Thanks a lot to everyone involved in making this happen, it’s really appreciated!)
However I notice I also get these error messages in the Supervisor log, it seems to happen each time I click into the Z-Wave JS Web UI.
21-04-13 11:00:35 ERROR (MainThread) [supervisor.api.ingress] Ingress error: 400, message='Invalid response status', url=URL('http://172.30.33.0:8099/socket.io/?EIO=4&transport=websocket&sid=RDkILXzvvMxPti8WAAAA')
21-04-13 11:09:26 ERROR (MainThread) [supervisor.api.ingress] Ingress error: 400, message='Invalid response status', url=URL('http://172.30.33.0:8099/socket.io/?EIO=4&transport=websocket&sid=mkS6hzbGuPlM8TN8AAAC')
21-04-13 11:18:47 ERROR (MainThread) [supervisor.api.ingress] Ingress error: 400, message='Invalid response status', url=URL('http://172.30.33.0:8099/socket.io/?EIO=4&transport=websocket&sid=kSWXk-XucP5CIqIzAAAE')
21-04-13 11:21:30 ERROR (MainThread) [supervisor.api.ingress] Ingress error: 400, message='Invalid response status', url=URL('http://172.30.33.0:8099/socket.io/?EIO=4&transport=websocket&sid=yPZGmZPBAzrY2OzjAAAG')
When I first noticed the error messages I tried removing and installing the “Z-Wave JS to MQTT” addon, but it did not help.
Today I also upgraded everything to the most recent versions, but the error messages still appear.
- Home Assistant OS 5.13
- supervisor-2021.04.0
- core-2021.4.4
- Z-Wave JS to MQTT 0.11.0
Thank you for any help regarding this.
Ever since upgrading to Zwavejs2mqtt 3.2.0 and above, my switches from many different brands take forever to receive on and off events. In Node Red you can see it just sitting there as “Sending” until it eventually sends. Before events like this were nearly instantaneous. Anyone had issues like this?
Any sensors like motion and door sensors still seem to be instant, only switches are lagging.
I restarted the host, which didn’t help. After I tried downgrading to v3.0.3 but it wouldn’t initialize. I then upgraded back to v3.3.0 and it seems to back to normal. Not sure what fixed it but it appears to be working now.
Has anyone had success with the everspring leak detector? I have one where battery level and low battery entities seems to work, but the alarm entities are disabled.
sorry if this has been covered above, (searched but didnt find):
can’t we set the units on the z-wave devices integrations manually?
we can change names, entity_id, icon, but not unit?
Asking because I like to streamline with the other units in my system (and have auto-entities create nice overviews…) need Watt instead of W in this case
We might be able to customize, but would prefer if this could be done I the settings of the device/entity:
That’s what customization is for.
Sure, I suggested that already. But we can set the other parameters directly in the entity config, without having to customize. So why not add Unit?
I have an Everspring ST812. I did have some trouble getting it setup, but it does work now. I only have a binary sensor and battery sensors enabled. Try refreshing that node with the module awake?
Thanks, will do.
This isn’t something that zwave js implements. These cards & configuration on the devices page are auto generated by the core. Make a feature request.
I hooked up a zooz zse19 over the weekend. All of the sensors work, but I can’t figure out how to use the tones that are on it.
Any suggestions?
yes on the eaotec siren you do it through service set_value like below… try it in dev/services, be sure to use device and not entity
service: zwave_js.set_value
data:
command_class: '121'
property: toneId
value: 2
endpoint: '1'
target:
device_id: f90d67f9793224b8fe1a3676e7fe15d3
Has anyone figured out how to best delete the device cache or re-interview a specific node in zjs integration? I added a device through zjs2m but not all of the entities are coming across through zjs integration. (LZW36 Inovelli not bringing over energy sensors).
I assume samba share and deleting a cache file will reset device info? Will this reset all of my entity naming?
Click the advanced button:
Then click interview:
1 Like
or wait until beta assuming Add UI for Z-Wave JS Device Reinterview by cgarwood · Pull Request #8957 · home-assistant/frontend · GitHub makes it in and do it direct from HA 
2 Likes
I’m using ZJS not ZJS2M server, I’ll try to specify in the future.
Of note, I did try to disable ZJS integration (takes down ZJS server add-on as well), spool up ZJS2M, and re-interview the node, and ZJS2M get’s the sensors and shows them, but ZJS on restart still isn’t seeing it. I believe it has to do with the ZJS integration cache in HA, and not the server.
THIS is what I’m looking for! Thank you! I can work without energy monitoring in the meantime!
Any idea how I add the tcp://: to the add-on config? If I try and edit the YAML file in the “Configuration” “Edit in YAML” page, every time I edit the device field it resets it back to a default /dev/ttyS0 setting.
I don’t think it allows you to do so. Switch to the zwavejs2mqtt community addon if you need that functionality.