After moving to Z-Wave JS to MQTT add-on I'm getting Ingress Errors

Configuration Z-Wave
1

I’ve recently moved to the Z-Wave JS to MQTT so that I can use its Z-Wave control panel with Z-Wave JS.

I’ve noticed that I’m now getting Ingress errors showing up in the log of the form:

21-04-04 08:07:42 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=y0gfQ6UWAgrZxPCBAAA4')
21-04-04 08:34:07 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=5QT93fX3AXdMyt0QAAA6')
21-04-04 08:34:08 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=-n1GGeF9YD4b8cCXAAA8')

These usually result in the Z-Wave web interface not loading properly. Is that the only thing, or should I be more worried about these errors? Thanks.

System Health

version core-2021.3.4
installation_type Home Assistant OS
dev false
hassio true
docker true
virtualenv false
python_version 3.8.7
os_name Linux
os_version 5.4.83-v8
arch aarch64
timezone Europe/Amsterdam
Home Assistant Community Store
GitHub API ok
Github API Calls Remaining 4933
Installed Version 1.11.3
Stage running
Available Repositories 841
Installed Repositories 11
Home Assistant Cloud
logged_in true
subscription_expiration 19 April 2021, 2:00
relayer_connected true
remote_enabled false
remote_connected false
alexa_enabled true
google_enabled true
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
Home Assistant Supervisor
host_os Home Assistant OS 5.12
update_channel stable
supervisor_version supervisor-2021.03.6
docker_version 19.03.13
disk_total 109.3 GB
disk_used 9.1 GB
healthy true
supported true
board rpi4-64
supervisor_api ok
version_api ok
installed_addons File editor (5.2.0), Samba share (9.3.1), InfluxDB (4.0.3), Terminal & SSH (9.1.0), Grafana (6.2.0), Z-Wave JS (0.1.16), Z-Wave JS to MQTT (0.9.1)
Lovelace
dashboards 2
resources 8
views 4
mode storage
1 Like
2

I have the same problem.
Following this topic

1 Like
3

Same here

21-04-08 08:48:17 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=SgYsgootyWWNs2ORAAAa')
21-04-08 08:48:46 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=0Cgl31cy-sPAgnzeAAAc')

but it doesn’t seem’s to affect anything…

4

Same here, watching this as well.

5

is this this error?

6

Same problem here.

7

I’m also encountering this when using “Heal” on a dead node.
zwavejs2mqtt: 4.0.0
zwave-js: 7.3.0

Watching issue, I’ll post more info whenever I have time for this (as I’ve replaced all my valves today, and have a few more to go, that might be later this week)

8

I’m seeing this as well. Has anyone found a fix? Or what the cause really is?

9

Also seeing this

10

Same issue here.

11

Same issue Here after changing Zwave.js to mqtt

Happends when opening the Gui interface

1 Like
12

same. following.

13

same here:

Did anybody report this issue on Github?

zwavejs2mqtt: 5.8.0
zwave-js: 8.4.1