Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

H Observes stops sending data until flow redeployed #29

Open
perjury opened this issue Nov 30, 2019 · 5 comments
Open

H Observes stops sending data until flow redeployed #29

perjury opened this issue Nov 30, 2019 · 5 comments

Comments

@perjury
Copy link

perjury commented Nov 30, 2019

From time to time, H Observe stops sending data. This can be fixed by redeploying the flow. I'm currently having to redeploy flow every 2/3 days

@Jacopos94
Copy link

i have the same issue

@hoeni
Copy link

hoeni commented Oct 2, 2020

Same here with H command. After some days the harmony does not send the commands anymore. After a deployment it works again.

@Mikypan81
Copy link

Same issue with activities. Anyone have managed to solve this???

@zygi79
Copy link

zygi79 commented Mar 31, 2022

I have now tested this as the node-red-contrib-harmony-websocket always crashes my Node Red when not being able to connect to the hub. But unfortunately it seems that I am facing the same issue which is not solved. Anybody meanwhile found a workaround?

@Jacopos94
Copy link

I stopped using nodered when I bought a homey device, but my workaround for nearly a year was creating a flow that at a set time of day would force a redeploy and that worked most of the time and when it did not work I would force a redeploy via a simulated hue from alexa.in the end I stopped using harmony remotes and activities in favour of an rm4pro since I could not get the harmony hub to reliably stay online

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants