As the title mentions my modem for some strange reason reboots when I’m looking (for too long?) at my home assistant webpage from within my network. This doesn’t happen when I visit it from outside the network.
At first it seemed to happen most often with the iframes I had in homeassistant (all showing grafana dashboards) but now it also seems to happen when I check other stuff as camera’s or even the home assistant log…
My configuration is internally without ssl, but externally I use an reverse nginx proxy which applies SSL and I use duckdns. Both internally and externally I use the duckdns link to access my installation.
I have no idea where I can even start debugging… I called Ziggo (the ISP) and they can’t help me, homeassistant seems to stay online during all of this but just inaccesable since the modem is down. Also no errors are shown. Has anybody experienced something similair? Or have any pointers where I could take a look?
I’m running home assistant 0.95 in a virtual env with python 3.7.3 on a raspberry pi 4 which is hooked up directly to the modem.
these are inaccessible by me… So I called the ISP and he told me he can’t see a whole lot and only that the router turns of and back on again several times lately… (like multiple times a day)
Haha I don’t really want to pay 4 times more and or get really slow adsl speeds. Thanks for the help though ;-p and having ur own modem us not allowed unfortunately…
You can ask Ziggo to put the connectbox in Bridge mode and use your own router. This will probably solve your issue. But imho you’re looking at the wrong forum as this is not related to HA.
Thanks for your reply. The problem is that it is happening due to Home-assistant. Only when I visit homeassistant I have this problem. It doesn’t seem like something that could be able to happen with Home assistant. Appearantly it does something wrong…
you want bridge mode… if you don’t want Ziggo to snoop at your traffic, and be able to set all router options your self. Ziggo has diminished your self control extensively, so buy a good router and take control.
If the Ziggo modem would be rebooted because of HA, you could then start investigating.
Seems an odd problem though, which shouldn’t be happening spontaneously. Did you configure the Ziggomodem in HA, and do you by any change have scripts or services pointing at the modem?
Allright thanks for the advice I’ll look into buying a new router and put it in bridge mode. Any tips would be welcomed but ofcourse I will also check another forum (tweakers) for that :)! Kinda was looking for a reason for that anyway :P!
No HA doesn’t interact with my modem at all, didn’t even knew that was possible… And I have no custom scripts running.
This is your assumption… A quick search will show you other people have (had) this problem as well and the issue was related to the number of connections which made the modem to reset. This is in no way related to HA.
believe it or not but i have exactly the same problem, when there is a lot more load within home assistant, like ping, opening a big log page, open a ipcam stream my Ziggo Connectbox reboots. I still have not been able to solve it. will have to try to put the modem in bridge mode.
Edit:
I now know for sure that the Ziggo Connectbox is the cause. I have now placed the modem in bridge mode and my own router behind it. Everything in Home Assistant now runs much smoother and the camera has a smooth live feed without crashing the modem.
I’ve got more or less the same problem, but this is not HA related. I have a Pi 4 running Raspbian with OpenMediaVault and HASS.io.
As mentioned here the problem is with the Ziggo ConnectBox (a rebranded Compal device) in combination with a Raspberry Pi 4. There’s something the Linux networking stack does on Pi 4’s that the Compal modem/router does not like.
Related issues that I’ve experienced include:
Running Borg Backup from a laptop to the Pi using it’s DuckDNS address (which routes the trafic through the modem) outright crashes the modem. Borg Backup uses SSH to connect which is nothing out of the ordinary. Running it using the direct LAN IP address of the Pi works fine.
My Fedora Linux laptop’s WiFi connections stall a few seconds after connecting to the ConnectBox provided WiFi since the Pi 4 is connected. Restricted to ethernet for now.
The Pi regularly loses ethernet connection. Worked around this issue by using cron to execute a custom script ever minute that pings the router to check for connectivity, and bring the interface down and back up if it does not respond.
@toMeloos and others:
I’ve noticed this issue also with an entirely different setup, not with a rPI running HA. In my case, it was accessing a couple of Panasonic security camera’s over HTTPS, while using a WiFi 6 Nic or a wired connection to the remote destination.
As far as I’ve diagnosed and reproduced it with my local CB it has to do with NAT Loopback, something triggers the box to be stressing out and within seconds the modem reboots.
Please report this issue over at the Ziggo Community website and ask to swap it for an Ubee (Non-Wireless) as this modem doesn’t have this issue.
Ziggo appears to be aware of this, but due to the specific situation, and only very few reports of this problem it’s on their list as being a “single customer incident” I’ve been told.
So if we all would report such, then maybe it’s getting a higher prio assigned.
I’ll look into buying a new router and put it in bridge mode. Any tips would be welcomed but ofcourse I will also check another forum (tweakers) for that :)! Kinda was looking for a reason for that anyway :P!