Jump to content

Ambient Weather plugin linked to my RainwiseNet weather station

SHM

By SHM
in AmbientWeather

Go to solution Solved by bpwwer,

Recommended Posts

SHM Advanced

SHM

Posted
Posted

I have Ambient Weather plugin linked to my RainwiseNet weather station via AWN api.  I have entered just the api in the plugin configuration and it then gives me all of the weather station data (attached).  However, on the AC, the plugin only shows 2 nodes, each with the same weather station data (Barometric pressure, atmospheric pressure, temperature).  Have tried "adding all nodes" in the plugin menu with no luck.  Any ideas on how to get the other data to the AC to use for programming?

AC.png

ambient weather plugin.pdf install.log debug.log

bpwwer Advanced

bpwwer

Posted
Posted

Everything in the logs looks correct. The plug-in appears to be working fine based on what's in the log file.

Did you restart the AC after the plug-in was fully running?  The plug-in builds the nodes dynamically based on the data it sees from AWN.  The AC must be restarted after the nodes have been defined since it only reads the node definitions when it starts.

SHM Advanced

SHM

Posted
  • Author
Posted

My plugin shows 3 nodes and node 2 has 11 "drivers" which match the available weather data from my station.  These drivers do not show up on the AC.  Am I missing something?

bpwwer Advanced

bpwwer

Posted
Posted

Please answer my question above.

If you have restarted the AC, try restarting both the plug-in and then a minute or so later the AC.

As I said, based on the logs and the fact that the nodes are showing up in PG3 means the plug-in is working properly.  

bpwwer Advanced

bpwwer

Posted
Posted

It's PG3x that sends the commands to the IoX to create the nodes.  And the AC reads the info from the IoX.  So if there's a problem when PG3x sends the commands to create the nodes, the error should show up in the PG3x log.

You can try deleting and reinstalling (or even re-install the plug-in), but the problem doesn't appear to be the plug-in.

You can also PM me the log package after restarting the plug-in and I'll take a look at it.

  • 2 months later...
SHM Advanced

SHM

Posted
  • Author
Posted

Sorry for the delay.  I have deleted and re-installed the plugin with IoX restart via AC.  I have attached the PG3x logs and IoX logs and screen shots of the AC and UD mobile.  Interestingly, UD mobile shows all of the weather data points but the AC does not.  Seems to be an IoX display issue.  

ISY screen.png

UDM screen.PNG

AmbientWeather_4-29-2024_11156_PM.zip

bpwwer Advanced

bpwwer

Posted
Posted

Have you restarted the AC after the plug-in was installed?  The AC (not IoX) needs to be restarted after a plug-in is installed for it to understand the new nodes created by the plug-in.  

The log files are strange, like something is out of sync.  The PG3x log ends at 1:11:56pm with the line downloading log. However, the last line in the plug-in's log is at 3:08 and is "invalid API key", and there's nothing after that.  Possibly because the log is set to errors only and no errors happen after that.   

Looks like PG3x is 2 hours behind.

I found where the plug-in attempts to create the nodes and it looks like the IoX rejects them with a 404 (not found) error.  I don't  see anything wrong with what the plug-in is doing, this seems to be something failing in IoX.   I'd suggest power cycling and see if that fixes it.  If not, you'll have to submit a support ticket to UDI.

bpwwer Advanced

bpwwer

Posted
Posted

The AC is just an app, you exit and then re-launch.   

However, that won't effect IoX, when you restart IoX from configuration section, I don't know if that re-launches the AC or not. 

Because you're seeing 404 errors when PG3 asks the IoX to create nodes, it means something isn't working right on the box.  That issue may also prevent IoX from restarting from AC so I recommend you power cycle the box to force it to restart.  If that doesn't work, you'll need to submit a ticket to UDI.  

  • Solution
bpwwer Advanced

bpwwer

Posted
  • Solution
Posted

@SHM Ambient's API is not very easy to work with.  They tend to simply add data fields to the query results as by new hardware and don't document it very well.  There's also no versioning.  So stuff just suddenly appears.  There's also no way to know what data fields will be present because they don't provide any type of mapping from a hardware type to data fields.

Given the number of different stations and sensors that are available there are way too many combinations to try and have pre-defined node definitions for each.  So the plug-in looks at the data fields and dynamically creates node definitions to match what's being sent.  There are (again, not well defined) rules they mostly use for naming conventions.  Like the field name will end in 'in' if it is a field for an indoor sensor. 

All this is to say that plug-in is really just making guesses at what it should be creating.

Your station is the first one that has had a field called 'windgustdir'.   Many stations have a field called 'windgustmph' and given that Ambient could start using 'windgustkph'  or 'windgustms' at any time to represent wind gust speed in different units, the plug-in simply looked for a field that started with 'windgust'.    Thus the plug-in thought your station was reporting two windgust speed fields and the AC fails when there are two fields with the same type. 

I've modified the plug-in to recognize 'windgustdir' as a wind direction field and create the appropriate node value for that.  It should work for you now.  The new version is 2.0.12

Guest
This topic is now closed to further replies.
Go to topic listing

  • Recently Browsing

    • No registered users viewing this page.

  • Forum Statistics

    • Total Topics
      37k
    • Total Posts
      371.4k
×
×
  • Create New...