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

Something went wrong discovering a harmony hub #10

Closed
UserRG opened this issue Mar 19, 2020 · 19 comments
Closed

Something went wrong discovering a harmony hub #10

UserRG opened this issue Mar 19, 2020 · 19 comments

Comments

@UserRG
Copy link

UserRG commented Mar 19, 2020

If I opend the Config-Node there is the Message "Something went wrong discovering a harmony hub".
Scanning for hubs ist not possible...
If i type in the IP-Address there is no function at the ObserveNode...
Screenshot1
I trigger an activity to switch on my Plug for TV. But there is no function.

@lopelex
Copy link
Owner

lopelex commented Mar 20, 2020

Need a little more information.

@lopelex
Copy link
Owner

lopelex commented Mar 20, 2020

Hardcore the ip address and enable debug.

@UserRG
Copy link
Author

UserRG commented Mar 21, 2020

I already did that:
HarmonyHubConfig

Whenn I save the Config-Node the function works. But a few hours later there is no function... I ve got another Poblem with Alexa node. The node crashed an Node Red restarts. I delete the Alexa Node, so I will test again with Harmony. But the warning "Something went wrong..." still appears.

@UserRG
Copy link
Author

UserRG commented Mar 22, 2020

At this evening the problem ist still there... The action doesn't arrive in node red. I restart the Hub and do the configuration on "myharmony" again. But the Message appears again... I debug the Nodes and it works again... I have a fix IP-Adress and I dont't know what I can do... With my Remote-Control the function works perfectly...

@lopelex
Copy link
Owner

lopelex commented Mar 23, 2020

What is output in the node-red console?

@UserRG
Copy link
Author

UserRG commented Mar 23, 2020 via email

@famthi
Copy link

famthi commented Apr 19, 2020

same error for me: the harmony hub can't be detected, hard coded IP address doesn't work either. When I activate the debug mode, node red crashes with this log:

`Welcome to Node-RED

19 Apr 14:23:33 - [info] Node-RED version: v0.16.1
19 Apr 14:23:33 - [info] Node.js version: v7.4.0
19 Apr 14:23:33 - [info] Linux 4.19.97-v7l+ arm LE
19 Apr 14:23:34 - [info] Loading palette nodes
19 Apr 14:23:38 - [info] Dashboard version 2.2.1 started at /ui
19 Apr 14:23:38 - [warn] ------------------------------------------------------
19 Apr 14:23:38 - [warn] [harmonyws-api] SyntaxError: Unexpected identifier
19 Apr 14:23:38 - [warn] ------------------------------------------------------
19 Apr 14:23:38 - [info] Settings file : /root/.node-red/settings.js
19 Apr 14:23:38 - [info] User directory : /root/.node-red
19 Apr 14:23:38 - [info] Flows file : /root/.node-red/flows_fc8dada4efbc.json
19 Apr 14:23:38 - [info] Server now running at http://127.0.0.1:1880/
19 Apr 14:23:38 - [info] Starting flows
19 Apr 14:23:38 - [info] [fritzbox-callmonitor:996b8a86.6e7e58] Connecting to fritzbox...
19 Apr 14:23:38 - [info] Started flows
19 Apr 14:23:38 - [info] [fritzbox-callmonitor:996b8a86.6e7e58] Connected to fritzbox
19 Apr 14:23:39 - [info] HarmonyWS open (192.168.1.25)
19 Apr 14:23:39 - [red] Uncaught Exception:
19 Apr 14:23:39 - TypeError: RED.util.encodeObject is not a function
at Node.sendDebug (/root/.node-red/node_modules/node-red-contrib-harmony-websocket/nodes/server.js:74:29)
at Node.info (/root/.node-red/node_modules/node-red-contrib-harmony-websocket/nodes/server.js:82:18)
at Hub.Node.openListener (/root/.node-red/node_modules/node-red-contrib-harmony-websocket/nodes/server.js:15:44)
at emitNone (events.js:91:20)
at Hub.emit (events.js:185:7)
at Harmony.harmony.on (/root/.node-red/node_modules/node-red-contrib-harmony-websocket/lib/hub.js:24:44)
at emitNone (events.js:86:13)
at Harmony.emit (events.js:185:7)
at _client.onOpen.addListener (/root/.node-red/node_modules/harmony-websocket/lib/harmony-websocket.js:115:18)
at Timeout._onTimeout (/root/.node-red/node_modules/chnl/dist/channel.cjs.js:2:3240)
at ontimeout (timers.js:365:14)
at tryOnTimeout (timers.js:237:5)
at Timer.listOnTimeout (timers.js:207:5)`

@lopelex
Copy link
Owner

lopelex commented May 21, 2020

Is the problem still in the new version?

@UserRG
Copy link
Author

UserRG commented May 21, 2020 via email

@DesignDawg
Copy link

I am having the exact same issue. I've had this set up and running for several months+, from back when the nodes were called "HWS Command," "HWS Activity," etc. I updated tonight to 2.2.1, and not only do my flows not recognize the nodes, but the nodes can no longer comment with my hubs or get any activities or commands.

I get the "Something went wrong discovering an Harmony Hub" error. I can't get it to discover, and I can't hard code the IPs and get anything to work.

I ended up NPM installing v. 1.3, and it works again

@lopelex
Copy link
Owner

lopelex commented May 24, 2020

Maybe it is due to nodejs and node-red outdated version. I can not reproduce the error.

@DesignDawg
Copy link

DesignDawg commented May 24, 2020 via email

@lopelex
Copy link
Owner

lopelex commented May 24, 2020

Try to export the flow as json and rename the nodes with text editor and then import it again.

@DesignDawg
Copy link

DesignDawg commented May 24, 2020 via email

@DesignDawg
Copy link

image
Alright. Can confirm. Updating to latest version of Node and node-RED did the trick! Funny, this was a fresh Docker install last night, and I assumed the source I installed from was the latest version, but somehow it was actually older than my previous one!

Thanks for continuing to develop and support. This project is a fantastic solution.

I will update my flows now, and (duh...why didn't I think of that?) just changing the text and reimporting makes total sense!

@JasonBSteele
Copy link

Just installed and tried to configure but got the error in the OP.

I updated to the latest Node Red as suggested above but that didn't work.

22 Jun 19:51:30 - [info] Node-RED version: v1.0.6
22 Jun 19:51:30 - [info] Node.js version: v12.18.0
22 Jun 19:51:30 - [info] Linux 4.19.75-v7+ arm LE

Manually setting the IP is working fine.

@CaptainSweatpants
Copy link

Updating Node-Red to 7.0 fixed this issue for me (mostly). I still get that “something went wrong...” error, but not nearly as much as before.

@kapet
Copy link

kapet commented Jan 12, 2021

Bug is here: https://github.com/lopelex/node-red-contrib-harmony/blob/master/nodes/server.html#L47

There's a '/' in front of the 'hws', this works if the admin UI as at / but breaks if I set httpAdminRoot. The 404 error is visible in the Chrome dev console when the "Something went wrong etc" message is shown.

@lopelex
Copy link
Owner

lopelex commented Jan 13, 2021

Cool, thx. Never used httpAdminRoot.

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

7 participants