Appdaemon not receivng events after HA restart

Third party integrations AppDaemon
21

hmmm this seems to be an extra issue:
I’ve written a wait function


and call it in each module e.g.
with wait.wait_available(self,“sensor.dev16_em_tot”,False)

it works fine when the module is reloaded … it also works fine when i restart the appdaemon container.
but leaving the appdaemon container running and restart home assistant fails again

16.06.2020 14:54:20 INFO energy: dev sensor.dev16_em_tot not ready
16.06.2020 14:54:21 INFO energy: dev sensor.dev16_em_tot not ready
16.06.2020 14:54:22 INFO energy: dev sensor.dev16_em_tot not ready
16.06.2020 14:54:23 INFO energy: dev sensor.dev16_em_tot not ready
16.06.2020 14:54:24 INFO energy: dev sensor.dev16_em_tot not ready
16.06.2020 14:54:25 INFO energy: dev sensor.dev16_em_tot not ready
16.06.2020 14:54:26 INFO energy: dev sensor.dev16_em_tot not ready
16.06.2020 14:54:27 INFO energy: dev sensor.dev16_em_tot not ready
16.06.2020 14:54:28 INFO energy: dev sensor.dev16_em_tot not ready
16.06.2020 14:54:29 INFO energy: dev sensor.dev16_em_tot not ready
16.06.2020 14:54:30 INFO energy: dev sensor.dev16_em_tot not ready
16.06.2020 14:54:31 INFO energy: dev sensor.dev16_em_tot not ready
16.06.2020 14:54:32 INFO energy: dev sensor.dev16_em_tot not ready
16.06.2020 14:54:33 INFO energy: dev sensor.dev16_em_tot not ready
16.06.2020 14:54:34 INFO energy: dev sensor.dev16_em_tot not ready

it almost seems like the connection isn’t ready … any idea?
I guess there is nothing like self.wait_for_hass_load_ready() right?
JKW

22

https://appdaemon.readthedocs.io/en/latest/CONFIGURE.html#hass-plugin-startup-conditions

1 Like
23

AD 4.0.4 was just released which should handle HASS restarts better - it will wait until HASS is ready before starting up again.

24

Hey Andrew, thank you for all the amazing work on AppDaemon.

I’ve been having issues surrounding HA restarts still. I’m running the docker image with the ‘latest’ tag. It seems that as of February 2, 2021, the latest tag is still 4.0.3. Is this intentional?

I see that both 4.0.4 and 4.0.5 have since been released. Not sure if they are still considered pre-release / not stable? I can manually pull those tags, but I’d prefer to just run ‘latest’

This is my current docker compose yaml:

  appdaemon:
    container_name: appdaemon
    image: acockburn/appdaemon:latest
    restart: unless-stopped
    ports:
      - 5050:5050
    volumes:
      - /opt/appdata/appdaemon:/conf
      - /etc/localtime:/etc/localtime:ro
    environment:
      - TOKEN=mytoken
      - HA_URL=myurl
25

its a mistake that 4.0.3 is still latest.

latest should be 4.0.5

that will be corrected with next release.

1 Like