bsileo / hubitat_poolcontroller

Integration from a SmartThings or Hubitat hub to nodejs_poolcontroller
MIT License
8 stars 5 forks source link

Not discoverable #7

Closed therapcat closed 4 years ago

therapcat commented 4 years ago

hi Brad, sorry for opening a new issue. I installed the poolController next and also the pool controller web client. I can't confirm if either are running.

I've edited the config.json file in the poolController next to reflect my ST hub IP address. I'm not sure if that's the IP I should use or the IP of the Raspberry PI that is connected to my RS485 adapter.

I had this all working on the 5.3.3 version before.

I really just need this to show up in SmartThings. The app is there but the pool controller doesn't show up.

Please advise.

therapcat commented 4 years ago

This is the output when I try to run this with NPM start:

hoobs@hoobs:~/nodejs-poolController-next $ npm start

nodejs-poolController@6.0.0 start /home/hoobs/nodejs-poolController-next npm run build && node dist/app.js

nodejs-poolController@6.0.0 build /home/hoobs/nodejs-poolController-next tsc

Init state for Pool Controller info: Init http interface: SmartThings error: Error initializing interface bindings: Error: watch /home/hoobs/nodejs-poolController-next/web/bindings/smartThings.json ENOENT Error: listen EADDRINUSE 0.0.0.0:4200 at Object._errnoException (util.js:1022:11) at _exceptionWithHostPort (util.js:1044:20) at Server.setupListenHandle [as _listen2] (net.js:1351:14) at listenInCluster (net.js:1392:12) at doListen (net.js:1501:7) at _combinedTickCallback (internal/process/next_tick.js:141:11) at process._tickCallback (internal/process/next_tick.js:180:9) at Function.Module.runMain (module.js:686:11) at startup (bootstrap_node.js:187:16) at bootstrap_node.js:608:3 npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! nodejs-poolController@6.0.0 start: npm run build && node dist/app.js npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the nodejs-poolController@6.0.0 start script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in: npm ERR! /home/hoobs/.npm/_logs/2020-05-26T22_22_48_373Z-debug.log hoobs@hoobs:~/nodejs-poolController-next $ [1] 0:bash* "hoobs" 15:23 26-May-20

therapcat commented 4 years ago

rebooted the whole thing. Re-ran it. Still not showing up in ST. I'd add it manually but I don't know the MAC address for the Pool Controller? Is that just the MAC address for the Rasbperry PI?

Init state for Pool Controller info: Init http interface: SmartThings error: Error initializing interface bindings: Error: watch /home/hoobs/nodejs-poolController-next/web/bindings/smartThings.json ENOENT
info: Server is now listening on 0.0.0.0:4200 info: Serial port: FAKE_PORT opened info: Serial port: FAKE_PORT request to open succeeded without error

bsileo commented 4 years ago

This error:

error: Error initializing interface bindings: Error: watch /home/hoobs/nodejs-poolController-next/web/bindings/smartThings.json ENOENT

There was a change on the controller side, config should now be:

"fileName": "smartThings-Hubitat.json",
bsileo commented 4 years ago

And this looks like a problem -

Error: listen EADDRINUSE 0.0.0.0:4200

Something else is on port 4200 already on your Pi?

bsileo commented 4 years ago

If you wind up trying to do it manually, then yes the MAC address of the PI running nodejs-poolController

therapcat commented 4 years ago

I think this was from the previous instance not loading all the way. I’ll reboot and try it again. I didn’t get this error after rebooting.

I’ll change the config to show this smartThings-Hubitat.json and hopefully I’ll be good.

On May 26, 2020, at 5:17 PM, Brad Sileo notifications@github.com<mailto:notifications@github.com> wrote:

And this looks like a problem -

Error: listen EADDRINUSE 0.0.0.0:4200

Something else is on port 4200 already on your Pi?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/bsileo/hubitat_poolcontroller/issues/7#issuecomment-634347817, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALK72AYTNM7QUSIWUXFTJMDRTRLYFANCNFSM4NLI3EMQ.

therapcat commented 4 years ago

Ok. I added it manually and it verified it. It also added the controller but there were 0 devices listed. Do I have to add those manually?

bsileo commented 4 years ago

What's showing up in your ST logs? Trying going to Configuration for the main device, change the logging level to "Trace"

therapcat commented 4 years ago

When I try to edit the pool controller, I named it "Pentair" I get an error "Error fetching device. Please try again."

therapcat commented 4 years ago

should I delete those logs? Not sure if there's any sensitive info there. But if you search Pentair in them, you can see an error 500 for com.smartthings.stclient

bsileo commented 4 years ago

I was looking for the ide logs from SmartThings. - From https://graph.api.smartthings.com/ide/logs

therapcat commented 4 years ago

Screen Shot 2020-05-26 at 5 50 13 PM Screen Shot 2020-05-26 at 5 49 20 PM Screen Shot 2020-05-26 at 5 49 13 PM IMG_2218

therapcat commented 4 years ago

I re-added the controller, but it still gave 0 options for devices when adding. It didn't end up adding it because I already had the other one in there with the same name. But the issue is with pulling the configs from the pentair controller. It isn't reading any of the devices.

bsileo commented 4 years ago

Agreed- your nodejs-poolController instance is not working right. Thats a prerequisite so you need to sort that first then get the SmartThings side going. Best source of help on that is https://gitter.im/nodejs-poolController/Lobby

bsileo commented 4 years ago

Assuming this is resolved so closing.