stevehoyt

@photogeek54 Not to worry. I will be out of town for a week or 2, and am waiting for fixes from another developer before I can do any further testing. Steve

@photogeek54 Hi I am currently running prerelease 0.2.05. I see in the non production store that 0.2.061 is available. I have tried restarting the node server, reinstalling it, and restarting PG3. Regardless, the new version does not start. Should I stay at the version I am running or is there something else I need to do to update it. Thanks Steve

Thanks to everyone. It only lasted for 2 days. Now everything has returned to normal.

@photogeek54here's a snapshot of what I am seeing FYI

@Javi Thanks for your comments. This only started since I installed and began running the non production version of the solar edge nodeserver. I am running it to do testing for @photogeek54 . So are you saying I should reboot the nodeserver? I am running PG3 nodservers on a polisy. Or should I reboot the PG3 server or entire Polisy. Thanks Steve

@photogeek54 I am getting an error when starting the Admin console "already subscribed". I saw it once yesterday, but was able to get the console started and populated with values. I am getting it today and can get the console to start, but there are no values for anything i.e all node servers etc. The solar edge nodeserver is up and running correctly. It is passing data to HA via that udi to HA integration written by @shbatm I have included the error log from the admin console below. As this is preproduction let me know how you want me to proceed. i.e delete solar edge nodeserver and retry, submit to UDI, try something else...... Steve ISY Error Log.v5.5.9__Fri 2023.05.26 06.55.27 AM.txt

@photogeek54 Got it up and running with no problem. So far all values are populating. I will let you know any thoughts after watching it for a few days.

did you look in the MyQ history in the app. Sometimes there is additional info there as to where the command came from.

Thanks for checking. If there is anything you need from me to help, let me know

Hi @bpwwer I think your question points out the problem. I don't think the nodeserver is seeing the sensors (and some other available info). I have included a debug log file which shows what it is seeing. Some items are obvious some are not to me. I have included 2 screen shots of all the variables that I see looking at my weatherlink. Note the list on the right side of the screen shots. In addition I went to the Davis website and got info on retrieving the airlink info via an API. It looks like they have opened up a lot more info now. I don't know anything about api's hopefully that might mean something to you. here is the link. Thanks https://weatherlink.github.io/airlink-local-api/ WeatherLink_5-15-2023_84731_AM.zip

@bpwwer Good Morning Just wondering if you had an thoughts on my initial post? Thanks Steve

@photogeek54 I have a solar system with 2 inverters and 2 batteries. I would be willing to test it if you like. I will be out of town all next week but could try it the week after that.

If it is sensors you need, I am using yolink sensors to monitor pool ingoing and outgoing temp, along with the pool water level. It requires a hub and nodeserver like CAO. I Tried CAO, but my pool was too far away from the hub.

I thought I would publish a practical use for the Rainmachine @glarsen and Flume @Jimbo.Automates PG3 node servers . I started this project about a year ago and thanks to the help of the 2 above developers, making some changes for it, it has been running fine for many months. It takes the expected usage for each irrigation circuit ( from Rainmachine info ) and compares it to the actual usage ( from Flume ). If an excess water situation is detected, i.e. a malfunction in a circuit, an alert message is sent to me so I can fix the problem. All this is done via the ISY running on a polisy and the 2 PG3 node servers. This has been invaluable during our drought conditions. I recently added Home Assistant to my house. I use it for display purposes only. All control, warnings etc is still in the ISY / node servers. I did however create a visual interface so HA lets me know what is going on. I have attached 2 pictures below of it. The first shows usage vs expected for the last 4 days. The second shows it for the last run of the circuit. The purpose of this post is to let both developers know their work is of value and let other PG3 users see a practical application. I will post in both Rainmachine and Flume PG3 areas Steve

I thought I would publish a practical use for the Rainmachine @glarsen and Flume @Jimbo.Automates PG3 node servers . I started this project about a year ago and thanks to the help of the 2 above developers, making some changes for it, it has been running fine for many months. It takes the expected usage for each irrigation circuit ( from Rainmachine info ) and compares it to the actual usage ( from Flume ). If an excess water situation is detected, i.e. a malfunction in a circuit, an alert message is sent to me so I can fix the problem. All this is done via the ISY running on a polisy and the 2 PG3 node servers. This has been invaluable during our drought conditions. I recently added Home Assistant to my house. I use it for display purposes only. All control, warnings etc is still in the ISY / node servers. I did however create a visual interface so HA lets me know what is going on. I have attached 2 pictures below of it. The first shows usage vs expected for the last 4 days. The second shows it for the last run of the circuit. The purpose of this post is to let both developers know their work is of value and let other PG3 users see a practical application. I will post in both Rainmachine and Flume PG3 areas Steve

Hi I don't have the PG3 nodeserver running, but I am using the Home Assistant solar edge integration. I don't know what connection you have from the inverter to the internet. In my case, I have their zigbee connection. I have a lot of issues with the zigbee connection dropping. When it does, I get zero values or non numeric data in numeric fields. You can see if the zigbee connection is up by looking at your inverter for the S_OK message. Granted it is not the same as you, but your symptoms might be due to bad data I am seeing too. As an aside, their servers at the moment have sent me a message that they are running slow. Steve

I should have mentioned it. I am on a polisy too. Here are 2 captures

if it is any help to @bpwwer. I have 6 nodesevers running. Kasa, Rainmachine, Flume, weather link, wireless tags, and Yolink. Yolink is the only one displaying the version number. I am running 3.1.18 have been leery of upgrading, due to some issues I have seen, as this version is very stable.

I noticed the same thing on most of my node servers. Awhile back, PG3 quit displaying the version number. 5 out of my 6 node servers just show production like you show in your screenshot

as an aside... I don't use the tesla nodeserver so can't comment on the polling interval. My tesla model s was using 2KW per day just while sitting in the garage. After much searching on the internet, I found that I could reduce this to zero by turning off the "cabin overheat protection". The car was NOT turning on the ac/heating. For some reason, this setting kept the car awake all the time which used the 2 KW per day. So if your polling often, this might be what would be expected in usage.

Good Morning Just upgraded and the temp is there now. Thank You

@Panda88 Hi Not sure if you prefer info communicated via this forum or GitHub so I have posted this in both places. Can we get the temp value sent to the isy for motion detectors. Thanks

I just installed this Node Server. Install went with no problems. I noticed in the writeup and upon testing, that no values are available for the Air Quality Index monitors. I have 2 of them. One inside and one outside. Any chance of adding these in the future. No rush. Thanks AirLink Air Quality Monitor by Davis Instruments BY DAVIS INSTRUMENTS SKU 7210

look under pg3 node servers... it is close to the bottom

you might check the yolink thread here for future needs. There is a discussion about remotes