Jimbo.Automates

Hey @bpwwer Realized my weatherflow wasn't working, and found just this in the log: 2022-02-03 18:15:00,052 Thread-1563 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.8/threading.py", line 932, in _bootstrap_inner 2022-02-03 18:15:00,057 Thread-1563 udi_interface ERROR udi_interface:write: self.run() 2022-02-03 18:15:00,058 Thread-1563 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.8/threading.py", line 870, in run 2022-02-03 18:15:00,062 Thread-1563 udi_interface ERROR udi_interface:write: self._target(*self._args, **self._kwargs) 2022-02-03 18:15:00,063 Thread-1563 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/00:0d:b9:52:bf:fc_9/nodes/weatherflow.py", line 420, in poll 2022-02-03 18:15:00,066 Thread-1563 udi_interface ERROR udi_interface:write: eto = self.eto.doETo() 2022-02-03 18:15:00,067 Thread-1563 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/00:0d:b9:52:bf:fc_9/nodes/et3.py", line 361, in doETo 2022-02-03 18:15:00,069 Thread-1563 udi_interface ERROR udi_interface:write: return evapotranspriation(self.temp_max, self.temp_min, None, self.WindSpeed(), self.elevation, self.rh_max, self.rh_min, self.latitude, self.canopy, self.day) 2022-02-03 18:15:00,070 Thread-1563 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/00:0d:b9:52:bf:fc_9/nodes/et3.py", line 180, in evapotranspriation 2022-02-03 18:15:00,073 Thread-1563 udi_interface ERROR udi_interface:write: Rs = calc_solar_radiation(min_t, max_t, latitude_r, declination, julian_day) 2022-02-03 18:15:00,074 Thread-1563 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/00:0d:b9:52:bf:fc_9/nodes/et3.py", line 122, in calc_solar_radiation 2022-02-03 18:15:00,076 Thread-1563 udi_interface ERROR udi_interface:write: Rs = 0.17 * math.sqrt(t_max - t_min) * Ra 2022-02-03 18:15:00,077 Thread-1563 udi_interface ERROR udi_interface:write: ValueError 2022-02-03 18:15:00,077 Thread-1563 udi_interface ERROR udi_interface:write: : 2022-02-03 18:15:00,078 Thread-1563 udi_interface ERROR udi_interface:write: math domain error 2022-02-03 18:15:06,749 Thread-5 udi_interface ERROR weatherflow:udp_data: Failed to send data to ISY: update() takes 2 positional arguments but 3 were given 2022-02-03 18:15:33,376 Thread-5 udi_interface ERROR weatherflow:udp_data: Failed to send data to ISY: update() takes 2 positional arguments but 3 were given I restarted and still seeing the issue. This is with the original Sky, I haven't swapped out for the new Tempest yet.

With IoP we can now put ${sys.program.#.name} and ${sys.node.#.name} in the Path for Network Resource, but if the program or node name contains spaces it sends a bad post command. Normally if the Path has spaces you can set "Encode URL" to fix them, but when using ${sys.program.#.name} you can't enable "Encode URL". How do we get around that, besides naming the Programs with + signs instead of spaces? This is an extremely using enhancement, but not being able to fix spaces makes it very limiting. Or maybe I'm missing something? I'm sure @MWareman or others must be using this?

Thanks all for confirming! Sent from my Pixel 6 Pro using Tapatalk

The Polyglot Version 3 Nodeserver for CAO Wireless Tags version 3.0.13 is released. If you are going to buy a Tag Manager or any Tags, please use my affiliate link: https://goo.gl/rXAGk9 See the README for more information, including information on moving from PG2. The Release Notes are also available.

@garybixler I have reproduced your issue and will debug further.

Please PM me the log or email jimboca3@gmail.com

Sorry, there is a delay, it's there now.

It's a known issue that the version shown in the store listing is updated before the NS will actually see the version, @bpwwer is working on better ways to keep that in sync. But I just restarted my production and it's 3.0.12

Sorry, I missed this. Let me know if it's still happening.

The Polyglot Version 3 Node server for Flume Water https://flumewater.com/ version 3.0.11 released. If you are going to buy one, please use my affiliate link: https://flumewater.com?grsf=0tbrt2 See the README for more information. The Release Notes are also available. I can no longer use this device because my water company installed a fancy new meter that is not compatible, but I will continue supporting the best I can. I still have the hub turned on to test, but can't see any water flow.

Yes! Being able to look at programs in safe mode would be very helpful! It failed for me as well.

Really think it's fixed this time, 3.0.12 released...

Really think it's fixed this time, 3.0.12 released...

The Polyglot Version 3 Nodeserver for CAO Wireless Tags version 3.0.12 is released. If you are going to buy a Tag Manager or any Tags, please use my affiliate link: https://goo.gl/rXAGk9 See the README for more information, including information on moving from PG2. The Release Notes are also available.

No, it's not waiting on the tag manager, it's trying to throttle adding nodes to the ISY so it doesn't overwhelm it. But the udi_interface (the module between the NS and PG3) is multithreaded and not all python list functions are thread safe, so the code gets confused. I need to figure out how to make the code thread safe, or use a Python mutex.

Ya, others reporting it's still having issues. Working with @bpwwer to figure out a solution.

Ok, bummer, and yes I've been discussing this issue with Bob, not sure yet what we can do, but will try to figure it out soon.

Hit the load profile in PG3 NS then open admin console. Sent from my Pixel 6 Pro using Tapatalk

Yes, the license will be fine. Sent from my Pixel 6 Pro using Tapatalk

Awesome! Yes multiple copies of NS running seems to be happening a lot. Sent from my Pixel 6 Pro using Tapatalk

The Polyglot Version 3 Nodeserver for CAO Wireless Tags version 3.0.11 is released. If you are going to buy a Tag Manager or any Tags, please use my affiliate link: https://goo.gl/rXAGk9 See the README for more information, including information on moving from PG2. The Release Notes are also available.

OK, found the issues, should really be fixed in 3.0.11. It's actually common code in all my nodeservers so now I need to fix them all. It doesn't occur all the time, only if the ISY is slow to add a new node, which happens...