stevehoyt

No problem go ahead and run it for a couple days and lets see what happens. I don't know if Davis has any limitations on how often we can query. If so, I can shut mine off for awhile until you get the data you need and it won't hurt me. I am not sure what your options are for changing the nodeserver are, but I don't have a problem deleting a station in the node server for now. I rarely restart it so no big deal. Per benoit's answer below to me. Is it hard to just do the poling via 1 thread only as a permanent fix? "I think the problem appears when the nodeserver tries to publish data simultaneously from 2 threads. I contacted Bob, and the nodeserver indeed can publish from 2 threads. When polling, there will be one thread per weather stations, and they basically get polled at the same time. This means that it is likely that publishes can happen at the exact same time.

@bpwwer I see that Benoit has talked to you about this issue. What are your thoughts? Should we have the option to turn off one of the consoles? I know I can delete it in the config section. I would be perfectly satisfied to turn off one of the consoles. Most of the data ( except indoor temp humidity etc) is all coming from the same outside source, so it is redundant. I have multiple consoles so that I see the info in different rooms. The one I would turn off in my case would be "Steves House" Steve

FYI I am seeing about 10 of these errors per day. Also see an occasional similar error from the solar edge nodeserver. If you think it would be of value, I can open a ticket with UDI. About all I could say is to contact you as you know what is going on. As I am running a Polisy not EISY I doubt anything would get done. Let me know if you think it would be of value otherwise I will just live with it for now.

I'll keep your comments in mind and watch what is going on when I see the errors again. Xfinity internet has been flakey the last few days here. That may be the cause. Pardon my ignorance I know nothing about MQTT, but where is the MQTT broker living. Since I have a polisy I assumed everything was on it. Thanks

@bpwwer Got the fixed version installed. So far all looks OK. I'll keep checking. I have been seeing disconnects every few hours though. I have attached a log file for you to look at. Note the ones around midnight and 3 AM. Are you seeing the same thing on your connection to me. Steve Davis_V2_10-4-2023_61205_AM.zip

@bpwwer I just tried the new version. No change as far as data for the airlinks being displayed. Also for the fun of it I tried to write a program with an if statement on both of the airlinks and the parameters do not appear in the if. I am not sure if that means anything. No idea why you would not see both airlinks, but if I had to guess it probably is related to the weather link pro share. I will message you privately with the API v2 keys. Why don't you see if that makes a difference. I am not sure how much polling they will allow, but for now lets give it a try. If you need me to I could delete one and see if the data would display then. I prefer not to do that if possible but will if needed. I could try deleting it from your config file too if that would help. Let me know what else I can do.

I should have told you I changed the name from office to equip closet. as I moved it. We both should be looking at the same thing, perhaps the renaming caused the problem. Anything I could do to help figure this out?

@bpwwer a bit of new info. I stumbled on this z-wave X-ray this morning. It shows the airlink info is there, apparently the admin console can't display it for some reason. FYI i cleared java cache and redid the test. Still the same results.

just updated to 5.7.0 on Polisy and all programs were disabled.

@bpwwer There does appear to be something wrong with my airlink fields getting updated the admin console.It does not appear ever to be updating. I never see what you had shown in your other post for an airlink. . Whenever I select airlink it shows the last item I selected. See an example below I had selected the Vantage pro first and then went back to the airlink. To make sure all was well, this AM I updated all modules on the PG3. I then deleted Davis V2 and restarted the Admin Console to clear everything. I then reinstalled the Davis V2 node server and restarted the Admin Console. Same thing. If I look in the PG3 nodeserver logs it is setting up my 2 airlinks OK. I quickly checked if they showed up in the info sent from UDI to Home assistant app and they appear to be ok. So it looks like an Admin Console issue. Here are the versions I have currently installed. Let me know what you think I should try next. PS When you try it from your side connecting to my station is everything ok? Very weird if it is. Thanks Steve

@bpwwer I restarted the node server....here are the log files and log file packages in debug mode. As you can see above my airline info in the admin console does not look like what you showed in the other thread. Thanks Steve Davis_V2_9-27-2023_81346_AM.zip Davis_V2_9-27-2023_81336_AM.zip

Good Morning @bpwwer I just installed the new beta version in a new slot and deleted my old version. Most of it seems fine but am seeing a couple errors. I assume you are still using my station too. Can you let me know what you think. Various screen shots below

@bpwwer You can ignore the message above....Got updated to pg3x 3.2.2 and it has now started. Thanks

I restarted it and this is the error I got. See info below. I'll try and update to PG3X this afternoon or tomorrow. So don't spend a lot of time worrying about this error. It might be fixed with PG3X. 8/23/2023, 11:11:58 [pg3] info: [WeatherLink(15)]: Restarting Nodeserver 8/23/2023, 11:11:58 [pg3] warn: [WeatherLink(15)]: Was not running. Starting... 8/23/2023, 11:12:01 [pg3] info: startNs:: WeatherLink 8/23/2023, 11:12:01 [pg3] info: startNs:: WeatherLink is valid 8/23/2023, 11:12:01 [pg3] info: checkLicense:: WeatherLink Valid perpetual license found. 8/23/2023, 11:12:01 [pg3] info: startNs:: WeatherLink finished update check 8/23/2023, 11:12:01 [pg3] info: [WeatherLink(15)] :: Starting NodeServer - Version 2.0.4 8/23/2023, 11:12:01 [pg3] info: startNs:: WeatherLink updating database (enabled, timestarted) 8/23/2023, 11:12:01 [pg3] info: MQTTS: Client Connected: pg3frontend_fFNiD 8/23/2023, 11:12:02 [pg3] error: [WeatherLink(15)] :: STDERR: File "/var/polyglot/pg3/ns/000db9594020_15/./wll.py", line 1 V8', 'value': 0, 'uom': 56, 'name': 'Wet Leaf 1'}, ^ 8/23/2023, 11:12:02 [pg3] error: [WeatherLink(15)] :: STDERR: SyntaxError: invalid syntax 8/23/2023, 11:12:02 [pg3] info: [WeatherLink(15)] :: Exit cause code: 1 - signal: null 8/23/2023, 11:12:02 [pg3] info: startNs:: WeatherLink starting polls 8/23/2023, 11:12:02 [pg3] info: Starting WeatherLink Info timer 0 8/23/2023, 11:12:02 [pg3] info: Starting WeatherLink Version Check timer 8/23/2023, 11:12:17 [pg3] warn: MQTTS: keepaliveTimeout: pg3frontend_fFNiD 8/23/2023, 11:12:17 [pg3] error: MQTTS: clientError: pg3frontend_fFNiD keep alive timeout 8/23/2023, 11:12:17 [pg3] info: MQTTS: Client Disconnected: pg3frontend_fFNiD 8/23/2023, 11:12:22 [pg3] info: MQTTS: Client Connected: pg3frontend_fFNiD 8/23/2023, 11:12:54 [pg3] info: [00:0d:b9:59:40:20_12] controller reporting command DON 8/23/2023, 11:12:54 [pg3] info: [RainMachine 12] :: STDOUT: PING 192.168.0.34 (192.168.0.34): 56 data bytes 8/23/2023, 11:12:54 [pg3] info: [RainMachine 12] :: STDOUT: --- 192.168.0.34 ping statistics --- 1 packets transmitted, 1 packets received, 0.0% packet loss, 1 packets out of wait time round-trip min/avg/max/stddev = 5.673/5.673/5.673/0.000 ms 8/23/2023, 11:12:55 [pg3] info: [00:0d:b9:59:40:20_14] setup reporting command DOF 8/23/2023, 11:13:31 [pg3] warn: MQTTS: keepaliveTimeout: pg3frontend_fFNiD 8/23/2023, 11:13:31 [pg3] error: MQTTS: clientError: pg3frontend_fFNiD keep alive timeout 8/23/2023, 11:13:31 [pg3] info: MQTTS: Client Disconnected: pg3frontend_fFNiD 8/23/2023, 11:13:36 [pg3] info: MQTTS: Client Connected: pg3frontend_fFNiD 8/23/2023, 11:13:54 [pg3] info: [00:0d:b9:59:40:20_12] controller reporting command DOF 8/23/2023, 11:13:54 [pg3] info: [RainMachine 12] :: STDOUT: PING 192.168.0.34 (192.168.0.34): 56 data bytes 8/23/2023, 11:13:54 [pg3] info: [RainMachine 12] :: STDOUT: --- 192.168.0.34 ping statistics --- 1 packets transmitted, 1 packets received, 0.0% packet loss, 1 packets out of wait time round-trip min/avg/max/stddev = 6.564/6.564/6.564/0.000 ms 8/23/2023, 11:13:55 [pg3] info: [00:0d:b9:59:40:20_14] setup reporting command DON

Any idea why I get the message log file not found when I try and look at it? Thanks

@bpwwer Hi I was thinking about asking you how your test was going. Before I did however, I looked in the nodeserver non production store thinking I might find the same version you are testing and try installing it I did not see one...no big deal. I then saw the notice that 2.0.4 was available. I installed it. It says it started but did not. Also I get a log file error if I try to look at the log. Any ideas? Software versions below.

@bpwwer I think I got it setup. Sent you a private message with the info. Let me know if it does not work.

@bpwwer No problem sharing info. Not sure if you need my API key and login info or not. For now I set the station to public and here is my URL https://www.weatherlink.com/bulletin/a4cf142c-4278-4caa-8f2a-075ff6aef066

here's a very old video about the problem. Not sure it is still relevant but at least taking a look in the event log might give you a clue.

@MrBill Do you think this might be something others might want, and a feature request to UDI would be in order? Would it be difficult for them to implement? Many years ago when I was a programmer we used these lines as documentation too.

I have been looking through the wiki, but can't seem to find a way to "comment out a line" I am aware of the comment command, but it does not do what I need. In particular, I have messages that I have inserted in programs when debugging. After everything is working, I would like to be able add a character such as a # before a command. This would stop the command from executing without having to delete the line. The idea being, I would not have to redo the line should the need to debug arise in the future. Does anyone know a way to do this. Thanks Steve

thanks will do.

Hi @bpwwer I am working with @shbatm and the Home Assistant integration. He encountered the problem below... 1st paragraph. 2023-06-28 09:48:38.736 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.inverter_1_apparent_power (<class 'custom_components.isy994.sensor.ISYSensorEntity'>) is using native unit of measurement 'VA' which is not a valid unit for the device class ('power') it is using; expected one of ['W', 'kW']; He suggested I send you a request for the enhancement ... 2nd paragraph Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author. I will have to add a check for this and classify it as an "Apparent Power" device class in Home Assistant. This module uses the ISY's control names to determine device classes, and that node server uses "CPW" (Power) for the apparent power. It doesn't look like the ISY actually has a control for Apparent or Reactive Power (e.g. "APW"/"RPW"), just power and total_power_used (TPW). May be something to suggest to them to add. Thanks Steve

I have a Flume and a Rain Machine controller. I use it to detect problems in a given circuit. If > x + 1 gallons is running where x = expected flow, I send an alert to check for a problem with that circuit. I have a large yard with 20+ circuits and due to dogs, squirrels, and gophers etc., have frequent problems, especially with the drip irrigation.

For more reasons than the node server, you should pursue getting it changed to be a single site.