Jump to content

Trouble finding AIR after move from PG2 to PG3


tmorse305

Recommended Posts

 

Hi @bpwwer, Sorry if you have watched the edits on this message.  There were additional configuration instructions that came up on the NS after the station ID is entered which I didn't see initially.  There still seems to be a problem, it's not happy with the Station ID.  Do I have the configuration entered correctly?

Thank you.  

 

Errors:

2022-02-20 16:04:23,984 Thread-1   udi_interface      ERROR    weatherflow:query_station: Station Query failed for Station ID: [Errno Expecting value] <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><title>GlassFish Server Open Source Edition  4.1.2  - Error report</title><style type="text/css"><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 500 - Internal Server Error</h1><hr/><p><b>type</b> Exception report</p><p><b>message</b>Internal Server Error</p><p><b>description</b>The server encountered an internal error that prevented it from fulfilling this request.</p><p><b>exception</b> <pre>javax.servlet.ServletException: java.lang.NullPointerException</pre></p><p><b>root cause</b> <pre>java.lang.NullPointerException</pre></p><p><b>note</b> <u>The full stack traces of the exception and its root causes are available in the GlassFish Server Open Source Edition  4.1.2  logs.</u></p><hr/><h3>GlassFish Server Open Source Edition  4.1.2 </h3></body></html>

2022-02-20 16:04:24,226 Thread-1   udi_interface      ERROR    weatherflow:query_station: Station Query failed for key: [Errno Expecting value] <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><title>GlassFish Server Open Source Edition  4.1.2  - Error report</title><style type="text/css"><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 500 - Internal Server Error</h1><hr/><p><b>type</b> Exception report</p><p><b>message</b>Internal Server Error</p><p><b>description</b>The server encountered an internal error that prevented it from fulfilling this request.</p><p><b>exception</b> <pre>javax.servlet.ServletException: java.lang.NullPointerException</pre></p><p><b>root cause</b> <pre>java.lang.NullPointerException</pre></p><p><b>note</b> <u>The full stack traces of the exception and its root causes are available in the GlassFish Server Open Source Edition  4.1.2  logs.</u></p><hr/><h3>GlassFish Server Open Source Edition  4.1.2 </h3></body></html>

image.png

Link to comment

@JimboAutomates Hey Jim, Made the conversion tonight from PG2  to PG3. 

Got it running. Parameter instructions could be improved a bit, or examples given. Had to play a while to get it.But am not getting forecast info. Not sure what I should be putting for the station info for the forecast. I am using a Tempest on site for other data.  Any suggestions? Thanks. 1155679065_ScreenShot2022-02-20at8_52_23PM.thumb.jpg.379a5d7088c9d2072621df3e4b003309.jpg

Link to comment
16 minutes ago, dbwarner5 said:

.But am not getting forecast info. 

UPDATE: The forecast data has now populated. Just took a while. However Forecast conditions for Forecast 1 &2 are both "unknown" . Not sure if this is an error or just an update issue. 

Cheers and thanks again for all the hard work you are doing on this stuff!!

Screen Shot 2022-02-20 at 9.14.04 PM.jpg

Link to comment
10 hours ago, dbwarner5 said:

@bpwwer Thanks Bob!  Great NS.  One very minor and not important note: on the UD Mobile app, the “Conditions” are reporting as a number vs text. Not really important but just wanted you to know! 

All values for every node are currently numbers.  It's up to the UI to convert those to text based on the mapping provided by the node server.   It's possible that there's something in the mapping that is causing UD mobile to fail, but I believe the admin console isn't having problems with it.

If conditions are showing up as unknown, then WeatherFlow probably added some new ones that I don't know about.  If they add something new, the mapping has to be updated so that the node server knows what to do with it.

Yes, it takes a while for the forecasts to populate.  There's something wrong in the node server and it ends up waiting for one LongPoll interval before it makes the query to WeatherFlow for that info.

Link to comment

Something is wrong with the station ID.    When the node server contacts the WeatherFlow server to get the information about the station, the WeatherFlow server is responding with:

Quote

The server encountered an internal error that prevented it from fulfilling this request.

That is coming from WeatherFlow, not the node server. 

Link to comment

It works fine for me even with your station ID and the error is coming from WeatherFlow.  So it has to be your configuration. 

The only error in the node server is because it's not getting valid data from the WeatherFlow server.

Link to comment
22 hours ago, bpwwer said:

All values for every node are currently numbers.  It's up to the UI to convert those to text based on the mapping provided by the node server.   It's possible that there's something in the mapping that is causing UD mobile to fail, but I believe the admin console isn't having problems with it.

If conditions are showing up as unknown, then WeatherFlow probably added some new ones that I don't know about.  If they add something new, the mapping has to be updated so that the node server knows what to do with it.

It appears that value 14 for GV13 is creating the UNKNOWN conditions result. I have it in two forecasts.

20 hours ago, JimboAutomates said:

I think you have to restart ISY then resync UDMobile

Thanks Jim. worked. Rebooted ISY, resync UDMobile, now conditions show up as names not numbers. T

Link to comment
2 hours ago, bpwwer said:

It works fine for me even with your station ID and the error is coming from WeatherFlow

@bpwwer, thanks for your reply.  Its strange that it works for you (without the token?)  Here is my configuration, does it look correct?

I created a 2nd token, same result.

This is a long shot but maybe related?  The first time I set this up I incorrectly created a key "Station ID".  When I restarted the blue message about needing the Station ID was gone so I thought I was all set.  @jimboAutomates set me straight on that but could that be a left over somehow?  I have deleted and re-added the NS twice so I would think that would clear everything but just thought I would throw that out there.

 

Thanks again for your help.

image.png.6c83c58ab12702617081c7609ddc31ae.png

Link to comment

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...