Polyglot weather station node servers

[bpwwer]

1 hour ago, glarsen said:

I'm having a problem re-installing the WeatherPoly nodeserver after moving Polyglot from vm on an esxi server to a RPI.  I deleted the nodeserver from the old Polyglot and ISY prior to starting up the new machine and re-installing WeatherPoly.  The node majors all appear in the Node Servers WeatherPoly dropdown, but they do not appear in the nodes list in the ISY.  The WeatherPoly Polyglot console also shows 0 nodes. 

I've tried restarting the AC, Polyglot and ISY, in different orders, together and separately,uninstalling and reinstalling WeatherPoly and nothing makes any difference.  The other 3 Polyglot nodeservers on my system (MyQ, AVRemote, Sonos) all work fine.

I've attached a collection of screen grabs and logs.  Any idea what I'm missing here?

I don't see anything in the logs that indicate an issue so my only guess at this point is that the Polyglot database is corrupt for that node server slot.  I've seen this type of behavior before where the database entries don't get cleared out properly and Polyglot thinks the nodes are installed on the ISY so it never tries to add them.  Even after deleting and re-installing the node server. I think this may be related to a bug in Polyglot and unfortunately the only way to really fix it is to uninstall the node server, manually clear out the database and re-install.  

The command to clear out the slot in the database is: 

mongo polyglot --eval "db.nodes.remove({'profileNum':'6'})"

Where the profile number (6 above) is the slot where the node server was installed.

[glarsen]

1 minute ago, bpwwer said:

I don't see anything in the logs that indicate an issue so my only guess at this point is that the Polyglot database is corrupt for that node server slot.  I've seen this type of behavior before where the database entries don't get cleared out properly and Polyglot thinks the nodes are installed on the ISY so it never tries to add them.  Even after deleting and re-installing the node server. I think this may be related to a bug in Polyglot and unfortunately the only way to really fix it is to uninstall the node server, manually clear out the database and re-install.  

The command to clear out the slot in the database is: 

mongo polyglot --eval "db.nodes.remove({'profileNum':'6'})"

Where the profile number (6 above) is the slot where the node server was installed.

Ok, thanks, I'll give that a try.

Also, I noticed in the log when restarting the nodeserver after manually installing the profile I get this:

1/9/2019, 11:06:34 AM - debug: NS: Failed to upload nodedef/nodedefs.xml to ISY. Re-Trying.
1/9/2019, 11:06:34 AM - debug: NS: Failed to upload nodedef/nodedefs.xml to ISY. Re-Trying.
1/9/2019, 11:06:34 AM - error: unhandledRejection REPORT THIS!: TypeError: Cannot read property 'message' of undefined
    at Object.installprofile (/snapshot/udi-polyglotv2/lib/modules/nodeserver.js:626:51)
    at process._tickCallback (internal/process/next_tick.js:68:7)

 

[glarsen]

Uninstalled WeatherPoly.

Clearing the database gave me this: 

 

~$ mongo polyglot --eval "db.nodes.remove({'profileNum':'6'})"
MongoDB shell version: 3.2.11
connecting to: polyglot
WriteResult({ "nRemoved" : 0 })

Re-added and now see this in the log:

2019-01-09 11:31:14,373 [MainThread] [INFO ] Received Config from STDIN.
2019-01-09 11:31:14,373 [MainThread] [INFO ] UDI Polyglot v2 Interface 2.0.29 Starting...
2019-01-09 11:31:14,397 [Interface ] [INFO ] Connecting to MQTT... localhost:1883
2019-01-09 11:31:14,397 [MainThread] [INFO ] Calling Controller to create controller node
2019-01-09 11:31:14,406 [Interface ] [INFO ] MQTT Connected with result code 0 (Success)
2019-01-09 11:31:14,407 [Interface ] [INFO ] MQTT Subscribing to topic: udi/polyglot/ns/6 -  MID: 1 Result: 0
2019-01-09 11:31:14,408 [Interface ] [INFO ] MQTT Subscribing to topic: udi/polyglot/connections/polyglot -  MID: 2 Result: 0
2019-01-09 11:31:14,408 [Interface ] [INFO ] Sent Connected message to Polyglot
2019-01-09 11:31:14,454 [Interface ] [INFO ] Adding node WeatherPoly(weather)
2019-01-09 11:31:14,455 [Interface ] [INFO ] Waiting on Controller node to be added.......
2019-01-09 11:31:14,460 [NodeServer] [INFO ] Starting WeatherPoly Node Server
2019-01-09 11:31:14,469 [NodeServer] [INFO ] Check for existing configuration value
2019-01-09 11:31:14,469 [NodeServer] [INFO ] Adding configuation
2019-01-09 11:31:14,469 [NodeServer] [INFO ] Sending customParams to Polyglot.
2019-01-09 11:31:14,469 [NodeServer] [INFO ] Trying to create a mapping
2019-01-09 11:31:14,469 [NodeServer] [INFO ] MAPPING inhum to humidity-inside
2019-01-09 11:31:14,469 [NodeServer] [INFO ] Try to create node definition profile based on config.
2019-01-09 11:31:14,469 [NodeServer] [INFO ] write_profile: Writing profile/nodedef/nodedefs.xml
2019-01-09 11:31:14,470 [NodeServer] [INFO ] write_profile_zip: profile/version.txt as version.txt
2019-01-09 11:31:14,470 [NodeServer] [INFO ] write_profile_zip: profile/nls/en_us.txt as nls/en_us.txt
2019-01-09 11:31:14,470 [NodeServer] [INFO ] write_profile_zip: profile/editor/editors.xml as editor/editors.xml
2019-01-09 11:31:14,470 [NodeServer] [INFO ] write_profile_zip: profile/nodedef/nodedefs.xml as nodedef/nodedefs.xml
2019-01-09 11:31:14,471 [NodeServer] [INFO ] write_profile: done.
2019-01-09 11:31:14,471 [NodeServer] [INFO ] Sending Install Profile command to Polyglot.
2019-01-09 11:31:14,471 [NodeServer] [INFO ] remove all notices
2019-01-09 11:31:14,471 [NodeServer] [INFO ] Sending removenotice to Polyglot for index {'key': '0'}
2019-01-09 11:31:14,472 [NodeServer] [INFO ] Calling discover
2019-01-09 11:31:14,472 [NodeServer] [INFO ] Creating nodes.
2019-01-09 11:31:14,473 [NodeServer] [INFO ] Deleting orphaned temperature node
2019-01-09 11:31:14,473 [NodeServer] [INFO ] Removing node temperature
2019-01-09 11:31:14,473 [NodeServer] [INFO ] Creating Humidity node
2019-01-09 11:31:14,473 [NodeServer] [INFO ] Adding node Humidity(humidity)
2019-01-09 11:31:14,473 [NodeServer] [INFO ] Deleting orphaned pressure node
2019-01-09 11:31:14,473 [NodeServer] [INFO ] Removing node pressure
2019-01-09 11:31:14,474 [NodeServer] [INFO ] Deleting orphaned wind node
2019-01-09 11:31:14,474 [NodeServer] [INFO ] Removing node wind
2019-01-09 11:31:14,474 [NodeServer] [INFO ] Deleting orphaned rain node
2019-01-09 11:31:14,474 [NodeServer] [INFO ] Removing node rain
2019-01-09 11:31:14,474 [NodeServer] [INFO ] Deleting orphaned light node
2019-01-09 11:31:14,474 [NodeServer] [INFO ] Removing node light
2019-01-09 11:31:14,474 [NodeServer] [INFO ] Deleting orphaned lightning node
2019-01-09 11:31:14,474 [NodeServer] [INFO ] Removing node lightning
2019-01-09 11:31:14,475 [NodeServer] [INFO ] starting web server thread
2019-01-09 11:31:14,480 [NodeServer] [INFO ] WeatherPoly Node Server Started.
2019-01-09 11:31:14,481 [Thread-1  ] [INFO ] Started web server on port 8100
2019-01-09 11:31:14,491 [Interface ] [INFO ] Adding node WeatherPoly(weather)
2019-01-09 11:31:14,492 [Interface ] [INFO ] Waiting on Controller node to be added.......
2019-01-09 11:31:14,589 [Interface ] [INFO ] Adding node WeatherPoly(weather)
2019-01-09 11:31:14,590 [Interface ] [INFO ] Waiting on Controller node to be added.......
2019-01-09 11:31:14,591 [Interface ] [INFO ] Adding node WeatherPoly(weather)
2019-01-09 11:31:14,592 [Interface ] [INFO ] Waiting on Controller node to be added.......
2019-01-09 11:31:14,594 [Interface ] [INFO ] Adding node WeatherPoly(weather)
2019-01-09 11:31:14,594 [Interface ] [INFO ] Waiting on Controller node to be added.......

Still, the nodes show in the nodeserver list on the iSY, but the nodes aren't added to the Main list.

[glarsen]

Well, I was able finally to add all of the nodes to the ISY manually, and the data is updating.  None of the nodes appear on the WeatherPoly entry in the Polyglot dashboard, but I guess that's minor.  Thanks for looking into this.

[bpwwer]

1 hour ago, glarsen said:

Uninstalled WeatherPoly.

Re-added and now see this in the log:

Still, the nodes show in the nodeserver list on the iSY, but the nodes aren't added to the Main list.

The log indicates that the node server is trying to add the nodes to the ISY, but it's not happening.  The node server sends the request to Polyglot and Polyglot is supposed to send the command to the ISY to add the node.  If Polyglot thinks the node already exists on the ISY, it won't try to add it again so that's the only thing I can think of that would cause this.  Manually clearing the Polyglot database should have solved it.  Possibly it is sending the command and the ISY is rejecting it for some reason, but that should show up in the Polyglot log.

The fact that the nodes aren't showing up in Polyglot dashboard also points to Polyglot thinking they've already been added.  

My next suggestion was going to be to try and install it in a different slot. But now that you have things mostly working, it's probably not worth it to keep experimenting.

I'm sorry it's been so much trouble. Most of the time it just works, except when it doesn't.

[Adolfo]

Only have 3 nodes: "Controller" "Humidity" and  "Ilumination"   all without information on ISY.

Log:

2019-02-28 09:32:00,156 [Interface ] [DEBUG] Received stop from Polyglot... Shutting Down.
2019-02-28 09:32:00,159 [Interface ] [INFO ] Disconnecting from MQTT... localhost:1883
2019-02-28 09:32:00,161 [Interface ] [DEBUG] Stopping WeatherFlow node server.
2019-02-28 09:32:00,162 [Interface ] [INFO ] WeatherFlow node server UDP thread finished.
2019-02-28 09:32:00,163 [Interface ] [INFO ] MQTT Graceful disconnection.
2019-02-28 09:32:03,885 [MainThread] [INFO ] Received Config from STDIN.
2019-02-28 09:32:03,885 [MainThread] [INFO ] UDI Polyglot v2 Interface 2.0.29 Starting...
2019-02-28 09:32:04,017 [Interface ] [INFO ] Connecting to MQTT... localhost:1883
2019-02-28 09:32:04,066 [Interface ] [INFO ] MQTT Connected with result code 0 (Success)
2019-02-28 09:32:04,084 [Interface ] [INFO ] MQTT Subscribing to topic: udi/polyglot/ns/2 -  MID: 1 Result: 0
2019-02-28 09:32:04,084 [Interface ] [INFO ] MQTT Subscribing to topic: udi/polyglot/connections/polyglot -  MID: 2 Result: 0
2019-02-28 09:32:04,085 [Interface ] [INFO ] Sent Connected message to Polyglot
2019-02-28 09:32:04,138 [NodeServer] [INFO ] Starting WeatherFlow Node Server
2019-02-28 09:32:04,139 [NodeServer] [INFO ] Sending customParams to Polyglot.
2019-02-28 09:32:04,366 [NodeServer] [INFO ] WF says units are US
2019-02-28 09:32:04,366 [NodeServer] [INFO ] daily rainfall = 0.040000
2019-02-28 09:32:04,367 [NodeServer] [INFO ] yesterday rainfall = 7.986000
2019-02-28 09:32:04,368 [NodeServer] [ERROR] Failed to create Temperature Node
2019-02-28 09:32:04,368 [NodeServer] [INFO ] Adding node Humidity(humidity)
2019-02-28 09:32:04,370 [NodeServer] [ERROR] Failed to create Pressure Node
2019-02-28 09:32:04,371 [NodeServer] [ERROR] Failed to create Wind Node
2019-02-28 09:32:04,372 [NodeServer] [ERROR] Failed to create Precipitation Node
2019-02-28 09:32:04,373 [NodeServer] [INFO ] Adding node Illumination(light)
2019-02-28 09:32:04,375 [NodeServer] [ERROR] Failed to create Lightning Node
2019-02-28 09:32:04,376 [NodeServer] [INFO ] Finished adding all nodes
2019-02-28 09:32:04,376 [NodeServer] [INFO ] Initialzie rain data
2019-02-28 09:32:04,381 [NodeServer] [ERROR] Exception in thread NodeServer:
Traceback (most recent call last):
  File "/usr/lib/python3.5/threading.py", line 914, in _bootstrap_inner
    self.run()
  File "/usr/lib/python3.5/threading.py", line 862, in run
    self._target(*self._args, **self._kwargs)
  File "./weatherflow.py", line 141, in start
    self.discover()
  File "./weatherflow.py", line 254, in discover
    self.nodes['rain'].InitializeRain(self.rain_data)
KeyError: 'rain'
2019-02-28 09:33:04,109 [Controller] [INFO ] Query WeatherFlow server for observation data
2019-02-28 09:33:04,110 [Controller] [INFO ]  -  /swd/rest/observations/station/2587?api_key=6c8c96f9-e561-43dd-b173-5198d8797e0a
2019-02-28 09:33:04,273 [Controller] [ERROR] Exception in thread Controller:
Traceback (most recent call last):
  File "/usr/lib/python3.5/threading.py", line 914, in _bootstrap_inner
    self.run()
  File "/usr/lib/python3.5/threading.py", line 862, in run
    self._target(*self._args, **self._kwargs)
  File "/home/pi/.local/lib/python3.5/site-packages/polyinterface/polyinterface.py", line 771, in _parseInput
    self.longPoll()
  File "./weatherflow.py", line 152, in longPoll
    self.query_data()
  File "./weatherflow.py", line 350, in query_data
    self.nodes['temperature'].setDriver('ST', data['obs'][0]['air_temperature'])
KeyError: 'temperature'
 

Ideas?

Thanks 

[bpwwer]

1 hour ago, Adolfo said:

Only have 3 nodes: "Controller" "Humidity" and  "Ilumination"   all without information on ISY.

Log:

2019-02-28 09:32:00,156 [Interface ] [DEBUG] Received stop from Polyglot... Shutting Down.
2019-02-28 09:32:00,159 [Interface ] [INFO ] Disconnecting from MQTT... localhost:1883
2019-02-28 09:32:00,161 [Interface ] [DEBUG] Stopping WeatherFlow node server.
2019-02-28 09:32:00,162 [Interface ] [INFO ] WeatherFlow node server UDP thread finished.
2019-02-28 09:32:00,163 [Interface ] [INFO ] MQTT Graceful disconnection.
2019-02-28 09:32:03,885 [MainThread] [INFO ] Received Config from STDIN.
2019-02-28 09:32:03,885 [MainThread] [INFO ] UDI Polyglot v2 Interface 2.0.29 Starting...
2019-02-28 09:32:04,017 [Interface ] [INFO ] Connecting to MQTT... localhost:1883
2019-02-28 09:32:04,066 [Interface ] [INFO ] MQTT Connected with result code 0 (Success)
2019-02-28 09:32:04,084 [Interface ] [INFO ] MQTT Subscribing to topic: udi/polyglot/ns/2 -  MID: 1 Result: 0
2019-02-28 09:32:04,084 [Interface ] [INFO ] MQTT Subscribing to topic: udi/polyglot/connections/polyglot -  MID: 2 Result: 0
2019-02-28 09:32:04,085 [Interface ] [INFO ] Sent Connected message to Polyglot
2019-02-28 09:32:04,138 [NodeServer] [INFO ] Starting WeatherFlow Node Server
2019-02-28 09:32:04,139 [NodeServer] [INFO ] Sending customParams to Polyglot.
2019-02-28 09:32:04,366 [NodeServer] [INFO ] WF says units are US
2019-02-28 09:32:04,366 [NodeServer] [INFO ] daily rainfall = 0.040000
2019-02-28 09:32:04,367 [NodeServer] [INFO ] yesterday rainfall = 7.986000
2019-02-28 09:32:04,368 [NodeServer] [ERROR] Failed to create Temperature Node
2019-02-28 09:32:04,368 [NodeServer] [INFO ] Adding node Humidity(humidity)
2019-02-28 09:32:04,370 [NodeServer] [ERROR] Failed to create Pressure Node
2019-02-28 09:32:04,371 [NodeServer] [ERROR] Failed to create Wind Node
2019-02-28 09:32:04,372 [NodeServer] [ERROR] Failed to create Precipitation Node
2019-02-28 09:32:04,373 [NodeServer] [INFO ] Adding node Illumination(light)
2019-02-28 09:32:04,375 [NodeServer] [ERROR] Failed to create Lightning Node
2019-02-28 09:32:04,376 [NodeServer] [INFO ] Finished adding all nodes
2019-02-28 09:32:04,376 [NodeServer] [INFO ] Initialzie rain data
2019-02-28 09:32:04,381 [NodeServer] [ERROR] Exception in thread NodeServer:
Traceback (most recent call last):
  File "/usr/lib/python3.5/threading.py", line 914, in _bootstrap_inner
    self.run()
  File "/usr/lib/python3.5/threading.py", line 862, in run
    self._target(*self._args, **self._kwargs)
  File "./weatherflow.py", line 141, in start
    self.discover()
  File "./weatherflow.py", line 254, in discover
    self.nodes['rain'].InitializeRain(self.rain_data)
KeyError: 'rain'
2019-02-28 09:33:04,109 [Controller] [INFO ] Query WeatherFlow server for observation data
2019-02-28 09:33:04,110 [Controller] [INFO ]  -  /swd/rest/observations/station/2587?api_key=6c8c96f9-e561-43dd-b173-5198d8797e0a
2019-02-28 09:33:04,273 [Controller] [ERROR] Exception in thread Controller:
Traceback (most recent call last):
  File "/usr/lib/python3.5/threading.py", line 914, in _bootstrap_inner
    self.run()
  File "/usr/lib/python3.5/threading.py", line 862, in run
    self._target(*self._args, **self._kwargs)
  File "/home/pi/.local/lib/python3.5/site-packages/polyinterface/polyinterface.py", line 771, in _parseInput
    self.longPoll()
  File "./weatherflow.py", line 152, in longPoll
    self.query_data()
  File "./weatherflow.py", line 350, in query_data
    self.nodes['temperature'].setDriver('ST', data['obs'][0]['air_temperature'])
KeyError: 'temperature'
 

Ideas?

Thanks 

I'm assuming you're trying to use the cloud based WeatherFlow node server. I've been trying to debug this for weeks and can't figure out why the cloud based polyglot fails to create some of the nodes.  Right now I'm stuck and can't even start the debug environment for the cloud polyglot so no progress is being made. 

If you're not running this on the cloud based polyglot let me know. When I last tested, it did work with a local polyglot, but my debugging efforts for the cloud may have caused some issues.

[Adolfo]

33 minutes ago, bpwwer said:

I'm assuming you're trying to use the cloud based WeatherFlow node server. I've been trying to debug this for weeks and can't figure out why the cloud based polyglot fails to create some of the nodes.  Right now I'm stuck and can't even start the debug environment for the cloud polyglot so no progress is being made. 

If you're not running this on the cloud based polyglot let me know. When I last tested, it did work with a local polyglot, but my debugging efforts for the cloud may have caused some issues.

Nop, I'm running this in a local polyglot-raspi in my network.

Also, the nodes that I see are empty of information.

[bpwwer]

2 hours ago, Adolfo said:

Nop, I'm running this in a local polyglot-raspi in my network.

Also, the nodes that I see are empty of information.

Ah, OK,, thanks.

Working on the local install is a lot easier to debug. I rolled back all the changes I made trying to get it working on the cloud and then added my latest attempt. It seems to be working locally again, but I'm not sure about cloud.  It does take some time for the store to notice the latest update. It should move to version 0.0.2 when it does.  You'll probably have to delete your existing copy and re-install from the store once it's there.

This is still pretty experimental, but should work.

[DaveStLou]

On 11/12/2018 at 3:59 PM, bpwwer said:

I suspect that the query causes a bit of network congestion, just enough that the server connection times out and fails.   Or it could be something blocking in the node server to polyglot interface long enough to cause the timeout and failure.

When ever I run a full query on the system (like the default program), WeatherPoly goes offline. Is there anything I can do to allow me to run query. Change polling? Or is there someway to restart WeatherPoly on my Raspberry Pi?

Edited March 18, 2019 by DaveStLou

[bpwwer]

1 hour ago, DaveStLou said:

When ever I run a full query on the system (like the default program), WeatherPoly goes offline. Is there anything I can do to allow me to run query. Change polling? Or is there someway to restart WeatherPoly on my Raspberry Pi?

The problem is that we still don't know why it's going off line.  The query seems to be what triggers it, but without actually knowing what is failing it can't really be fixed.

Polyglot makes it easy to create a node server, but it also hides a lot of the communication from the node server developer. The WeatherPoly code isn't doing anything at all when the ISY does a query. The query is handled entirely between node server interface code and Polyglot.

Can you provide anymore information about what happens when it does "offline"?  The WeatherPoly node server has a separate process that listens for the incoming weather data and publishes it to Polyglot (and then to the ISY). Offline could mean that thread has crashed while the main WeatherPoly code continues to run, or it could mean that the whole WeatherPoly node server was killed.  Next time it goes offline, can you run 'ps auxww | grep weatherstation' on the RPi and see if the node server is still running or not? And in either case, there should be some indication of what happened to cause it to go offline.  My RPi is currently offline so I can't run any experiments myself.

As far as I know, Polyglot doesn't have any way to automate node server start/restarts. Might be a good feature request for it though.

[DaveStLou]

13 minutes ago, bpwwer said:

The problem is that we still don't know why it's going off line.  The query seems to be what triggers it, but without actually knowing what is failing it can't really be fixed.

Polyglot makes it easy to create a node server, but it also hides a lot of the communication from the node server developer. The WeatherPoly code isn't doing anything at all when the ISY does a query. The query is handled entirely between node server interface code and Polyglot.

Can you provide anymore information about what happens when it does "offline"?  The WeatherPoly node server has a separate process that listens for the incoming weather data and publishes it to Polyglot (and then to the ISY). Offline could mean that thread has crashed while the main WeatherPoly code continues to run, or it could mean that the whole WeatherPoly node server was killed.  Next time it goes offline, can you run 'ps auxww | grep weatherstation' on the RPi and see if the node server is still running or not? And in either case, there should be some indication of what happened to cause it to go offline.  My RPi is currently offline so I can't run any experiments myself.

As far as I know, Polyglot doesn't have any way to automate node server start/restarts. Might be a good feature request for it though.

Since I can reproduce the error on demand by running the query all, here's the results of the command on pi:

pi       28526  0.2  1.6  56472 15528 ?        Sl   16:02   0:19 python3 ./weatherstation.py
pi       31301  0.0  0.0   4372   564 pts/0    S+   17:50   0:00 grep --color=auto weatherstation

In the Polyglot dashboard everything looks normal and there's nothing unusual in the WeatherPoly log.

The only thing I see in the Polyglot log is this:

2019-3-18 17:49:44 - error: ISY: connection failed. Retrying... Error: socket hang up

No other polyglot servers are showing offline when this happens. All I have to do is manually restart WeatherPoly and everything is fine again.

 

[bpwwer]

Thanks, it looks like it's the thread that's failing.  When I get my RPi back up, I'll see if I can reproduce it.

[bpwwer]

@DaveStLou if I'm correctly reproducing the issue, then I think I have if resolved.

When I query the node server, it switches the online status to false, but the WeatherPoly node server is not stopping, it continues to receive data and update the data nodes properly. It is only the online status value that is wrong.  If that's the same behavior you are seeing, then what I just pushed (version 0.1.6) should resolve it.

It looks like a bug somewhere in the node server interface.  The node server starts with the status initialized to false,  when it starts communicating with Polyglot, it gets switched to true. However when queried, the query seems to return the initial value, not the current value and thus, it's switched back to false.  

My change is to simply set the initial value to true.  

[TJF1960]

Hi Bob, 

I have been seeing False on the Meteobridge nodeserver as well. Will the new version you pushed here also include Meteobridge? How long does it usually take for it to show up in the store?

 

Thank you,

Tim 

[bpwwer]

27 minutes ago, TJF1960 said:

Hi Bob, 

I have been seeing False on the Meteobridge nodeserver as well. Will the new version you pushed here also include Meteobridge? How long does it usually take for it to show up in the store?

Thank you,

Tim 

I did push up new versions of the other weather station node servers as well.  I think the process that checks for new versions on the node server store runs once a day so give it 24 hrs.

[mbking]

Hello Bob,

I'm trying to uninstall the AmbientPoly from my local Polyglot instance on a RPi and the Uninstall is not uninstalling the node server.  I click the Uninstall button, get the banner message that the node server is being uninstalled, but the node server is still there.  I'm assuming I uninstall the node server first in Polyglot, then delete from the Admin Console from the ISY.  Do I have the process correct and do you have any ideas on how to get the Uninstall to work?

[bpwwer]

13 hours ago, mbking said:

Hello Bob,

I'm trying to uninstall the AmbientPoly from my local Polyglot instance on a RPi and the Uninstall is not uninstalling the node server.  I click the Uninstall button, get the banner message that the node server is being uninstalled, but the node server is still there.  I'm assuming I uninstall the node server first in Polyglot, then delete from the Admin Console from the ISY.  Do I have the process correct and do you have any ideas on how to get the Uninstall to work?

I had problems too getting node servers to uninstall.  I believe the proper sequence should be:

1) Stop the node server, make sure it is not connected and running.

2) Delete the node server using the dashboard entry "delete" button.  This should remove the node server from the ISY and from the dashboard

3) Uninstall from the store.  All this should do at this point is remove the node server files from the system.

If step 3 fails, you can remove the files from the terminal. The files are located in ~/.polyglot/nodeservers/AmbientPoly.  Removing that directory removes everything which is what the uninstall button is supposed to do.  I think you have to restart Polyglot after a manual remove before you can re-install.

[mbking]

3 hours ago, bpwwer said:

I had problems too getting node servers to uninstall.  I believe the proper sequence should be:

1) Stop the node server, make sure it is not connected and running.

2) Delete the node server using the dashboard entry "delete" button.  This should remove the node server from the ISY and from the dashboard

3) Uninstall from the store.  All this should do at this point is remove the node server files from the system.

If step 3 fails, you can remove the files from the terminal. The files are located in ~/.polyglot/nodeservers/AmbientPoly.  Removing that directory removes everything which is what the uninstall button is supposed to do.  I think you have to restart Polyglot after a manual remove before you can re-install.

Bob,

Thanks for the help.  This did the trick.  Once the node server was deleted, uninstalling from the store worked fine.  I'll keep this information for future reference.  Thanks again.

[DaveStLou]

On 3/20/2019 at 5:36 PM, bpwwer said:

I did push up new versions of the other weather station node servers as well.  I think the process that checks for new versions on the node server store runs once a day so give it 24 hrs.

I haven't seen the new versions yet in the store. 

[bpwwer]

18 hours ago, DaveStLou said:

I haven't seen the new versions yet in the store. 

Looks like it's there now.

[DaveStLou]

3 hours ago, bpwwer said:

Looks like it's there now.

I've updated and it seems to have fixed the query problem. Thanks!

[TJF1960]

I noticed this morning that for Meteobridge precipitation page the first value does not have a proper name. Please see screenshot. Also, we haven't had rain for two days. Is that value supposed to be daily rain fall or monthly?

Thanks,

Tim

 

[bpwwer]

On 3/30/2019 at 10:31 AM, TJF1960 said:

I noticed this morning that for Meteobridge precipitation page the first value does not have a proper name. Please see screenshot. Also, we haven't had rain for two days. Is that value supposed to be daily rain fall or monthly?

Thanks,

Tim

I believe that's what Meteobrige reports as "Total Rainfall".  I've added the name and pushed a new version with that change.  Thanks for reporting it.

[bpwwer]

Formal announcement of the availability of the udi-darksky-poly node server.   This node server will pull data from the DarkSky (www.darksky.net) weather service.  You must register with them to use the service.

The DarkSky node server pulls the current condition data along with the 7 day forecast.  To configure set the following custom parameters:

- APIkey   : Your API ID, needed to authorize connection to the DarkSky API.

- Location : latitude and longitude of the location to query the data for. ex: 42.3601,-71.0589

- Units    : 'si' or 'us' request data in this units format.

The node server will work on either a local Polyglot installation or the Polyglot Cloud.