Automate-Pulse-v2
Automate-Pulse-v2 copied to clipboard
sillyfrog
Hub dropping out randomly
I have two hubs and both of them have been dropping out randomly over the last month or so, but only in HA and not in the app.
Each hub has two blinds on it. The app is still able to control the blinds but Home Assistant shows them as unavailable. I have not been able to find anything in the logs of HA that show anything apart from the entities becoming unavailable. Power cycling the hub fixes the problem, one hub is connected via ethernet and the other via wifi, but has good signal.
Has anyone else been seeing this?
I've been having problems this week. I reload the integration in Home assistant and it starts working again.
I will try that next time and see how I go. Interesting that it is not just me it is happening to.
Jumping on the bandwagon. Since updating HA to 2023.5.2, the pulse hub integration requires manual reloading after each system reboot. I automatically restart HA every night so it's quite frustrating to have all my blinds offline in the morning!
I'm hosting it on a RPi 3 which is not super stable at the best of times and tends to hang every 2-3 days if I don't, often when I'm away from home. Just makes it a bit more stable generally. Although with the new db optimisations maybe it's worth trying it without for a while :)
Same issue. I now have hourly job to refresh/reload. Haven't noticed anything obvious in logs.
HA 2023.5.2 Integration 0.9.9
I have not changed anything and the hub seems to be stable again.
I am yet to upgrade to 2023.5 and want to but hesitant if something breaks, is everyone else still having issues?
For those having issues, how far away is your hub from your blinds? When I first set mine up it would drop out every so often, and I moved the hub closer (like about 2m away now). Easy for me I know as I only have one set of blinds to control.
The range on the hub is terrible, however when the hub drops out in HA I can still use the app to control them so it’s not a signal issue. A simple reload of the integration fixes it.
I have two hubs and only one seems to drop out. Now on 2023.5 and the problem persists.
For those having issues, how far away is your hub from your blinds? When I first set mine up it would drop out every so often, and I moved the hub closer (like about 2m away now). Easy for me I know as I only have one set of blinds to control.
Exact same here. After disabling auto restarts of HA it's been more stable, but still not perfect. Dropped out again last night, requiring a reload of the integration.
Same issue. I now have hourly job to refresh/reload. Haven't noticed anything obvious in logs.
This is a good idea. Will try to set up a similar automation until this gets resolved.
Same issue. I now have hourly job to refresh/reload. Haven't noticed anything obvious in logs.
Hope this is not off topic, but how do you schedule a reload of the integration?
Hope this is not off topic, but how do you schedule a reload of the integration?
First, get the entry_id from your automate (blind hub) entry in config/.storage/core.config_entries. I used the Terminal & SSH add-on to find it, since you can't see the hidden .storage folder through file editor. It's a long string of random numbers/letters. Then simply create an automation, triggered however you like, to call the homeassistant.reload_config_entry and put your entry_id in.
service: homeassistant.reload_config_entry
data:
entry_id: yourentryidhere
Same issue for me, hubs keep going unavailable in HA. Reloading integration brings them back online.
Mine seems to only be occurring on HA restart. Is it possible to delay the initial loading of integrations within HA?
It happens randomly where the devices go 'unavailable' with a reload of the integration brining the devices back up. I've not been able to figure a common denominator for why it happens. As it can sometimes be up for a number of days, and other times go down a couple of times a day - and sometimes it doesn't work when HomeAssistant restarts.
Enabled debug logging, but haven't been able to find anything yet.
I just ended up creating an automation below that checks every couple of minute, and if a shade is unavailable, it reloads the integration
alias: General - Reload Acmeda Pulse
description: ""
trigger:
- platform: time_pattern
minutes: /2
condition:
- condition: state
entity_id: cover.sunshade
state: unavailable
action:
- service: homeassistant.reload_config_entry
data:
entry_id: daee7e7023a3d1ba7d22ad60287583da
mode: single
Thank you @dgaust and @lukefo for the tips in setting up the reload automation, have setup an automation now to reload if any of the shades report as unavailable.
@dgaust are you finding the reload when unavailable is working? Reason I ask, is because I had an automation to send a message when the shades were "unavailable", but it didn't seem to trigger. Got home this arvo and they were offline, but no notification was sent.
It's been a while since I've upgraded HA, so never noticed this, I have updated over the weekend, and things are going OK for me (v2023.9.3), is this still an issue for you with the latest HA?
@dgaust are you finding the reload when unavailable is working? Reason I ask, is because I had an automation to send a message when the shades were "unavailable", but it didn't seem to trigger. Got home this arvo and they were offline, but no notification was sent.
Sorry, didn't see this one. I checked the history, and it only happens rarely, the last time it triggered ran to completion was two days ago. Since I setup the automation I've not run into an issue with the blind becoming unavailable.
I’m on 2023.10.1 and both of my hubs were unavailable after rebooting HA. I did go through a period of time where it seemed to be better but I have no data to back that up with.
Also anyone else’s hubs being recalled due to the firmware unable to be updated OTA?
Not sure if people are still having this issue, but I've been having this problem too, and I just realised it seems to be happening exclusively when the blinds are controlled through an automation.
I have just posted about it on Reddit, but here is a copy of what I wrote there for the sake of this discussion...:
Riddle me this: In Home Assistant, I have an automation to close my blinds at sunset. This is done with the Automate Pulse v2 integration installed via HACS.
The blinds work fine when they are controlled manually through HA (e.g. a button to close the blinds on the dashboard). When in an automation, though, the blinds become unresponsive and don't move at all, and I have to power-cycle the blinds controller (Pulse Hub v2) as the connection from blinds controller to HA drops out (the controls for all blinds stop working and turn grey in HA, even when the automation is only for one blind).
The blinds controller itself is working fine as I can still go into its iPhone app and close the blinds in there, while the controls are greyed out and unresponsive in HA. It's just the connection between the blinds controller and HA that goes offline, and only when I attempt to control the blinds in an automation.
Interestingly, a simple automation such as:
at 8:15pm
Close one specific blind
...in the trace timeline, actually shows:
Triggered at 8:15pm
Blind is closing
Blind is opening
Blind is unavailable.
Any ideas on why this might be happening, please?
If someone can get some debugging logging when it happens, I maybe able to take a look.
Given mention of devices needing to be replaced, I'm wondering if there's a correlation (just a guess). I've been running over a week now and still no issues (I adjust the blinds every 10 minutes during daylight hours to follow the sun, so the integration is used a lot).
I have one hub on v1.9.0 that's not been replaced (nor have I had issues), and it has 9 shades attached. I'm running HASS 2023.9.3 (via docker).
I really don't want to send my hub in for the recall... such an inconvenience.
I have an automation to reload the integration after every HA reboot... otherwise the integration just doesn't work.
I've also edited my integration so that it ignores roller.online otherwise shades would regularly become unavailable, and the Pulse hub would need a reboot every time.
If someone can get some debugging logging when it happens, I maybe able to take a look.
Sorry for the noob question, but as I mentioned in #24, I enabled the debug logging mode on the integration, but can't seem to see anything relevant in HA Settings > System > Logs. Is that where I would find the logs? If so, the issue doesn't generate anything in the logs at all when it occurs...
Lucky you. I can’t even connect to mine. It’s as good as bricked.On 14 Oct 2023, at 1:29 pm, Simon @.***> wrote: I really don't want to send my hub in for the recall, such an inconvenience. I have an automation to reload the integration after every HA reboot... other the integration just doesn't work. I've also edited my integration so that it ignores roller.online otherwise the Pulse hub needed rebooting all the time...
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>
I have the same/similar issue with the official integration (pulse 1 hub) - I have 2 hubs. It stops working daily. I can still control via the app. Unfortunately I need to restart HA to get it to work again...attempting to reload the integration fails as it's "unavailable" as it requires a restart of HA to reload :( (when the integration is working I can reload it without the need to restart HA)
