-
Notifications
You must be signed in to change notification settings - Fork 18
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
Nodes quit working #8
Comments
Nevermind, a Node-RED restart seemed to have solved the issue |
I had a similar issue. Yes, restarting Node Red worked, but I believe this is still a bug. There is no indication that communication with the Harmony has stopped - it just silently fails. |
I just reopened this since it's not just me and mine did it again. Wonder if it's a Node-RED issue or the node.js that it wraps around. When I have time in the next week or so, I'm going to just try to go straight to the node.js and see if that stabalizes it. Thanks. |
Last time this problem happened, I sent a command to harmony using a command node, and I believe that was enough to reestablish the connection. My harmony observe node then worked again. Only light evidence at this point though - I haven't had the problem again to test. |
Same problem here. Restarting Node Red doesn't help. |
Should be fixed in latest version thanks to your contribution! |
In the last couple of days I've noticed that my harmony nodes no longer work. I verified that the harmony-server node reports back that it is connected to a valid server. But when I change an activity on the hub it's not producing any output from the H Observe node. Similarly, I verified that my h-activity node is pulling the id associated with an activity but sending a trigger message to the node is not turning on or off the activity. I'm not seeing any error messages generated in my log output.
The text was updated successfully, but these errors were encountered: