For context, I'm running HA-Fusion as my primary dashboard, and I'm simply trying to cast it to my nest hub which is on the same network. So far, I've managed to get decently far, but I've hit a roadblock in the form of the login page. Since the nest hub doesn't have a built in keyboard outside of specific apps, I can't type in my login information to get to the dashboard I'm trying to cast. I've heard you can set the device as trusted, but so far every attempt to do so in the config.yaml file results in HA booting into recovery mode, so I'm not entirely sure what I'm doing wrong. If anyone wishes to help, just reply to this post with whatever advice you have.
#Google Nest Casting Lockout
87 messages · Page 1 of 1 (latest)
What do the log say when it boots in recovery mode?
Is your indentation correct?
The log just doesn't load, which is odd in itself, but the indentation is fine, file manager says its all checked out. I could send you my config if you like, since that's what seems to be the issue as of right now.
let me check mine and send it her so we can cross check
Gotcha
homeassistant:
auth_providers:
- type: homeassistant
- type: trusted_networks
trusted_networks:
- 192.168.0.249
auth_providers:
- type: homeassistant
- type: trusted_networks
trusted_networks:
- 192.168.0.1/32
- 127.0.0.1
trusted_users:
192.168.68.64: (User ID)
allow_bypass_login: true```
For context, if I go anything beyond /32, it boots into recovery
Because the 0.1 there you see is literally my main address, as far as I know anyway
That is your gateway address 😛
And I've confirmed multiple times that that IS the nests IP in the trusted users section, even reserved it just to be sure
Oh
0.0.0.1 is the router usually
Right, so... if the nests IP is right, and the gateway... isn't needed, then how do I tell HA that the nest is safe to login to so long as its on my home network?
- 192.168.0.1/32
Would let anyone on 192.168.0.*** connect
homeassistant:
auth_providers:
- type: homeassistant
- type: trusted_networks
trusted_networks:
- 192.168.0.249 <<<< Your Nest IP here
allow_bypass_login: true
Huh, alright lets see what happens
For context I'm using the nabu casa url since casting requires https connection protocols
Just in case that matters lol
I use a Reverse proxy, but I don't think it will matter.
The Router should give your NEst's local adress to HA on the connection attempt AFAIK
Yeah, sadly I can't use the lovelace cast method since I'm using HA Fusion, which the integrated method doesn't currently support
So I had to go this route
I used to do it with Cast All the Things
Instead of the integration
That's how I know what you are doing 😛
Nowadays I use the cast option
lmao
And tbh, I only got 2 hubs left and can't wait to throw em away
Garbage dashboards hahaha. Way too slow for nice interfaces, and many front-end things don't work on em
Like card-mod
I mean technically, but no, just the login page
If so, click somewhere in the middle toward the bottom until you hit the button
it's just not loading
Under the login buttons
I had this bug
Uh, yeah no I'm pressing everywhere and there's jack shit there
Congratulations @gloomy isle! You just advanced to level 1!
o
Mhmh. Got a screenshot of what you see on the hub?
I do but I can't post it here lol
?
can you scroll down?
Uh, I can try?
allow_bypass_login boolean (Optional, default: false)
You can bypass login page if you have only one user available for selection.
This is why that doesn't work
trusted_users map (Optional)
You can also assign which users are available to select when user access login page from certain IP address or network.
USER_ID list | string (Optional)
List of user ids available to select on this IP address or network.
???
Try this:
auth_providers:
- type: homeassistant
- type: trusted_networks
trusted_users:
- 192.168.0.XX:UserNameToLoginOnTheNest
trusted_networks:
- 192.168.0.XX <<<< Your Nest IP here
allow_bypass_login: true```
This should work If i understand the docs properly
But I took 4 dabs since I woke up, so god knows
This is their sample config:
homeassistant:
auth_providers:
- type: trusted_networks
trusted_networks:
- 192.168.0.0/24
- 192.168.10.0/24
- fd00::/8
trusted_users:
192.168.0.1: user1_id
192.168.0.0/24:
- user1_id
- user2_id
"fd00::/8":
- user1_id
- group: system-users```
. . .
That's not good
That's... also... not good
auth_providers:
- type: homeassistant
- type: trusted_networks
trusted_users:
- 192.168.68.64:(HA Username)
trusted_networks:
- 192.168.68.64
allow_bypass_login: true```
I think it's right, but just to be sure
That is the issue
F u c k
The http_host
Trial and error I guess lol
Yeah I uh, they're saying to remove http from your config but uh
I don't have that... so....
Can you share your entire configuration.yaml?
Sure
It's pretty fuckin short
default_config:
# Load frontend themes from the themes folder
frontend:
themes: !include_dir_merge_named themes
automation: !include automations.yaml
script: !include scripts.yaml
homeassistant:
auth_providers:
- type: homeassistant
- type: trusted_networks
trusted_users:
- 192.168.68.64:A(HA Username)
trusted_networks:
- 192.168.68.64
allow_bypass_login: true```
Oh boy