I have been playing with this and and was getting a black screen after a period of time/not being able to recast
have noticed if i cast the same view/dashboard twice in a row the second time around it just casts a back screen but if i cast a different view its loads fine
Anyone else have the at issue?
I’ve been slowly moving my config from yaml to the UI. I found that once I moved external_url to “Settings > System > Network”, casting via a service call no longer worked. At this point it would produce “unable to connect to the Home Assistant Websocket API”. This is despite the fact that using https://cast.home-assistant.io/ to cast continued to work. To be able to call cast.show_lovelace_view successfully, I had to move external_url back into “configuration.yaml”. Have others found the same?
I use the Home Assistant Cloud and this setup never configured the external url in configuration.yaml and this service seems to need it
I had to add it manually, this should be in the documentation
homeassistant:
external_url: “https://abc123.ui.nabu.casa/”
Also, make the path and dashboard instructions easier, all you need is in the URL of the view when you navigate to it. This is simple enough for anyone to understand
https://abc123.ui.nabu.casa/{dashboard}/{viewpath}
Did you figure this out? This is my concern as the wife uses this Hub regularly and isn’t going to want it returning to HA while she’s there.
Sorry I am much confused. I have
my url is
to
I set up https://cast.home-assistant.io/
but it doesn’t work from there either, just says connected but unable to find view
Hello all,
Casting to my Google Nest Hub 2 is working. But i encounter problems with casting multiple views.
In my main view i have created links to some rooms or eg the lights.
When my main view is displayed, and i touch the link to the lights, the cast jumps to that view.
In these views i have a button to jump back to the main view.
But for some reason the jump back does not work. I have created in the lights view two different buttons, Each button with an different link back. See the snippets of code.
Doe anyone has an idea what i am doing wrong?
Main view:
type: custom:mushroom-template-card
primary: Lampen
secondary: ''
icon: mdi:lightbulb
icon_color: amber
layout: vertical
tap_action:
action: navigate
navigation_path: /g-home/lampen
Lights view, button to return back to main view, version 1:
type: custom:mushroom-chips-card
chips:
- type: action
tap_action:
action: navigate
navigation_path: https://192.168.178.221:8123/g-home
icon: mdi:arrow-left-bold-outline
alignment: justify
Lights view, button to return back to main view, version 2:
type: custom:mushroom-chips-card
chips:
- type: action
tap_action:
action: navigate
navigation_path: /g-home
icon: mdi:home
alignment: justify
So, jumping to an other view from main view works, but jumping back to the main view is the issue.
Kind regards, Bert
I found a solution by using an other card (custom:mushroom-template-card) for the return to the Home View, which works!
Hi all, I am trying to cast my Lovelace dashboard to a Google Nest Hub. And run in to an error. Hope someone has a good idea!
I go to https://cast.home-assistant.io/ and enter my nubu.casa url.
Then I log in to my HA. and select the appropriate google nest hub. Then the Google Nest Hub indicates that it is connected. And I get an overview of my HA Views. When I click one of my views it gives an Error on the Google Nest hubs Display
“Error: Cannot show Lovelace because we’re not connected to the same Home Assistant instance.”.
it’s a bit strange because I do see my own HA views on de cast webpage it looks like the same instance. Maybe i have to contact Nubu Casa for this problem? Maybe someone else has run into this problem?
Hi! I think this automation is great.
I like to watch my dashboard during daytime. But during nighttime it lights up the entire room where I have my Google Hub.
How can I make the automation to be active just from 7:00 to 23:00?
This works for me, but doesn’t seem to recast every 9 minutes to avoid the picture timeout. Looking at the traces, I can see it triggered at the 9 minute mark, but completely bypasses the recast because of the conditions. This leads to the picture card timing out for my camera.
Does the https://cast.home-assistant.io browser page have to remain open for this to keep functioning? It seems like if I close the tab that initiates the cast it will eventually stop working after a native google home task is preformed.
Hey all, I’ve recently created a new HACS integration to continuously cast dashboards to multiple different Chromecast displays.
Features:
Cool HACS integration is there anyway that you can think of to store the last view of a dashboard that was used and recast that instead of casting a specific view.
For Clarity sake say I have a dashboard that has 5 views. The first view is cast to a google nest hub. Someone then switches to the 5th view to control some sonos speakers or something. Then somebody uses a voice command to the hub to turn off some lights. The hub will then get the first view recast to it after the interruption from the voice command. Would there be way to broadcast the last view which was the 5th view in this case
I can try to implement this, I have a couple of ideas. Can you send me what your views look like in the URL? Just the end part
sorry havent got back to you. Just working some shift work
Wow, what an awesome investigation and solution!
Love it! I had the same issue, and also assumed that kind of problem. Thanks for sharing! Saved me now some time.
And again: VERY VERY nice solution!!
I struggled a long time to cast Google Calendar to my Nest Hub (it casted the calendar — but cleared all entries from Google, weird). But now that is working too.
Hi @b0mbays,
Hopefully, I may bother you with this…
I had a working casting of dashboards, but after being away for vacation and updating to HA 2023.4.5 and OS 10.0, i cant get casting my dashboards working anymore.
So i wanted to try your HACS integration. Btw, I am running HA on a RPi4/ssd.
For the Requirements:
I did however found in Integrations your Continuously Cast Dashboards integration, but was not able to add it. I got the following message:
## This device cannot be added from the UI
You can add this device by adding it to your 'configuration.yaml'. See the documentation for more information.
So there is an entry in my (config)/includes/integrations.yaml file:
### Google Nest Hub v2 Casting Dashbard.
continuously_casting_dashboards:
logging_level: warning #Required: Set the logging level - debug/info/warning (default is 'warning' - try 'debug' for debugging)
cast_delay: 45 #Required: Time (in seconds) for casting checks between devices
start_time: "06:30" #Required: Start time of the casting window (format: "HH:MM")
end_time: "02:00" #Required: End time of the casting window (format: "HH:MM") and must be after "00:00"
devices:
"<Display_Name": "Woonkamer display" #Required: Display name of your device. Find this on the actual device's settings or inside the Google Home app.
dashboard_url: "https://192.168.178.221:8123/g-home/huis-bl-45" #Required: Dashboard URL to be casted
I don’t know it this is necessary, but i have these trusted_networks in my auth_providers in my (config)/includes/homeassistant.yaml file:
auth_providers:
- type: trusted_networks
trusted_networks:
- 192.168.178.227/32 # Google Nest Huv v2
- 192.168.178.228/32 # Google Home
- 192.168.178.226/32 # ChromeCast TV
- 192.168.178.251/32 # Yamaha receiver
trusted_users:
IP_ADDRESS_1: DASHBOARD_USER_ID
IP_ADDRESS_2: DASHBOARD_USER_ID
IP_ADDRESS_3: DASHBOARD_USER_ID
allow_bypass_login: true
# Note that bypass_login only works if one user is authorized
But I am not sure what to fill-in at the trusted-users: config… If this is not necessary, please let me know.
I might have made several mistakes here, but i hope you can help me to solve this.
Kind regards, Bert
Hi @deltabert , i’m sorry I have only just seen this! I only keep track of the raised issues in Github and not here.
As for your setup, you don’t need to add any resources for the integration to your dashboards. The only one you need there is the ha-catt-fix.
There is no UI for the integration, and all is controlled via the configuration.yaml file. I think you need to move your setup there (or maybe it can stay inside the integration.yaml file?)
Your setup for the device name is incorrect.
It should follow the format like this:
continuously_casting_dashboards:
logging_level: debug
cast_delay: 25
start_time: "06:00"
end_time: "02:00"
devices:
"Kitchen display":
dashboard_url: "http://192.168.12.104:8123/kitchen-dashboard/default_view?kiosk"
volume: 5
start_time: "06:00"
end_time: "03:00"
That should get things working for you. Also, there have been some updates since 12 days ago so make sure to update 