stevehoyt

@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

Not sure if this would work for your application but I have been running their stuff for almost a year now and it is working fine. https://shop.yosmart.com/pages/shop-all-smart-water-solutions

@asbril Good to hear that all has gone well and you like it. I am not using zwave or ziggbee so that won't be an issue for me. I ordered a ssd along with it too. So if I understand it correctly, you run the OS and user data on the main memory and in addition to the google backups also backup to the SSD? I had heard somewhere I should move my user data to the ssd. If you can, would you let me know what you think the preferred config might be. Thanks Steve

@asbril Hi again. After much waiting, it looks like my home assistant yellow will be arriving toward the end of the month. I have been running HA now for 6+ months on a PC along with google backups. I don't anticipate any issues moving over to the yellow, based on other earlier thread discussions. I just thought I would checkin with you, and see what your impressions were after running it for a number of months. Thanks Steve

@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

I second what Indymike says above, if all legs are connected in parallel and already bridged. I have one meter and panel that feeds 3 sub panels through out my house and a detached pool house. The shortest run to a sub panel is 30 feet, the longest is about 100 feet to the pool house. Insteon devices all work fine with no bridges or range extenders. In fact, I used to have range extenders and they caused more problems after dual band was released, so I removed them all.

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.

@shbatm As a final followup to the issues we had, I updated HA to 2023.7.1 and your version 16. I have attached the log files before and after the upgrade from 15 to 16 to show you the "new normal". The could not communicate with device: 14 7F 2D 1 error I know is an error on my side with Insteon All looks pretty good to me Thanks for all your help. home-assistant_2023-07-07T15-06-57.008Z.log home-assistant_2023-07-07T15-03-02.894Z.log

@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.

I got this error a few weeks ago too. I have been working with the developer. I think you will see a solution to the problem in the next few days.

@Mecheng70 Sorry for the late reply I was out of town. Are you running version 0.2.25 I did not have to do anything to see my batteries. I may be mistaken, but I think this is part of additions being added to the latest test versions.

I am out of town until Tuesday . I will try what you are asking Wednesday or Thursday and let you know if I have any issues. @shbatm

@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

just verifying that the files got sent.....I had a couple errors sending thempg3-backup-6-6-2023_71919_AM.zippg3-backup-6-6-2023_71919_AM.zippg3-backup-6-6-2023_71919_AM.zippg3-backup-6-6-2023_71919_AM.zippg3-backup-6-6-2023_71919_AM.zippg3-backup-6-6-2023_71919_AM.zippg3-backup-6-6-2023_71919_AM.zip @shbatm