[supervisor.api.ingress] Ingress error: 400, message='Invalid response status' on a .0 address?

Configuration
1

So I’ve started seeing these errors in my log:

21-04-19 19:12:39 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=V-7NBjfDUYjDI9w_AAAE’)

When I search, I find most similar hits to be associated with Z-Wave JS or ZWJS2MQTT and I have been working to add those, so I’m sure there is an association with the websocket stuff they use. What’s more perplexing in my case, is that this is tied to a .0 address rather than a specific container IP, and I have no idea why it would do this in the first place or how to fix it. Anyone have any ideas on either?

2

@BurntOC I’m having the same issue when trying to run zwavejs service calls from Appdaemon. Have you had any luck finding a fix?

3

I’m getting the same errors. New build on Proxmox using “haos_ova-7.0.qcow2” and using a ZOOZ S2 ZST10. I also have random zwave devices getting reported as “dead”. A ping wakes them up. Not sure if this is related to this issue or not.

4

I’m getting this message. Any update?