Likewise. I bought a 3rd meross smart plug and now all 3 of them become unavailable multiple times a day
Agreed, I’m in the same boat and am very frustrated with the TP-Link integration. I have to reload it multiple times a day and of course, the devices I need are never available (via HA) when I need it. An automation to do this would be greatly appreciated.
Where is your issue on github? Things don’t get fixed by reloading integrations. They get fixed by posting proper bug reports.
Well, not sure if always. My example: I have an air conditioning devices integrated with HA via KNX. For longer periods of inactivity I switch power off completely from those AC units (by Shelly 1PM) so I don’t waste energy as they use ~20W while being idle. After a longer power off the KNX is not able to pick it up when turned on back again - is that a bug in KNX integration I should raise to be fixed or rather an expected behavior that a simple KNX integration reload fixes nicely?
That sounds like a bug.
Hi, Have a similar problem with a Samsung TV integration on a older Samsung TV. The manual reload works, however annoying.
I have made a automation activated when the entity goes unavailable. I use the “Home Assistant Core Integration: Reload config entry” service with the unresponsive entity.
alias: Samsung, Stue, reload TV
description: ''
trigger:
- platform: state
entity_id: media_player.samsung_65
to: unavailable
condition: []
action:
- service: homeassistant.reload_config_entry
target:
entity_id: media_player.samsung_65
mode: single
I’ve tried doing this with a Rest command and a curl script and cannot get it to reload an integration. I’ve does the whole Long lived access token and everything. But it still takes me to manually click reload in the UI before it reloads properly. In my case it’s Eufy Security. If anyone has any ideas, I’m all ears!
Thank you for this. I will try the same with my entities that become unavailable.
While this does not fix the bug with the integration, at least it makes it easier than manually reloading it.
I will also create a bug for the integration, if there is none.
I found this thread when looking for a fix for my Meross dimmer as well. Have you narrowed down what’s causing the integration to stop working? I haven’t had a chance to test my theory yet, but I’m wondering if it’s related to my internet access going down briefly (which happens at my house fairly regularly for anywhere from 5 seconds, to a few minutes at a time, unfortunately due to the type of internet service I have in my area).
I planned on setting up an automation that triggers an integration reload any time my internet access goes down (which I already monitor with ping sensors).
I use OctoPrint and, as I turn off the 3D printer when it is not in use, a lot of entities get stuck “unavailable”.
I found this topic when I was searching to write an automation to reload the integration.
While I did not find one to reload the integration, the solution to OctoPrint for me was using service HOMEASSISTANT.RELOAD_CONFIG_ENTRY, Home Assistant Core Integration - Home Assistant (home-assistant.io)
One entity of Octoprint responds even with power cycling the printer, the status of the printer, so I used that as a trigger and reloaded the entire entity using the homeassistant.reload_config_entry option.
It works for a per device and reloads all entities of that device.
I certainly would not want to muck around doing this for ZigBee though given I have over 40 ZigBee devices.
A reload Integration service would definitely be helpful.
Thanks for this.
I noticed that it helped to reload the Unifi integration after any update to Unifi Network.
Now I don’t have to remember as it will trigger an automation when my routers device track makes itself unavailable.
I haven’t had the issue with Unifi yet, but will keep an eye on it. I may do the same thing as a precaution
Following the Early Access channel means frequent updates. Digging my own grave ?
Never use Early Access in a prod environment, or an environment where a partner may be involved.
Anyway, that is a bit off topic and I don’t want to hijack another thread lol
Great tip.
I also turn off my printer when it is not in use ( Ender 3 ) and everytime I launch HA and my printer is OFFLINE I get error that HA could not make connection with Octoprint!
I`m using MQTT plugin within Octoprint so I think I do not need the Octoprint integration. Just deleted it.
I`m haging issues with ESPHOME and ZIGBEE they turn unavailable multiple times per day and I wonder if it is not due to the Octoprint integration. Will see, just deleted the bloody Octoprint integration.
Always worth a try. You can always add the integration back if you need to
Same Problem with Meross Mss310 (Energy Monitoring). I think it’s because of calling too much for information. I experienced same thing when I wanted to make a script flash the lights (switch), it just made the Plugin stop working, probably because of overload.
Don’t know how to fix the request problem right now (limitation of request probably) so I thought of the easy way… Reload the Plugin
I will play with the rate and burst limits a bit and see if that helps.
I will report, maybe that helps others too.
I ended up switching to Meross LAN, which entierly solved it.
Some of my integrations also need reloading from time to time (Wiser, IKEA) and I’m really interested in a solution to this. Am thinking a button to reload a specific integration and an automation to “press” that button.
+1 for integration reload