I’m getting: ValueError: day is out of range for month 
Same thing is happening to me
2020-02-28 19:13:36.175503 WARNING AppDaemon: ------------------------------------------------------------
2020-02-28 19:13:36.175988 WARNING AppDaemon: Unexpected error in scheduler loop
2020-02-28 19:13:36.176598 WARNING AppDaemon: ------------------------------------------------------------
2020-02-28 19:13:36.177424 WARNING AppDaemon: Traceback (most recent call last):
File "/usr/lib/python3.8/site-packages/appdaemon/scheduler.py", line 421, in loop
next_entries = self.get_next_entries()
File "/usr/lib/python3.8/site-packages/appdaemon/scheduler.py", line 335, in get_next_entries
next_exec = datetime.datetime.now(pytz.utc).replace(year=3000)
ValueError: day is out of range for month
Same, I think this is the issue?
Sorry about this - I just released version 4.0.2 with a fix.
3 Likes
These things happen.
Is there a add-on version on its way?
That I do not know - I don;t look after the addon. I believe it should update automatically and build a new version of the addon that can then be used to re0install but I am not 100% sure about that, hopefully @frenck can answer when he gets online. PyPi and docker should now be updated with the fix.
There is no (working) docker build yet is there?
when I run “latest” I run into the astral bug:
AttributeError: module ‘astral’ has no attribute ‘Location’
I really feel a little cluster-effed :-/
You’re not alone.
same here, 4.0.1 with working astral can’t start due to leap year and 4.0.2 won’t start due to the astral issue oh noooo
edit: I’ve installed the dev image … that works fine for today
So why is my appdaemon still working? I use @frenck addon… I only have the configcheck app and it is also working. I have not restarted the addon though…
The appdaemon log is filled with the error…
Maybe youre not using anything that needs timing.
My auto lights turn on, but not off
This is problematic. A whole day without a working home automation and it dosn’t seem to get fixed until midnight
If I go here: https://github.com/hassio-addons/addon-appdaemon
It looks like the appdaemon addon has been upgraded to v0.2.2
BUT my instance of Hass running on my Raspberry Pi is still only showing v0.2.1.
Is there something I have to do to get it to detect the availability of the upgrade?
It isn’t. You can always go back to a prior version. 
So not working isn’t an argument, particularly not with an open-source project. If you want faster response times, go take the package and be the maintainer. 
Sorry, a little rant seemed to be necessary, as you don’t use smilies either…
And in general, it is your responsibility, as admin of a home automation system, to take resonable measures to avoid such things => make yourself an update strategy. Not every new version does fit your environment or is without errors.
In my case I always wait one or two days, before I deploy my test system to production. But that may be, because I’m software developer myself.
@paddy0174 thanks for your rant, It wasn’t an upgrade that caused this but a date related bug, so no, going back to a previous version wouldn’t fix this, nor would any of your other suggestions.
@stowers If you go into the add-on store and click the refresh button top right it should now show as available for you to upgrade
Don’t really get the point of your post. Not sure if any amount of emoticons, changes anything But I am very glad for you that you don’t have any problems because you are a software developer…
You did however forget that the whole issue had nothing to do with upgrading anything, but was due to a leap-year bug. What makes it worse is that upgrading to the fix does not work, because the upgrade contains an other bug
The refresh worked! Thanks very much.
There should very shortly be a new docker version that fixes the second bug, the fix is already on PiPy.
Version 4.0.3 has the fix.