Force Cast does not seem to work

[Tokn59]

Hi, Really happy with this code. I tried to set up a solution with 2 different dashboards being cast to the same device depending on the state of an entity (input_boolean.nesthub_alarm). The idea is that when this entity's state becomes "on" a different dasboard is shown (cameras). However I can't seem to get this to work. The Nest hub keeps showing the first dashboard, not the secons when the state of input_boolean.nesthub_alarm changes. Any ideas ? Could you maybe publish a full example including the state trigger options ? From the examples it is unclear to me where devices: goes when adding the state_trigger optrions ... Thank you !!!!

[Tokn59]

Hello, sorry to repeat but is there any news on this please ? Thank You !

[joene-nl]

I am also not able to get state_triggers to work. Normal casting is working fine, but combining this with a state_trigger for when the doorbell rings is not responding at all.

[b0mbays]

@joene-nl I'll test out the cast triggers later today and get back to you 👍

[joene-nl]

@joene-nl I'll test out the cast triggers later today and get back to you 👍

You don't have to, my bad :) Made a mistake in the config, it does take something like 5-10s before the other dashboard is casted though.

[Tokn59]

Can you please share a working config example with the trigger ? Thank you !!!

Sent from my iPhone

On 8 Feb 2024, at 13:12, Joene-NL @.***> wrote:



@joene-nlhttps://github.com/joene-nl I'll test out the cast triggers later today and get back to you 👍

You don't have to, my bad :) Made a mistake in the config, it does take something like 5-10s before the other dashboard is casted though.

— Reply to this email directly, view it on GitHubhttps://github.com/b0mbays/continuously_casting_dashboards/issues/38#issuecomment-1933986148, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACGJZ76DXPYR5NZPZFX2YQ3YSS6JNAVCNFSM6AAAAAA6N2G7GCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZTHE4DMMJUHA. You are receiving this because you authored the thread.Message ID: @.***>

[joene-nl]

I think it was like this, as it took me too long to cast the new dashboard on trigger I removed it again:

logging_level: warning 
cast_delay: 45 
start_time: "07:00" 
end_time: "01:00" 
devices:
 "Displayname": 
  - dashboard_url: "http://ip:8123/lovelace-cast/default_view?kiosk" 
    volume: 0 
state_triggers:
 "Displayname":
  - entity_id: "sensor entitiy ID"
    to_state: "on"
    dashboard_url: "http://ip:8123/dashboard-carport/default_view?kiosk"
    time_out: 30 
    force_cast: true 

[b0mbays]

Closing this issue as it looks like you had the state_triggers nested within devices, but it needs to be it's own parent.

Let me know if didn't solve this, and i'll re-open 👍