The other day my WiFi network went down and with it, I lost access to my Zigbee network?* Is this normal or is this a sign of a massive issue?

*When I checked the Raspberry Pi running Home Assistant, all devices showed as unavailable.

  • @Kuinox@lemmy.world
    link
    fedilink
    English
    94 months ago

    Why did your wifi went down ?
    Some wifi and zigbee are on the same wavelength, if someone was jamming it (this is illegal), both can be taken down like this.

    • @sabreW4K3OP
      link
      English
      44 months ago

      There was a fault in the neighbourhood and Virgin make it so when their routers lose connection to the web, they kill all connections. It’s annoying!

        • @sabreW4K3OP
          link
          English
          14 months ago

          So if my internet goes down because there’s an area fault, I can’t, for example, scream movies from my NAS, because the router just refuses all connections. It’s infuriating. Especially as the local Internet drops constantly due Virgin selling over capacity.

          • Mbourgon everywhere
            link
            fedilink
            English
            24 months ago

            Is it worth it to double-NAT, and run a router between your internal network and their internet box? Then your router is doing the internal routing and possibly DNS too. It’s not perfect, but it might be worth it if the internet drops that much.

            • @sabreW4K3OP
              link
              English
              24 months ago

              This is my plan. I’m gonna get a NanoPi to do the routing.

  • @beeng@discuss.tchncs.de
    link
    fedilink
    English
    6
    edit-2
    4 months ago

    Your wifi went down or your internet connection?

    Sounds like from your comments that you mean internet.

    Zigbee does not rely on internet, but does rely on a local connection to your mqtt server which may be on another machine (ideally not), and if these machines are connected via wifi (ideally not) and your wifi went down, then yes you can lose functionality.

    • @sabreW4K3OP
      link
      English
      04 months ago

      My Mosquitto is on the same Raspberry Pi. But I’m starting to think it’s because I may have used the hostname in the config.

  • @Willem@kutsuya.dev
    link
    fedilink
    English
    64 months ago

    How is your coordinator linked to your home assistant?

    For example if you use Zigbee2MQTT and you have either Zigbee2MQTT or Homeassistant pointing to the internal ip of mosquito (192.168.1.11 for example) and your router goes down (with dhcp), it’s possible it cannot communicate anymore.

    This isn’t the case if it’s all running on the same box using localhost as address, running it in a docker network or when you run ZHA however.

    • @sabreW4K3OP
      link
      English
      24 months ago

      I think it didn’t work when I tried localhost, so used pi5.local

      • @Willem@kutsuya.dev
        link
        fedilink
        English
        24 months ago

        that uses mDNS, which in some cases requires your router to be online to be able to resolve it to a ip. If part of your internet disruption was your router going down, it would explain the issue

        • @sabreW4K3OP
          link
          English
          24 months ago

          Ahhhh, that explains it then. I so need to hurry up and build my router.

  • Avid Amoeba
    link
    fedilink
    English
    4
    edit-2
    4 months ago

    This is odd and I don’t think it should happen. You could try to reproduce it and gather some logs.

    • @sabreW4K3OP
      link
      English
      14 months ago

      I’ll play around with it tomorrow

  • @Jakor@lemmy.world
    link
    fedilink
    English
    34 months ago

    I had something similar (although probably unrelated) happen last week. All of a sudden my router went offline and nothing was getting an internet connection. Sonoff coordinator lost connection with all zigbee devices went unavailable at the same time. Tried rebooting my home assistant pc, router, unplugging sonoff antenna, switching Ethernet ports, etc without luck.

    Power cycling my Ethernet switches fixed it immediately. No idea why that did the trick. This has never happened before. I’m on Verizon fios if that matters.

    Posting here in case it helps someone identify a common thread/root cause for OP and me, because I thought it was bizarre that an Ethernet switch would ever need to be power cycled!