• 0 Posts
  • 184 Comments
Joined 1 year ago
cake
Cake day: June 10th, 2023

help-circle
  • I have a bunch of z-wave, too. Z-wave and Zigbee, I think, only broadcast when needed. That’s why they’re much more battery friendly. If they’re plugged in, they do more listening and re-broadcasting to do what you’re talking about.

    Wifi has, relatively, a ton more traffic. DHCP renewals, keep-alive messages, and basically always listening all the time to see if something is looking for it. That being said, these smart switches use very little data overall. Unifi shows them using about 700 bits per second, which is 0.0007 Mbps.


  • Actually now that I think about it, without more than 1 access point, everything will all be on the same channel. I have 3 different channels due to having 3 different access points, all set to individual channels. This reduces conflicts (more than one device trying to use the same channel at the same time, a weakness of wifi).

    As of right now, my “busiest” access point has 23 devices connected to it on 2.4 GHz. The AP is reporting that channel being 23% utilized. Still, I wouldn’t want anywhere near 100% utilization. Things would certainly slow down as it gets higher.

    Newer versions of WiFi reduce this problem, but smart devices use whatever is cheap and effective. 2.4 GHz travels better through walls and has better range compared to 5 GHz, but 5 GHz is faster and has more available channels.


  • I currently have 54 things connected to WiFi in my house. Only 10 of those are connected to 5 Ghz. The rest only support 2.4.

    With one good access point it would probably work no problem. I have 3 access points due to the layout of my house.

    Use channels 1, 6, and/or 11. Those are the only channels that don’t overlap with other channels. If you live in a dense area, 2.4 gets tricky. 5 is easier, because more channels.











  • I installed MagicMirror onto a Raspberry Pi using a pre-made Magic Mirror OS image (can’t remember where I got that, but I think it’s relatively “official”, so maybe their website? It comes ready to go with Docker and everything you need set up.

    Then I installed this https://github.com/pelaxa/MMM-ImmichSlideShow and configured it.

    I actually found some additional configuration options by going back in the chain to the project it’s based on (linked at the top of the readme). Their documentation included some additional stuff that actually works with MMM-ImmichSlideShow. Edit: Looking at my config again, and all the stuff is in the MM-ImmichSlideShow documentation now. Maybe they updated it.

    Then I hooked up an old monitor, put it in vertical mode, and that’s it.

    It was actually kind of difficult to figure out how to get the display to work in vertical mode. A lot of old forum posts are the “old” way of doing it. I ended up making a cronjob that runs 60 seconds after boot and runs some command that rotates the display. I’ll dig it up if you need me to, but since MMM-ImmichSlideShow is still broken it’s not turned on right now so I can’t check it. Here’s the line from my crontab to rotate the display: @reboot sleep 60 && DISPLAY=:0 xrandr --output HDMI-1 --rotate right




  • Mine was having some weird problem with docker, I think it must be a docker bug. Basically it put the Wanderer stuff at the very bottom of the routes (running “sudo route” on Debian lists the routes). The last entry in the routes table needs to be eth0 or the equivalent so that stuff can loop back to the beginning of the list. At least that’s my understanding.

    So anyway, to get around that bug/limitation I had to create a static docker network which I called “wanderer-static” using docker network create --attachable -d bridge --subnet 172.28.0.0/16 --gateway 172.28.0.1 wanderer-static. Choose a subnet that’s not being used already.

    Then in the docker compose file, point everything at that network by:

    Removing

     networks:
       wanderer:
         driver: bridge
    

    Adding

    networks:
      wanderer-static:
        external: true
    

    And finally, pointing each service to that network. Under each service you should have:

        networks:
          - wanderer-static
    

    I also had to update the ORIGIN and whatever else to http://wanderer-static:7000, etc.