New to HA - having issue with mushroom room select
I have my HA setup on a pi4 running on an IOT vlan and acess it from phone/tablet etc from an internal vlan that has a firewall rule setup to allow 8123 traffic to pass. I can get to most of the stuff but I have a dashboard that is using the mushroom select card with a room helper and when I put my phone or tablet on the IOT network it works like a champ. When I move back to the internal network I will get an error message “type: custom:mushroom-select-card entity: input_select.room_select name: Room icon_color: accent”
Segmented networks are not officially supported within HA.
HA is designed and expects a flat subnet to work as intended.
This is because every segmented network is different for IP’s and number of segments and firewalls and sharing rules and about 650495849085 other things.
This does not mean you can’t use them or that they can’t be made to work, it means that to get them working you are the support structure on your own subnet(s). Consider it Advanced mode…
That setup sound like it is supported, since the HA is on the IoT network.
However the error is not that descriptive. Something is either missing of the text or this is not an error and you need to log elsewhere, like the logs, for one.
Yes the HA running on Pi is on the same IOT network as all my IOT devices. The segmentation is coming from trying to access the HA application on my iOS devices or from my laptop which sit on another LAN network for internal stuff (NAS etc). I have the firewall set to let traffic from LAN to IOT pass on 8123 but access is spotty and slow to load the HA app on iOS. I also get the error mentioned before when it is trying to load the dashboard that is leveraging the mushroom select card for what room to bring up.
I have another question. I installed all this off the raspberry pi setup and it put everything inside docker which I am not super familiar with. If I do a backup of everything I have and then just install ubuntu on the pi and then install HAOS on that (much more familiar with ubuntu) will I be able to perform a restore of my current config? Thanks.
Okay, then what is the thing with Docker?
HAOS have addons where everything is handled.
When you back up then everything is backed up, but installation on Ubuntu requires a Core installation to avoid Docker and that is much more complex in maintenance, both of requirements on the OS and on extra functionality that was before handled by HAOS in addons.
It gets back to trying to figure out why everything is so slow when trying to connect from my iOS devices. When I log in to the pi device I can do a docker ps and see all the containers that have been installed for home assistant plus the add-ons that I installed. There seem to be no tools available like tcpdump and no ability to install any packages via apt. This is all new to me so it’s a learning journey.
When you ‘move’ the machine to the other network. How?
Change IP? Host name?
Reason I ask is browser will see the changed ip as a different website. So if you were internal. Then moved to IoT, And got it to work. Then moved Back to internal.
If you made changes while on IoT and moved back to internal you may run into caching issues on the browser. And it would exhibit like you’re describing.
So I’d clear the browser cache whole connected internal and see if that clears it up. There s nothing inherent that should change when you move the machine between subnet that should cause it. I’m pretty sure that part is just a caching issue.
Sorry I should have been more clear. If I switch my iPhone to the IOT wifi I can use the HA mobile app with no issues, everything comes up fine and I can select which room I want to control etc. If I put it back on my home wifi then that is when it gets super slow and I get those mushroom card errors where the room selection goes away because it is leveraging the mushroom card. I am not moving the HA pi device between networks at all.
