"Unable to connect to Home Assistant" about scheduler-component

[nielsfaber]

Oh wow, that doesn't sound really bad.
I would like to find the root cause here, but it looks like that will not be easy.
I'm hoping you can help me finding this.
Have you been successful with reproducing it? The issue comes back as soon as you add the scheduler again?

It sounds like the issue is caused by the scheduler-card, not this component though.
Because the component has really nothing to do with browsers and cookies, it only does the timekeeping part on the background.
Simple way to proof this would be to keep the scheduler integration on (with some schedules running), and remove the card from your Lovelace config, see if the problem persists.

[pqpxo]

Hi there,

I've had another 2-3 people on Facebook confirm that they've had the same issue and managed to resolve it by removing this component. I'll try and spin up another instance of HA and reproduce the issue, I'm not willing to risk my 'production' HA instance again

[KTibow]

@pqpxo how'd it go?

[Kylespamaccoun7]

Hi, this just happened to me this morning. I installed scheduler card, restarted three times trying to get it to work before I remembered I had to install an actual integration.

Then I installed the integration via HACS and I had the error described above. Clearing cache did not work like frontend stuff normally does, but I was able to run on another browser and in incognito mode (chrome).

I had to actually clear cookies as described above. I didn't want to lose my sign-ins so I cleared the cookies individually. I cleared the database storage cookie and local storage cookies associated with the ip address and port HASS runs on. Wish I had tried them individually.

Sorry I don't have any logs available. I run hass version 0.108.8 on docker (virtual machine). I wonder if the other users who had issues were running older versions as well. Hope this helps.

[pqpxo]

Hi, this just happened to me this morning. I installed scheduler card, restarted three times trying to get it to work before I remembered I had to install an actual integration.

Then I installed the integration via HACS and I had the error described above. Clearing cache did not work like frontend stuff normally does, but I was able to run on another browser and in incognito mode (chrome).

I had to actually clear cookies as described above. I didn't want to lose my sign-ins so I cleared the cookies individually. I cleared the database storage cookie and local storage cookies associated with the ip address and port HASS runs on. Wish I had tried them individually.

Sorry I don't have any logs available. I run hass version 0.108.8 on docker (virtual machine). I wonder if the other users who had issues were running older versions as well. Hope this helps.

Hey there ... After many hours and trying to figure out the cause I actually downgraded to 0.114 and experienced the same issue. Initially I thought it was something new/introduced in 0.115 but it appears not

[pqpxo]

@pqpxo how'd it go?

Going to spin up another VM later this evening and give it a try. Is there anything I should be looking out for log wise or in the Network tab in Chrome Inspector? I spent ages trying to find an error or clue to what was causing the issue.

[nielsfaber]

This issue is also posted in the scheduler-card: nielsfaber/scheduler-card#59
I propose we continue the follow-up there. As it is likely caused by the card.

[KTibow]

Consider closing if just the scheduler-component doesn't cause any errors?

[nielsfaber]

So far i don't know for sure whether the scheduler-component can be excluded from the equation...

[nielsfaber]

I close this issue, assuming that this problem is fixed with new version of the card.
Please re-open if there are problems again.