Home Assistant on Raspberry Pi4 is blocking my Bell Aliant Fibreop TV

Configuration
1

I’ve had some issues with my Bell Aliant FibreOp TV service the last month or so and had the techs out yesterday finally to try and solve it. In doing so we replaced hardware and found that when my raspberry Pi4 with Hassio running on it (hardwired and I’m also paying the Nabu subscription) is connected and working properly, it randomly will somehow kick the FibreOp TV (which is also hardwired) off the network and it will not reconnect until I unplug my Pi4.
Has anyone encountered such a thing before? I’ll admit I’m not the most tech savy but I had this all running for almost a year and this just started over the last 2 months or so and Home Assistant has been running great. I cannot unfortunately pinpoint exactly when it occurred. Any suggestions would be greatly appreciated!

2

A little more info, The specific IP addresses for the FibreOp TV receivers are reserved addresses. It’s almost like the Home assistant Raspberry Pi is blocking those 2 IP addresses from accessing the router.

3

This happened to mo with another hardware/software (not with HA).
Thats why i prefer in some devices use static ips instead of dhcp.

4

So in your case it was a non static IP attempting to take over a reserved one? I just assumed that the reserved one was exactly that… reserved… So frustrating when you’re not versed in all this stuff…

5

Yes. Probably a bad implementation on the broadband routers company.
When the reserved device was off for a while , another one took the ip address.

6

Sort your DHCP server so it doesn’t allocate those addresses then.

2 Likes
7

So I have the two receivers IP addresses reserved, I also have the Pi reserved, and it died again this morning at some time… So I checked the logs and this is the only thing showing in the home assistant logs…

"2020-10-26 01:34:34 WARNING (zeroconf-ServiceBrowser__googlecast._tcp.local._279) [homeassistant.components.cast.discovery] setup_internal_discovery failed to get info for 85ccc078-0bc5-447a-90c6-b7af810c4de1, Google-Cast-Group-85ccc0780bc5447a90c6b7af810c4de1-1._googlecast._tcp.local.

2020-10-26 02:41:33 WARNING (zeroconf-ServiceBrowser__googlecast._tcp.local._279) [homeassistant.components.cast.discovery] setup_internal_discovery failed to get info for 85ccc078-0bc5-447a-90c6-b7af810c4de1, Google-Cast-Group-85ccc0780bc5447a90c6b7af810c4de1._googlecast._tcp.local.

8

AND, After reviewing the router logs, it has this error happening every few seconds… DNS lookup errors… Now as soon as I unplug the Pi, these errors stop as well…

2020-10-26 11:40:55 ERR DNS DNS name resolution failure (emcmdbtwmx.iga.bz)
2020-10-26 11:40:55 ERR DNS DNS name resolution failure (hjpliyurfesl.ig.bz)
2020-10-26 11:40:55 ERR DNS DNS name resolution failure (ujaxnzlnsu.ig.bz)
2020-10-26 11:40:55 ERR DNS DNS name resolution failure (emcmdbtwmx.ig.bz)
2020-10-26 11:40:57 ERR DNS DNS name resolution failure (INVESTO-90NLRTE.iga.bz)
2020-10-26 11:40:57 ERR DNS DNS name resolution failure (_kerberos._tcp.WinnipegSite._sites.dc._msdcs.iga.bz)
9

So which machine is looking for those apparently non exsitent dns addresses?

10

Are you running a DNS server on the raspberry pi? eg pi-hole, adguard etc?

11

I am not that I’m aware of. I stopped using HomeAssistant for a while because of this, I just installed a fresh instance of it yesterday and again, it’s hijacking my internet. So frustrating and I don’t know what to do.
Anyone have a recommendation on what information I should provide to try and troubleshoot this? I’d love to get Home Assistant working again for me.
Thanks

12

No idea, perhaps explain what you mean by this!