I ran the script manually (seconds later) - and it is working fine.
I am running HA container (Docker) 2022.10.4 on a Rpi 4 (2Gb) and it is showing no high loads etc. Z2M shows no errors.
My mqtt.publish scripts have run many times since that update (before the repair showed itself and once since - all working as expected with no more errors.
Any ideas?
…sorry, but not sure which category this goes in…
i restart and nothing new, just “save” the repair like if i have really repaired but i do nothing and the error goes and doesnt come back…
Perhaps not related but the 2 sensors used are from Arduino MQTT and perhaps no more up to date with the last MQTT broker version…i will investigate if the error goes back
My devices are mainly Hue/Aqara but I am not sure it’s related (as you suggested) as the issue appears to be around the availability of the service call: mqtt.publish.
Does this happen when HA is starting up? It could be the MQTT config entry is not ready yet and an automation could fail if mqtt.publish is called, because it is not registered yet.
That’s an excellent question.
I haven’t had the error in a while (plenty of restarts since the last one for upgrades etc) but I will keep a lookout - thank you for the suggestion.
Can you check you have if this file is still present in your install? homeassistant/components/mqtt/device_tracker/schema_yaml.py.
B.T.W. This file should have been removed with the upgrade to HA Core 2022.12, you can safely remove it.
What method do you use to upgrade Home Assistant core?
I’m not sure how to look inside the container itself. I only look at the directory that I have linked to /config via the docker-compose volumes: command: