Static IP on HA Green?

[jovial crow]

Hey all - I want to assign a static IP on a network w/o DHCP. I have searched, but this is silly - I don't see any way to set the IP configuration:

What am I missing?

Thanks!

[vocal prism]

That is odd, It should be an option there. Could you show a screenshot of your about page please?
settings->about

[jovial crow]

I thought so too -

[vocal prism]

Ok so you have a bug that happens sometimes with the green where the supervisor has problems and core thinks its a container install because it cant find the supervisor.

[jovial crow]

OK - just set it up, nothing configured yet, so if I have to nuke it thats fine

[vocal prism]

You need to perform a safe shutdown of the green and then power it up again (dont just pull the power to cycle it).
Press the power button on it to start a shutdown. after a moment the OS should shut down then you can power it on again.

This should make the about say that it is on HAOS and also the network settings should work correctly.

[jovial crow]

ohhh ok it thinks its running in a container so naturally it can't configure ip

[vocal prism]

Exactly this.

[jovial crow]

weird bug 🙂

OK it shut down properly

[wild wigeon]

Press the button for about 6 seconds to initiate the shutdown.
Only cut the power when all LEDs turned off.

[jovial crow]

I tapped the power button and it shutdown

it took like 10 secs and the yellow heartbeat went dark

[vocal prism]

Hopefully should be ok when it reboots.

[vocal prism]

If your interested, The trigger seems to be if you plug it into power before attaching a network cable. I am not sure on the specifics but this seems to make the supervisor loose its mind.

[jovial crow]

You know... I think I may have done that in that my network cable wasn't all the way in after it powered up

[vocal prism]

There we go, That is looking better. you will also likely get a OS update pop up now too. 🙂

[wild wigeon]

Sidenote: You should update the OS to get a Linux vulnerability fix.

[jovial crow]

yup 16.3 -> 17.3

Updates pretty quick

[vocal prism]

Yup, The green is a nice little device.
This bug crops up for a few people and they don't realise until they try to do something that requires OS and its missing.
FYI: In general I recommend setting static IP's on the DHCP server side instead of the client side to centralise but whatever works for you. Just be sure to make sure there is a DNS server set correctly otherwise you will get a new problem. 🙂

[jovial crow]

All good - I run AD DNS (don't ask) in home so those DCs are set.

Now I just need to figure out these ZBT2 and ZWA2 things

[vocal prism]

Now I just need to figure out these ZBT2 and ZWA2 things
For the most part: plug them in -> see them on the devices page -> follow instructions.
There is a little bit more that happens but that will get you started in any case. 🙂

[jovial crow]

I picked up a powered USB hub so I should probably do all that jazz as well

[vocal prism]

Sounds like you have got everything in hand tbh. You just ran into a stupid bug which tripped you up for a bit.

Good Luck with it all, If you have any other issues then come on back and start a new thread. 🙂

[jovial crow]

Thanks for your help!

[vocal prism]

No worries, Happy Automating. 🙂

[jovial crow]

One other quick Q - the ZBT-2 s ays zigbee or thread, but one or the other yah? Can I have two ZBT-2 so I can do both?

[vocal prism]

It is one or the other yes, And yes you can have 2 if you want.
Although unless you actually need thread for something you should try to avoid it tbh...
Also: If you have 2 then you should ensure you place them at least 25cm apart (2 wavelengths at 2.4ghz).

[jovial crow]

OK I will avoid thread for now

[jovial crow]

Any chance I can get your take on one more issue? So originally HA Green pulled a DHCP of 192.168.51.91 and so it was discovered with homeassistant.local:8123 to that IP. I changed the IP to static at 192.168.50.13:8123 works. On my PC, http://homeassistant.local:8123 works. But on my android (pixel 9 pro) phone when I open the app and let it find the HA while on the same network segment, it finds it at http://192.168.51.91:8123. So somehow mdns is cached or something on the phone. I deleted the cache/storage for the app but no change.

In Chrome on the phone it resolves to the new, current IP (192.168.50.13)

[wild wigeon]

You likely have to adjust the mm server settings in the Companion app.

If it has already been configured.