Integration is not currently compatible with HA 2023.5.0

[Wheemer]

Getting this error:

Setup failed for custom integration ha-continuous-casting-dashboard: Requirements for ha-continuous-casting-dashboard not found: ['catt==0.12.10'].

What are the prerequisites? It was working but suddenly is not, I don't think I changed anything.

[b0mbays]

Hey @Wheemer , that looks like the old name of the integration on an older version. Can you update or remove + reinstall the integration?

It should be called "continuously_casting_dashboards" in the logs and inside your configuration.yaml.

[Wheemer]

Setup failed for custom integration continuously_casting_dashboards: Requirements for continuously_casting_dashboards not found: ['catt==0.12.10'].

[b0mbays]

That's odd. And you say this was working previously and then stopped working? Could you post your config for the integration?

Also, what version of HA are you running?

[Wheemer]

Yes it was working, however it always stopped, never was continuous for long. However it's been getting this error for a few days now.

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: "Family Room display": #Required: Display name of your device. Find this under device settings -> Information -> Device Name dashboard_url: "http://192.168.0.108:8123/lovelace/default_view?wp_enabled=true" #Required: Dashboard URL to be casted

[b0mbays]

That's frustrating! The integration was never really stable until it moved to the new name of 'cotinuously_casting_dashboards' so that's why it would have never been continuous for long. (hopefully!)

What device are you casting to? Can you change the logging_level to 'debug' and see if you get any more logs? Or does the integration just fail to start?

Could you also try uninstalling the integration, temporarily removing the config for the integration, re-installing and then adding the config back?

[Wheemer]

No it doesn't start at all. I forgot to mention I am on the latest beta version of HA.

I did completely remove the integration and settings and reinstalled when you mentioned I had an old version.

Do I need dashcast installed?

[b0mbays]

The beta shouldn't make a difference... Could you try installing dashcast? If that's the issue then that's my bad entirely!

The error above suggests 'catt' is not compatible with whichever version you are running... which doesn't make sense. Try installing dashcast first 😄

[Wheemer]

I just uninstalled dashcast, as it was previously installed. I thought it might be conflicting. Still won't run.

I see this in the logs:

Unable to install package catt==0.12.10: ERROR: Cannot install catt because these package versions have conflicting dependencies. ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts [notice] A new release of pip is available: 23.1 -> 23.1.2 [notice] To update, run: pip install --upgrade pip

[Wheemer]

Same errors after reinstalling dashcast again.

[b0mbays]

There must be something new in the HA Beta that is causing this dependancy error.

Do you have access to a terminal that is logged into HA? If so, could you try the following command:

pip install catt

or

pip3 install catt

And post the output?

Thank you!

I'll also try and upgrade to the Beta.

[Wheemer]

What must I have installed for pip or pip3 to be installed? I do not even have those when checking from the core-ssh prompt.

[Wheemer]

I have uninstall pyscript from HACS and AppDaemon addon to see if they were interfering. Are those requirements?

Same error.

[b0mbays]

Okay I have updated to the Beta and I see the same error. We'll have to wait for the developer of 'catt' to update their packages when a newer stable release of HA is released.

If you want to use the integration i'd suggest to downgrade to a 'stable' release of HA. You can either restore from a backup (if you have one) that is using the current stable HA version.

Or you can manually downgrade your HA version easily from within the HA terminal with the following command:

ha core update --version 2023.4.6

Here is what mine looking like when I upgraded, but you can do the same to go to a lower version:

[Wheemer]

Thank you, it is working now. I will refrain from updating this instance.

And I believe it would be helpful to add dashcast to the requirements.

Also I tried to setup an input boolean to turn the casting on and off, however that doesn't seem to work. It casts all the time regardless of the state of the boolean.

Here's my setting again:

`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: "Family Room display": #Required: Display name of your device. Find this under device settings -> Information -> Device Name dashboard_url: "http://192.168.0.108:8123/lovelace/default_view?wp_enabled=true" #Required: Dashboard URL to be casted state_triggers: "Family Room display":

• entity_id: "input_boolean.cast_to_hub" to_state: "on" dashboard_url: "http://192.168.0.108:8123/lovelace/default_view?wp_enabled=true"`

[b0mbays]

Great news!

Dashcast is not a requirement so you can safely uninstall that integration if you wanted 👍 (I just tested this by uninstalling the integration)

As for your state entity not working, that is strange. Just tested mine and it's working fine...

This is where I am triggering the "dummy" entity inside developer tools -> services:

And this is my setup:

When I turn it to 'on' a new dashboard casts to my "Office display" 🤔

Could you post a screenshot of your setup? There is no formatting in the code you posted so I can't figure out if there's anything wrong with the indentation etc 😄

[b0mbays]

Btw, the state trigger feature won't be able to 'turn off' the dashboard. It's only used for casting to a display when an entity changes. If you want to turn off the display with an entity, you could set up an Automation through HA to turn off the Google Cast device itself (which will return it to the clock).

However, if you have this integration running and it's within the time range, then it will try to cast to the display again 😄

[Wheemer]

OK I have given up on the boolean.

The code gets messed up even while using the code quotes, so this editor has issues.

It's all good now, I'm just keeping an eye on it to see if it stops casting now.

Thanks for you help and contribution to the community.

[Fishairman90]

Can confirm.. just installed HA 2023.5 and immediately started having issues with this. :-/

[b0mbays]

Ahhh no! Okay i'm working on a fix now for the new version.

Just pushed a new update for an unrelated unhandled exception that was causing some problems, but i'll get a compatible version out soon!

[b0mbays]

Well... I've tried a few things (such as forking the catt package) but alas it's not working. I'm reverting back to 2023.4.6 and will wait for a new release of catt.

I've raised an issue here and will get an update out as soon as it's working 👍

[klasenby]

Thanks for the heads up on this, I'll wait to upgrade as well

[Thorvarium]

Same here, I reverted to 2023.4.6 for now. Thanks!

[se-bastiaan]

For a temporary fix:

CATT needs to have PEP 517 build-system settings to make sure pip can install it from git https://github.com/se-bastiaan/catt/commit/e3ef4ee25da5f04dd43c79040864efcced44059d And the version here can just be a tag https://github.com/se-bastiaan/continuously_casting_dashboards/commit/1a9a2611efd497f182ba5bb6375ce6e49e06bc6f

[b0mbays]

Ahh thanks for the info! I'll try that out later on if there isn't a new pip version by then. It looks like they're pushing one now 👍

I'll do some testing with the new version and get an update out asap!

[b0mbays]

New update is out with added support for 2023.5.x, thanks everyone for their help!

[Thorvarium]

hey @b0mbays, I am having this now after updating HA and CCD:

[b0mbays]

Ah, you'll need to do a full system reboot for HA. After it has rebooted, it should use the new version

[Thorvarium]

It do not let me reboot without fixing this issue lol

On Wed, May 10, 2023, 10:51 AM b0mbays @.***> wrote:

Ah, you'll need to do a full system reboot for HA. After it has rebooted, it should use the new version

— Reply to this email directly, view it on GitHub https://github.com/b0mbays/continuously_casting_dashboards/issues/17#issuecomment-1542344833, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABSANPJF2C5EIZB42RPGQYLXFOTOBANCNFSM6AAAAAAXTOPLJE . You are receiving this because you commented.Message ID: @.***>

[b0mbays]

You can, there's a 'restart' and 'reboot' inside settings. The reboot doesn't do any checks.

If you can't find it Google is your friend 😁

[Thorvarium]

Oh, I didn't realize that reboot and restart were different options. Working great now thanks

[b0mbays]

That's great to hear! I'll make a note that some users may need to reboot 👍