-
Notifications
You must be signed in to change notification settings - Fork 5
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
Not discoverable #7
Comments
This is the output when I try to run this with NPM start: hoobs@hoobs:~/nodejs-poolController-next $ npm start
Init state for Pool Controller npm ERR! A complete log of this run can be found in: |
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 |
This error:
There was a change on the controller side, config should now be:
|
And this looks like a problem - Error: listen EADDRINUSE 0.0.0.0:4200 Something else is on port 4200 already on your Pi? |
If you wind up trying to do it manually, then yes the MAC address of the PI running nodejs-poolController |
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 GitHub<#7 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ALK72AYTNM7QUSIWUXFTJMDRTRLYFANCNFSM4NLI3EMQ>.
|
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? |
What's showing up in your ST logs? Trying going to Configuration for the main device, change the logging level to "Trace" |
When I try to edit the pool controller, I named it "Pentair" I get an error "Error fetching device. Please try again." |
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 |
I was looking for the ide logs from SmartThings. - From https://graph.api.smartthings.com/ide/logs |
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. |
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 |
Assuming this is resolved so closing. |
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.
The text was updated successfully, but these errors were encountered: