chuckl

Is there a trial version available for this plug-in? The PG3x store shows a purchase option only.

Just tried installing this NOAA plug-in on IoX 5.8.0 running on Polisy. Log indicates errors when starting. I followed the instructions in the GitHub repo listing at GitHub - BME-nodeservers/udi-noaa-poly: Polyglot V3 node server for NOAA weather data. My location is Castaic, CA. NOAA - National Weather Service - XML data feeds - Current Conditions notes a weather station to use is KLAX. NOAA's National Weather Service - California Watch/Warning RSS Feeds by Zone Forecast shows my zone as CAZ088 or CAZ288 (tried both, same error) NOAA's National Weather Service - California Watch/Warning RSS Feeds by County Forecast shows my county as CAC037 (tried both, same error) Any help would be appreciated. NOAA debug - 20240120-1.log

Please explain your question of running cloud vs. local. How do I determine that? There's no initialization in the log file because the plug-in has been running for > 24 hours. Do you want me to start / stop it? Is there any documentation on this plug-in? Is it in github?

I'm not sure if the values displayed in these screens are accurate. Specifically, the Battery Power, Consumption, and Total Power for today and yesterday don't look right. The values do not agree with what is shown in the Tesla Mobile App. Also, what is the "Generator Status" tab? Log files (set to Debug Level) & screenshots attached. System parameters that may be relevant: in "pre-PTO" (Permission to Export = No, Grid Charging = No) 9.6 kWh / 2 Powerwalls (1PW+, 1PW2) Backup Reserve (30% Backup, 70% Self-Powered) Operational Mode: Self-Powered -- PWs supply the house at night, solar during the day, nothing from the grid Sunrise: 6:36, Sunset 18:45 TeslaPW_11-27-2022_70820-AM.zip

Thanks for your reply! I did verify that I entered the correct credentials in the NS config and was logged in shortly after the two 'DSsolarMeter' entries were noted in the 0800 hour yesterday as the NS showed "connected" status and was displaying live data. I verified this by going to a separate browser window successfully gaining entry by entering the same credentials. The error persisted to the 1500 hour when I initially wrote this post. After your response, I repeated the PW POPO procedure multiple times during the first five minutes of a Node Server restart. The 3rd try seems to have resolved it. No more error. Again, thank you!

Enclosed is the log package. I cycled the PW during a startup and it didn't resolve the error. If it's any help, this is a new system with app settings: Operational mode: Self-Powered Permission to Export: No Grid Charging: No In the UI, it looks like it's closely tracking the app values. TeslaPW_11-19-2022_10207-PM.zip

While trialing this Node Server on my Polisy, I'm also getting a similar error in the Real-time ST-Inventory log file: ST-Inventory(3) Current Status: Connected Current Version: 1.0.8 [Production] Time Started: Nov 19, 2022, 11:53:50 AM 2022-11-19 12:33:59 error: POLY: getInv() Error: http://192.168.1.57:8080/rest/networking/resources 2022-11-19 12:34:11 error: NS: Parsing Error: TypeError: Cannot read properties of undefined (reading 'includes') at _0x435040.processNetworkResources (/var/polyglot/pg3/ns/000db9594260_3/Nodes/ControllerNode.js:1:5971) at _0x435040.onDiscover (/var/polyglot/pg3/ns/000db9594260_3/Nodes/ControllerNode.js:1:3118) Around that time, the Real-time Polyglot log file has: 11/19/2022, 12:32:52 [pg3] info: EXPIRE CHECK: ST-Inventory subscription expires in 6 days 11/19/2022, 12:33:29 [pg3] info: [00:0d:b9:59:42:60_2] controller reporting command DOF 11/19/2022, 12:33:30 [pg3] info: [00:0d:b9:59:42:60_4] controller reporting command DOF 11/19/2022, 12:33:35 [pg3] error: No code in error response 11/19/2022, 12:33:35 [pg3] error: ISY Response: [Try: 1] [00:0d:b9:59:42:60] :: [404 - OK] :: 5.679907ms - http://192.168.1.57:8080/rest/ns/2/nodes/n002_climate1/report/status/GV14/False/25 11/19/2022, 12:33:53 [pg3] info: set to expire on 2022-11-26T19:52:26.000Z 11/19/2022, 12:33:53 [pg3] info: EXPIRE CHECK: ST-Inventory subscription expires in 6 days

Thanks for your responses. I ended up going with the Rachio controller. Although the price was the comparable for both controllers, RainMachine has: the $29.95 yearly subscription for remote access whereas Rachio is free another $20 for the plug-in whereas Rachio is free the plugin offers no trial, there is no PG2 version that I can find, and I avoid buying something unknown

Please advise on this error ... Current Status: ConnectedCurrent Version: 0.1.15 [Production] 2022-11-18 15:49:43,940 Thread-26 udi_interface ERROR TeslaInfo:pollSystemData: Exception PollSystemData: 'tesla_info' object has no attribute 'DSsolarMeter' 2022-11-18 15:49:43,941 Thread-26 udi_interface ERROR TeslaInfo:pollSystemData: problems extracting data from tesla power wall 2022-11-18 15:49:43,942 Thread-26 udi_interface ERROR TeslaPWController:longPoll: Problem polling data from Tesla system

I'm evaluating candidates for control of my sprinklers and have narrowed it down between the Rachio and RainMachine hardware. I cannot seem to access a trial of this poly. Any advice?

Upgraded from the .15 release with no issues.

I second this idea! Chuck

Status Update: As of today, there have been no more incidents of time shifting by my ISY. My ISY NTP is currently pointed to 3.north-america.pool.ntp.org as suggesed and as a precaution, I now CLOSE the Admin Console after use instead of minimizing it and having it run constantly.

Up early on a Sunday (the only day I can sleep in) because the ISY set my Work Day rountines to run. At 12:26 this morning, the ISY log indicated Mon 09/01/1941 08:30:00 PM -AND- The Program Summary of the ISY indicated a last run time of some programs of 10/08/1977 at 2:58AM *** Here's the interesting part: I then shut down the Admin Console down, restarted it, and the bad run times are gone! Blanks now appear in their place. Took a snapshot of everything and all of it along with a backup of my ISY is on the way to ISY Support. I have a basic ISY. How do I know if I've hit the wall for program stack space and need to purchase the PRO upgrade?

Cancel that! Wrote too soon. See my new thread.