I wasted most of today attempting to get a Home Assistant Green device operational - and failed. This is a semi-custom SBC designed to run Home Assistant in a containerized system on top of a simplified Linux system. It downloads and deploys it’s image automatically on first boot, but the Docker supervisor basically refused to get an address, and subsequently anything that required the time: SSL, websites, etc. failed and the container(s) failed to deploy properly.I ran through several resets and failed flashes before I gave up. Every time I reset the device, it would give itself a new client ID and thus request a new IP address: https://pic8.co/sh/31YebQ.png
I’m currently running a RB2011 which is a few firmware revs behind. (I know, I’m bad and I realize it.)
I’m going to assume that only the current ID and it’s associated address will be canon at the time it’s in effect - but does a device doing this cause issues for itself? If there’s a situation where the client ID doesn’t get passed, would the router do something like try to assign it one of the other addresses, or will it give it a completely new address because the client ID is “different?”
I’m not trying to solve anything with the HA unit, that has to go back. They’re just doing odd stuff and it doesn’t seem to like my setup. I’m just curious as I’ve never seen a device do this, at least not one that wasn’t one of those Chinese SBCs that didn’t have a proper MAC address set.