Daniel

It's bitten me numerous times since my post on July 17th! What do ya mean it didn't trigger? "Office" occupancy sensor triggered! Switch to YAML and it shows "Office" media...

> > This sure will cause issues for new people. > > Why only "new people"? It much more affected experienced people since they are using entity_ids. It's a severe...

> 1. Using selectors in UI for automations became rather pointless since it usually selects wrong entities. More reasons to use yaml-mode. > 2. Using a selector in "Dev tools...

I have not had any trouble since changing to... ``` service: notify.alexa_media data: target: "{{ states('sensor.last_alexa' }}" ``` The ` service: notify.alexa_media_last_called` seemed to be a problem for me...

> I'll try the above change to use the service.alexa_media Did that solve your issue? I *think* the integration is temporarily removing & re-adding its services when it periodically contacts...

Thank you, Alan, for confirming this. Do you see any possible solution, other than avoiding the cause?

I already tried that. And just now I launched Chrome which I have never used for Home Assistant and have the same error message.

I no longer have that issue and I did nothing to resolve it, other than staying up to date with all updates in HA. I don't know when the issue...

> change the `manifest.json` in the `custom_components/astroweather` I made the change, restarted HA, and the integration is now running. 

@Maddin1684 > very strange as mine does not after the change and restart of home assistant I don't know what to say...