This is probably caused by an entity in your HA config that the card is unable to process.
I changed some things in the v2.0.1 release, that will make the card robust for such entities.
Please update to this version.
With the new version, you can check the browser log for information about which entity gives the problem.
I’ve updated also to 2.0.1, everything is working perfectly now.
Thanks for all the hard work! And maybe I repeat others, but this integration makes Hass usefull (using it since the beginning in august 2020!
Thanks for all your great work.
I have a feature request and am off traveling for holiday so no easy github access so sorry I am posting it here using my phone.
A vacation mode schedule that randomly turn things on and off. I currently use an appdeamon app called occupsim. I tell it the number of times I want the light turned on and it creates a random schedule for that many on/offs. Is this something the Scheduler could do?
Thanks
appdaemon…
For a long time it scared me a little. Then I used for ControlerX… And yesterday I spent hours on Schedy which is really a very well done scheduller ! Alas he doesn’t have a GUI!
I am a happy user of this integration, but all of a sudden those two unknown programs that make my card ugly have appeared and I can’t find a way to eliminate them. Can you help me? thanks.
Clear your whole storage by opening .storage and deleting the scheduler.storage file. If you’re using Samba, then check “Show hidden files and folders” under View on Windows Explorer to show the .storage folder. If you’re using Configurator, then remove .storage from hidden files/folders in the addon’s config.
The error indicates that a schedule is defective, in other words: for some reason the timer is not running.
Such schedule can still be modified by clicking on it.
Deleting your schedules storage file is not a good idea.
I would like to know when such problem occurs (I’ve never seen it), so I can solve this issue.
Please report it on Github if you experience this, and try to share as many details as possible.
Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/connection.py:84
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 2:54:16 AM (3 occurrences)
Last logged: 2:56:17 AM
[139842568859504] Received invalid command: scheduler