b0mbays / continuously_casting_dashboards

HACS Integration for continuously casting a Home Assistant dashboard to your Google Chromecast Displays
MIT License
230 stars 11 forks source link

No Casting #15

Closed Fishairman90 closed 1 year ago

Fishairman90 commented 1 year ago

Good morning, I am coming from another continuous casting project that worked pretty well but wanted to try this out. So im 99% sure it's not any of the "typical" casting issues.

Followed the instructions for the install Added everything to my .config Rebooted Nothing happens. No attempts to cast. Cant find anything complaining in the logs.

Fishairman90 commented 1 year ago

2023-04-30 12:10:38.471 DEBUG (MainThread) [custom_components.continuously_casting_dashboards.dashboard_caster] state_triggers_map: {} 2023-04-30 12:10:38.472 DEBUG (MainThread) [custom_components.continuously_casting_dashboards.dashboard_caster] monitored_entities: set() 2023-04-30 12:10:38.508 INFO (MainThread) [custom_components.continuously_casting_dashboards.dashboard_caster] Current local time: 12:10:38.507964 2023-04-30 12:10:38.508 INFO (MainThread) [custom_components.continuously_casting_dashboards.dashboard_caster] Local time is inside the allowed casting time for <Master_Bedroom_Display. Start time: 01:00:00 - End time: 23:00:00

b0mbays commented 1 year ago

Hey, can you post your config? Are there no more logs after the above logs? It should start to cast after printing that it's within the allowed casting time

b0mbays commented 1 year ago

I can see the name of the device in the log is:

<Master_Bedroom_Display

Are you sure that is what your device is named inside the devices settings or within the Google home app?

Fishairman90 commented 1 year ago

IMG_3726

Fishairman90 commented 1 year ago

Ahh I see what your saying.. the "<"

Fishairman90 commented 1 year ago

Changing, let me see what happens

Fishairman90 commented 1 year ago

Here is my full CONFIG

continuously_casting_dashboards: logging_level: debug #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 each device. start_time: '01:00' #Optional: Global start time of the casting window (format: "HH:MM") - Default is set to "07.00" and can be individually overwritten per device below. end_time: '23:00' #Optional: Global end time of the casting window (format: "HH:MM") and must be after "00:00". Default is set to "01.00" and can be individually overwritten per device below. devices: "Master_Bedroom_Display": dashboard_url: "192.168.1.3:8123/lovelace/overview" volume: 5 start_time: '01:00' end_time: '23:00' "Kitchen_Display": dashboard_url: "192.168.1.3:8123/lovelace/overview" volume: 5 start_time: '01:00' end_time: '23:00'

b0mbays commented 1 year ago

You don't need the "_" for the spaces in your names of the devices. Remove those and it should start casting 😁

For example:

"Office display": dashboard_url: "http://192.168.12.104:8123/nest-dashboard/default_view?kiosk" volume: 7 start_time: "06.00" end_time: "18.00"

Fishairman90 commented 1 year ago

FYI I had to change all the "time values" from " to ' because it was throwing errors for all of them.

b0mbays commented 1 year ago

That's strange. Could you post the error log for the time value? Mine has " for the time values and no errors...

Did the above change fix things for you too?

Fishairman90 commented 1 year ago

Here is the LOG ValueError: time data '06.00' does not match format '%H:%M'

It's casting now, but coming to a login screen. "Baby steps" Guess this casting method uses a different method of casting? Because I have never had to login.

I added "this" to my .config but now HA is booting in Safe mode.

homeassistant: auth_providers:

Fishairman90 commented 1 year ago

Ignore most of the last ^^^

Fixed that issue. It is trying to cast now and login.... but just is a black screen and says "login" if you press login, nothing happens but a button pops up and says "start over"

b0mbays commented 1 year ago

Ahh there was a mistake in the readme! It looks like I was using a dot (.) Instead of (:) between the timings which was causing the error that you saw. I've updated the examples in the readme now. Thank you!

As for your "login" error, that's a case of the trusted networks not working for the devices IP address. The long number and characters you sent represents an ipv6 IP address (I think...). Is there a way you can force your router to use ipv4 for your devices? That might be the issue.

For example, my displays are in the format of "192.168.1.200" etc

Fishairman90 commented 1 year ago

oof welp, im locked out of my HA on all devices..

b0mbays commented 1 year ago

Ignore my last comment, I misread your config. It looks correct, other than which IP address are you using for the trusted users?

It should be the device IP (192.168.1.19/32) and then the user ID. So, you require two entries for both of your devices

Fishairman90 commented 1 year ago

Finally fixed 90% of my issues and have one auto logging in. But for whatever reason now it's only working on one of them.

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 each device. start_time: '01:00' #Optional: Global start time of the casting window (format: "HH:MM") - Default is set to "07.00" and can be individually overwritten per device below. end_time: '23:00' #Optional: Global end time of the casting window (format: "HH:MM") and must be after "00:00". Default is set to "01.00" and can be individually overwritten per device below. devices: "Master Bedroom Display": dashboard_url: "http://192.168.1.3:8123/lovelace/overview" volume: 5 start_time: '01:00' end_time: '23:00' "Kitchen Display": dashboard_url: "http://192.168.1.3:8123/lovelace/overview" volume: 6 start_time: '01:00' end_time: '23:00'

Fishairman90 commented 1 year ago

Update, they seem to be working now.. Rebooted both Google Homes.

b0mbays commented 1 year ago

That's great to hear! 😁

You could also check out kiosk mode for making the dashboards full screen if that's something you're after, theres a link in the requirements section👍