Jump to content

Ambient Weather installed but no creating nodes


Recommended Posts

Posted

 

I just installed Ambient Weather on my Pilosy from PG3 Node server store. I entered the API key on the configuration and saved it. I see the node server on the Pilosy but none of the nodes get created. 

 

image.thumb.png.eb3ff050fe8c93230adec9068215694f.png

 

Posted

If that's all your log shows, then it looks like PG3 is unable to start the node server.  You can check the PG3 log for errors trying to start the node server.

Posted

UD Support connected to my Polisy to get everything running again, I have attached the PG3 Log file. I uninstalled and reinstalled the Ambient Weather Node Server with same results it will not start. I also installed the NOAA Node Server and it too will not start. Looks like PG3 has some issues. PG2 Node Servers run with no problems.

 

 

EDIT: File removed

Posted

The log is showing authentication errors connecting to the ISY. Sounds like you don't have the right username or password entered for the ISY.

Posted

@bpwwer  Ok so now am back to the original error where the Nodes never get created on my ISY. Node server starts then shuts down after 3 seconds. Attached it the log. Thank you

 

EDIT: Removed file

 

Posted

Look like you got lucky.  You happened to install a node server(s) that didn't get the latest version of the interface module and that version that did get installed, requires the latest version of pyisy module which is currently broken. 

The next version of PG3 will try to work around this, but at this point, there's no easy way to fix this.  Because Python relies on so many third party modules, if one of those breaks, it causes trouble for everyone using that module and there's nothing configured on the Polisy to let your manually change these packages.

I updated the AmbientWeather and NOAA node servers to require the fixed version of the module so you can try refreshing the store and then restarting(starting) one of those node servers and see if that works.

Posted

@bpwwer Thank you for the update. At this point I have the node servers I need running on PG2 so I will wait for a fix. Would that be the same issue I see with Ambient Weather Node Server?

Thanks again for the response and assistance.

Posted

Yes, at this point, you'll see the same problem with almost all node servers because it isn't really a problem with the node servers, but a module that they all depend on.

Posted
21 hours ago, bpwwer said:

Look like you got lucky.  You happened to install a node server(s) that didn't get the latest version of the interface module and that version that did get installed, requires the latest version of pyisy module which is currently broken. 

The next version of PG3 will try to work around this, but at this point, there's no easy way to fix this.  Because Python relies on so many third party modules, if one of those breaks, it causes trouble for everyone using that module and there's nothing configured on the Polisy to let your manually change these packages.

I updated the AmbientWeather and NOAA node servers to require the fixed version of the module so you can try refreshing the store and then restarting(starting) one of those node servers and see if that works.

@bpwwer,

I will be traveling to my other location that hasn't had an upgrade for several versions (isy, node server's, pg3), since I wasn't there and didn't want to upgrade remotely. Given the issue with pyisy module not working, does this mean I shouldn't perform an upgrade?

While everything is not at the latest version on IoP, everything is currently working and since it is a remote site, I wouldn't want anything to break.

Thanks for your opinion.

dc

Guest
This topic is now closed to further replies.

×
×
  • Create New...