macjeff

Can you update (if needed) to make this work in advance of the change? Jeff ----- Security image expiration Dear Netatmo developer, As of today, the images you get from the API, such as snapshots, vignettes or even profile images, do not expire. For security reasons, the retrieved URLs will now expire. Starting from the 09/05/2023, you will receive, along with the image URLs, an 'expire_at' field. The expiration time will be set at five minutes when rolled out but keep in mind that this value can change. As a result, you must take into account the 'expires_at' field that you will receive in the payload. What does it means for you ? Impacted API endpoint are : /homesdata when retrieving the image of each person /getevents when retrieving snapshots and vignettes If you do not download immediately the image URLs of these two API endpoints, you shall modify your code to handle the expiration time. Once the URLs are expired, and if you try to download the images again, you will receive a 404 HTTP error. You have to make a new API call to retrieve new URLs. Sincerely, Legrand - Netatmo - Bticino

I appreciate your response. Been a long day and glancing at the messages just got me stressed We think we know the issue. The timeout on the pushes needs to be increased. Logs show them timing out at 10 seconds so it tries again but it already was received. It just timed out before it got the success message. Will post once we know for sure.

But some of the duplicated notifications were not from my ISY at all. They were from the portal saying Up or Down and that kept duplicating. Doesnt that rule out programs? And as I said either in email to you or here (getting confused) that I noticed now that every time I get these strange pushes from multiple programs all at the same time there are UP DOWN messaages also duplicated. So I wonder if something is happening in connection. I had up and down portal messages YESTERDAY and look at the timestamps on the portal. It shows it was up yesterday. See screenshots. The difference in the two dates was a manual reboot but the important thing is that i got 20-30 up down duplicated messages from the portal at the same time as the driveway and others yesterday and portal shows UP!!! If it said Wednesday it would correspond with the ISY offline stuff. (please note I deleted my pushes from yesterday because I had over 100 so I cant screenshot them. Lets just take a wait and see approach. It could be portal maintenance or some other glitch and it may go away on its own. Also the periods are under 30 min where push notifications duplicate and I get the up down portal messages. But PLEASE dont waste your time looking at logs just yet!!!

see post I just sent. I am going to back out of my own conversation as everyone is attacking me and thats not what the forum is supposed to be about. I have helped many here. I am very experienced with the ISY and you said to post so I did. I just dont like responses like I am the problem. It could be random internet drops, duplicated UUID on push server. Lots of things. But its not the programs. Even disabled the problem happened with pushes from the portal.

I feel like I am being attacked here for posting. I have been doing this for many many years. I had the original ISY, and then the 994i, then Polisy, now IOP. So I know this stuff pretty well, and the pushes have been in place since the notification nodeserver started supporting push (and not just PUSHOVER). Never had issue until about 10 days ago. With that said, I have had a busy week but forgot to post something very important. Last week I put ALL PROGRAMS into a folder and disabled it. No programs could run. I was out of town so really did not care. I then rebooted my ISY. After the reboot I got duplicate down and up PUSH notifications from the portal over and over for 30 min. I have TWO ISY's and I rebooted them both at the same time. I then verified both showed UP SINCE...... at the same time in the portal and they did and I continued to get duplicate push notifications from the portal. Then they just stopped on their own without me doing anything. I only get them from one of my ISY's because only one is registered with UD Mobile. So my programs were disabled and the push came from the portal not my ISY. I was told to post the latest program by Javi so I did. That was a mistake because unless there are two issues, it has nothing to do. And the pushes came from all different programs. I think my post led people to believe it was the program. Any pushes during the period of duplication (Every one had PORTAL messages mixed in) would duplicate and then it would stop. BTW...I then turned programs back on last week and no issues for the weekend but then got it again yesterday. Maybe this is as simple as some sort of connectivity issue to the portal, but why would the portal say online for 2 days. Like it happened yesterday (Wednesday) and right now it says online since Tuesday but I got portal down messages yesterday. A screenshot below shows the portal messages. I had pages of them and again the portal showed it had been online for 20-30 min and I was still getting up/down/up/down. Maybe I should just hide this entire conversation since it seems to be causing me more of a headache then the original issue!!! I was just trying to see if anyone else had this issue. So far no issues today at all.

Ok here is all I know Happened 3 times so far in last 10 days All three in the AM but not the exact time. When it happens ALL of the programs that are triggered during the time the problem starts send duplicate notifications. Even a program that has one line to send a notification triggered once and then I got about 3-4 pushes a minute for 20-30 min the other day The program itself that sends the notification is only running once. I can confirm that with a variable counter and other things that would be fired by the program and are not. This usually goes on for about 30 min or less and then stops. I will get the notifications about every 20 seconds. If I check the program logs the last run and finish time is during those 30 minutes but lots of pushes since it last showed finished. It did not happen today. Last time was yesterday. And it happened on different days of the week If the notification node server is set to send to ALL devices (not just one) then all of them get all the duplicate pushes. I don't need any assistance as its not on my end. I agree with JAVI that its most likely a loop either happening in the Push Server or Apple. Just wanted to report it here

I was fooling around with program and had copied some stuff and forgot to remove it. The duplicate variable set is gone but that was after the issue. the program has nothing to do with issue. I think it’s on apples side. The push notifications get in a loop and keep coming in and then randomly stop. And then days later start again. it only started about 10 days ago and random on programs. One day one program might do it and the next time another one and sometimes if you at the same time. I even did some test programs with just a push in the program and it did it eventually There’s nothing happening on the ISY side so it’s something to do with the push notification server or Apple

Using ISY on Polisy. 5.5.9. Using Notification Nodeserver 3.4.6 Virtual Button is a nodeserver that you push a button to trigger a routine on Alexa. Its easier than setting up variables to trigger alexa. One thing to note- the button was only pushed once so the program only ran once. Some programs dont have virtual button. And one program is just a WAIT and then the notification server line. The only common denominator is notification nodeserver that are in all the programs. The last run time was right when the issue started but it duplicated for several minutes and all programs had been finished. I added a variable counter to each program. It reset at midnight last night. After I got 8 of the notifications the counter said 1. I then ran the program manually and it said 2. Then I got many more so I checked and it still said 2. This could be apple issue. But all of our devices get the same push randomly from almost every program but once the issue stops they all stop. It last happened last Monday Morning. Then again today so over a week later. So I wont post the program unless you really want to see it as the counter, the last finish time, and other things prove the program has only been run one time but the notification itself gets stuck in a loop and keeps sending. UPDATE- On the ones that were doing it this AM, I just went to the notification server line of the program. I re-selected the device (ALL DEVICES) and then hit update. I then saved the program. So far they have not done it, but whatever is causing this could have been fixed on the cloud side (Apple or UD) so my fix may have just been a coincidence.

I filed a ticket but was told to post here. Its not all but many programs. Pushes send over and over from UD Mobile. One time for hours and I got like 3-4 per minute. And ALL the devices get the pushes not just one. They stop on their own. And I can manually run the THEN of a program and it starts the loop again But I have counter in programs and it only runs once. Plus another parts of program only run once (As log shows) so its not the program I did get somewhere today on this. All I did is click on the notification server and reselect ALL devices and save it and so far so good. So UD said to post the program. Here it is with the PUSH line selected *** So now I have reselected every PUSH line in programs that are sending duplicate programs, clicked update and save So far now they are all working fine but we shall see as it comes in waves.

I have a message that ST Inventory needs an updae. I saw you took out the update on restart option. I could not find a way to update it. I restarted the nodeserver and after that a button appeared that said UPDATE under the configuration. It was not there before. I updated and all went well. Does the extra restart need to be done to get the UPDATE button to appear? I also wanted to note that if you go to the nodeserver and click on install this text is still there which is incorrect now NOTE: If you are trying to upgrade an existing installation of ST-Inventory, stop and re-start it from the dashboard. It will automatically load the newest version available. Installing from here will add the ST-Inventory to a new slot.

My store shows last update was 3/19 and it was 20. No sign of 21 but I have seen it take hours. I am running on Polisy not EISY so the latest version there is 3.1.19

I did not realize it would also report false updates so from now on I will sort the store by date and if the date shows a recent update then I will update.

I reported it to him @bpwwer in PM. Just so you know I reported I am having issues where some nodeservers say PRODUCTION with no version. Restarting PG3 brings back the version. He said its a known issue and as real updates come out they will be fixed as its part of the code that needs to be added to each nodeserver not pg3. But this AM, I had 3 nodeservers with update needed message and notification was one of them. BUT they were already up to date. And checking the store showed no update in last day or so and I check daily for updates. So I went ahead and restarted the three nodeservers. The version number reappeared and message went away. But 2 min later one of them came back. So I restarted pg3. Now all of them show versions and no update message. But Notifcation said failed and airthings said failed too. So I rebooted again. Notification was working then but airthings still said failed. I left it and went out and came back and airthings message changed. It now said my poll was 60 and needs to be 120 so I changed poll to 180 and its working now. So for now its all working but wanted to let you know the chain of events.

I rebooted again and its working I downloaded a log file earlier so see if this helps. Notification_3-22-2023_73720-AM.zip

Says something about threads can only be started once. All I did was reboot PG3. Jeff 2023-03-22 09:33:58,336 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-03-22 09:34:02,071 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.55 Starting... 2023-03-22 09:34:02,537 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.1.18 [ISY: 5.5.9, Slot: 15] 2023-03-22 09:34:02,540 MainThread udi_interface.interface INFO interface:__init__: Connect: Network Interface: {'addr': '172.16.1.210', 'netmask': '255.255.255.0', 'broadcast': '172.16.1.255'} 2023-03-22 09:34:02,543 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:1888 2023-03-22 09:34:02,547 MainThread udi_interface.interface WARNING interface:start: No node server version specified. Using deprecated server.json version 2023-03-22 09:34:02,549 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: controller not found in database. 2023-03-22 09:34:02,551 MainThread udi_interface DEBUG Controller:init_typed: enter 2023-03-22 09:34:02,552 MainThread udi_interface.custom INFO custom:_save: Sending data customtypedparams to Polyglot. 2023-03-22 09:34:02,553 MainThread udi_interface DEBUG Controller:init_typed: exit 2023-03-22 09:34:02,554 MainThread udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2023-03-22 09:34:02,555 MainThread udi_interface.interface INFO interface:addNode: Adding node Notification Controller(controller) [None] 2023-03-22 09:34:02,555 MainThread udi_interface.interface INFO interface:setController: Using node "controller", driver "ST" for connection status. 2023-03-22 09:34:02,626 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2023-03-22 09:34:02,628 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:0d:b9:53:2c:34_15 - MID: 1 Result: 0 2023-03-22 09:34:02,638 Publish udi_interface ERROR udi_interface:write: Exception in thread 2023-03-22 09:34:02,638 MQTT udi_interface.interface ERROR interface:_startMqtt: MQTT Connection SSLError: [SSL: BAD_LENGTH] bad length (_ssl.c:2488), Will retry in a few seconds. Traceback (most recent call last): File "/var/polyglot/.local/lib/python3.9/site-packages/udi_interface/interface.py", line 530, in _startMqtt self._mqttc.loop_forever() File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 1756, in loop_forever rc = self._loop(timeout) File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 1181, in _loop rc = self.loop_write() File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 1577, in loop_write rc = self._packet_write() File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 2464, in _packet_write write_length = self._sock_send( File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 649, in _sock_send return self._sock.send(buf) File "/usr/local/lib/python3.9/ssl.py", line 1174, in send return self._sslobj.write(data) ssl.SSLError: [SSL: BAD_LENGTH] bad length (_ssl.c:2488) 2023-03-22 09:34:02,639 Publish udi_interface ERROR udi_interface:write: Publish 2023-03-22 09:34:02,661 Publish udi_interface ERROR udi_interface:write: : 2023-03-22 09:34:02,662 Publish udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2023-03-22 09:34:02,662 Publish udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 980, in _bootstrap_inner 2023-03-22 09:34:02,666 Publish udi_interface ERROR udi_interface:write: self.run() 2023-03-22 09:34:02,667 Publish udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 917, in run 2023-03-22 09:34:02,670 Publish udi_interface ERROR udi_interface:write: self._target(*self._args, **self._kwargs) 2023-03-22 09:34:02,672 Publish udi_interface ERROR udi_interface:write: File "/var/polyglot/.local/lib/python3.9/site-packages/udi_interface/interface.py", line 616, in _sendThread 2023-03-22 09:34:02,674 Publish udi_interface ERROR udi_interface:write: self._mqttc.publish(topic, json.dumps(message), retain=False) 2023-03-22 09:34:02,675 Publish udi_interface ERROR udi_interface:write: File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 1257, in publish 2023-03-22 09:34:02,679 Publish udi_interface ERROR udi_interface:write: rc = self._send_publish( 2023-03-22 09:34:02,680 Publish udi_interface ERROR udi_interface:write: File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 2693, in _send_publish 2023-03-22 09:34:02,687 Publish udi_interface ERROR udi_interface:write: return self._packet_queue(PUBLISH, packet, mid, qos, info) 2023-03-22 09:34:02,687 Publish udi_interface ERROR udi_interface:write: File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 3016, in _packet_queue 2023-03-22 09:34:02,695 Publish udi_interface ERROR udi_interface:write: return self.loop_write() 2023-03-22 09:34:02,696 Publish udi_interface ERROR udi_interface:write: File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 1577, in loop_write 2023-03-22 09:34:02,701 Publish udi_interface ERROR udi_interface:write: rc = self._packet_write() 2023-03-22 09:34:02,702 Publish udi_interface ERROR udi_interface:write: File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 2464, in _packet_write 2023-03-22 09:34:02,708 Publish udi_interface ERROR udi_interface:write: write_length = self._sock_send( 2023-03-22 09:34:02,709 Publish udi_interface ERROR udi_interface:write: File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 649, in _sock_send 2023-03-22 09:34:02,712 Publish udi_interface ERROR udi_interface:write: return self._sock.send(buf) 2023-03-22 09:34:02,713 Publish udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/ssl.py", line 1174, in send 2023-03-22 09:34:02,718 Publish udi_interface ERROR udi_interface:write: return self._sslobj.write(data) 2023-03-22 09:34:02,719 Publish udi_interface ERROR udi_interface:write: OSError 2023-03-22 09:34:02,719 Publish udi_interface ERROR udi_interface:write: : 2023-03-22 09:34:02,720 Publish udi_interface ERROR udi_interface:write: [Errno 14] Bad address 2023-03-22 09:34:05,763 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2023-03-22 09:34:05,765 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:0d:b9:53:2c:34_15 - MID: 8 Result: 0 2023-03-22 09:34:05,766 MQTT udi_interface.interface ERROR interface:_startMqtt: MQTT Connection error: An exception of type RuntimeError occurred. Arguments: ('threads can only be started once',) Traceback (most recent call last): File "/var/polyglot/.local/lib/python3.9/site-packages/udi_interface/interface.py", line 530, in _startMqtt self._mqttc.loop_forever() File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 1756, in loop_forever rc = self._loop(timeout) File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 1164, in _loop rc = self.loop_read() File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 1556, in loop_read rc = self._packet_read() File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 2439, in _packet_read rc = self._packet_handle() File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 3039, in _packet_handle return self._handle_connack() File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 3138, in _handle_connack on_connect( File "/var/polyglot/.local/lib/python3.9/site-packages/udi_interface/interface.py", line 322, in _connect self._outThread.start() File "/usr/local/lib/python3.9/threading.py", line 894, in start raise RuntimeError("threads can only be started once") RuntimeError: threads can only be started once 2023-03-22 09:36:24,610 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-03-22 09:36:27,246 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.55 Starting... 2023-03-22 09:36:27,285 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.1.18 [ISY: 5.5.9, Slot: 15] 2023-03-22 09:36:27,287 MainThread udi_interface.interface INFO interface:__init__: Connect: Network Interface: {'addr': '172.16.1.210', 'netmask': '255.255.255.0', 'broadcast': '172.16.1.255'} 2023-03-22 09:36:27,289 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:1888 2023-03-22 09:36:27,292 MainThread udi_interface.interface WARNING interface:start: No node server version specified. Using deprecated server.json version 2023-03-22 09:36:27,293 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: controller not found in database. 2023-03-22 09:36:27,294 MainThread udi_interface DEBUG Controller:init_typed: enter 2023-03-22 09:36:27,295 MainThread udi_interface.custom INFO custom:_save: Sending data customtypedparams to Polyglot. 2023-03-22 09:36:27,296 MainThread udi_interface DEBUG Controller:init_typed: exit 2023-03-22 09:36:27,297 MainThread udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2023-03-22 09:36:27,298 MainThread udi_interface.interface INFO interface:addNode: Adding node Notification Controller(controller) [None] 2023-03-22 09:36:27,298 MainThread udi_interface.interface INFO interface:setController: Using node "controller", driver "ST" for connection status. 2023-03-22 09:36:27,344 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2023-03-22 09:36:27,346 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:0d:b9:53:2c:34_15 - MID: 1 Result: 0 2023-03-22 09:36:27,355 MQTT udi_interface.interface ERROR interface:_startMqtt: MQTT Connection SSLError: EOF occurred in violation of protocol (_ssl.c:2488), Will retry in a few seconds. Traceback (most recent call last): File "/var/polyglot/.local/lib/python3.9/site-packages/udi_interface/interface.py", line 530, in _startMqtt self._mqttc.loop_forever() File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 1756, in loop_forever rc = self._loop(timeout) File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 1181, in _loop rc = self.loop_write() File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 1577, in loop_write rc = self._packet_write() File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 2464, in _packet_write write_length = self._sock_send( File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 649, in _sock_send return self._sock.send(buf) File "/usr/local/lib/python3.9/ssl.py", line 1174, in send return self._sslobj.write(data) ssl.SSLEOFError: EOF occurred in violation of protocol (_ssl.c:2488) 2023-03-22 09:36:30,439 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2023-03-22 09:36:30,441 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:0d:b9:53:2c:34_15 - MID: 9 Result: 0 2023-03-22 09:36:30,442 MQTT udi_interface.interface ERROR interface:_startMqtt: MQTT Connection error: An exception of type RuntimeError occurred. Arguments: ('threads can only be started once',) Traceback (most recent call last): File "/var/polyglot/.local/lib/python3.9/site-packages/udi_interface/interface.py", line 530, in _startMqtt self._mqttc.loop_forever() File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 1756, in loop_forever rc = self._loop(timeout) File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 1164, in _loop rc = self.loop_read() File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 1556, in loop_read rc = self._packet_read() File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 2439, in _packet_read rc = self._packet_handle() File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 3039, in _packet_handle return self._handle_connack() File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 3138, in _handle_connack on_connect( File "/var/polyglot/.local/lib/python3.9/site-packages/udi_interface/interface.py", line 322, in _connect self._outThread.start() File "/usr/local/lib/python3.9/threading.py", line 894, in start raise RuntimeError("threads can only be started once") RuntimeError: threads can only be started once 2023-03-22 09:37:42,214 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-03-22 09:37:45,389 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.55 Starting... 2023-03-22 09:37:45,440 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.1.18 [ISY: 5.5.9, Slot: 15] 2023-03-22 09:37:45,443 MainThread udi_interface.interface INFO interface:__init__: Connect: Network Interface: {'addr': '172.16.1.210', 'netmask': '255.255.255.0', 'broadcast': '172.16.1.255'} 2023-03-22 09:37:45,446 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:1888 2023-03-22 09:37:45,450 MainThread udi_interface.interface WARNING interface:start: No node server version specified. Using deprecated server.json version 2023-03-22 09:37:45,451 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: controller not found in database. 2023-03-22 09:37:45,453 MainThread udi_interface DEBUG Controller:init_typed: enter 2023-03-22 09:37:45,455 MainThread udi_interface.custom INFO custom:_save: Sending data customtypedparams to Polyglot. 2023-03-22 09:37:45,456 MainThread udi_interface DEBUG Controller:init_typed: exit 2023-03-22 09:37:45,457 MainThread udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2023-03-22 09:37:45,458 MainThread udi_interface.interface INFO interface:addNode: Adding node Notification Controller(controller) [None] 2023-03-22 09:37:45,459 MainThread udi_interface.interface INFO interface:setController: Using node "controller", driver "ST" for connection status. 2023-03-22 09:37:45,525 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2023-03-22 09:37:45,527 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:0d:b9:53:2c:34_15 - MID: 1 Result: 0 2023-03-22 09:37:45,536 MQTT udi_interface.interface ERROR interface:_startMqtt: MQTT Connection SSLError: EOF occurred in violation of protocol (_ssl.c:2488), Will retry in a few seconds. Traceback (most recent call last): File "/var/polyglot/.local/lib/python3.9/site-packages/udi_interface/interface.py", line 530, in _startMqtt self._mqttc.loop_forever() File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 1756, in loop_forever rc = self._loop(timeout) File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 1181, in _loop rc = self.loop_write() File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 1577, in loop_write rc = self._packet_write() File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 2464, in _packet_write write_length = self._sock_send( File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 649, in _sock_send return self._sock.send(buf) File "/usr/local/lib/python3.9/ssl.py", line 1174, in send return self._sslobj.write(data) ssl.SSLEOFError: EOF occurred in violation of protocol (_ssl.c:2488) 2023-03-22 09:37:45,539 Publish udi_interface ERROR udi_interface:write: Exception in thread 2023-03-22 09:37:45,557 Publish udi_interface ERROR udi_interface:write: Publish 2023-03-22 09:37:45,558 Publish udi_interface ERROR udi_interface:write: : 2023-03-22 09:37:45,559 Publish udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2023-03-22 09:37:45,560 Publish udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 980, in _bootstrap_inner 2023-03-22 09:37:45,564 Publish udi_interface ERROR udi_interface:write: self.run() 2023-03-22 09:37:45,565 Publish udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 917, in run 2023-03-22 09:37:45,568 Publish udi_interface ERROR udi_interface:write: self._target(*self._args, **self._kwargs) 2023-03-22 09:37:45,569 Publish udi_interface ERROR udi_interface:write: File "/var/polyglot/.local/lib/python3.9/site-packages/udi_interface/interface.py", line 616, in _sendThread 2023-03-22 09:37:45,572 Publish udi_interface ERROR udi_interface:write: self._mqttc.publish(topic, json.dumps(message), retain=False) 2023-03-22 09:37:45,574 Publish udi_interface ERROR udi_interface:write: File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 1257, in publish 2023-03-22 09:37:45,579 Publish udi_interface ERROR udi_interface:write: rc = self._send_publish( 2023-03-22 09:37:45,580 Publish udi_interface ERROR udi_interface:write: File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 2693, in _send_publish 2023-03-22 09:37:45,588 Publish udi_interface ERROR udi_interface:write: return self._packet_queue(PUBLISH, packet, mid, qos, info) 2023-03-22 09:37:45,589 Publish udi_interface ERROR udi_interface:write: File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 3016, in _packet_queue 2023-03-22 09:37:45,597 Publish udi_interface ERROR udi_interface:write: return self.loop_write() 2023-03-22 09:37:45,598 Publish udi_interface ERROR udi_interface:write: File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 1577, in loop_write 2023-03-22 09:37:45,602 Publish udi_interface ERROR udi_interface:write: rc = self._packet_write() 2023-03-22 09:37:45,604 Publish udi_interface ERROR udi_interface:write: File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 2464, in _packet_write 2023-03-22 09:37:45,610 Publish udi_interface ERROR udi_interface:write: write_length = self._sock_send( 2023-03-22 09:37:45,612 Publish udi_interface ERROR udi_interface:write: File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 649, in _sock_send 2023-03-22 09:37:45,616 Publish udi_interface ERROR udi_interface:write: return self._sock.send(buf) 2023-03-22 09:37:45,617 Publish udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/ssl.py", line 1174, in send 2023-03-22 09:37:45,621 Publish udi_interface ERROR udi_interface:write: return self._sslobj.write(data) 2023-03-22 09:37:45,622 Publish udi_interface ERROR udi_interface:write: ssl 2023-03-22 09:37:45,623 Publish udi_interface ERROR udi_interface:write: . 2023-03-22 09:37:45,624 Publish udi_interface ERROR udi_interface:write: SSLError 2023-03-22 09:37:45,625 Publish udi_interface ERROR udi_interface:write: : 2023-03-22 09:37:45,625 Publish udi_interface ERROR udi_interface:write: [SSL: BAD_LENGTH] bad length (_ssl.c:2488) 2023-03-22 09:37:48,616 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2023-03-22 09:37:48,618 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:0d:b9:53:2c:34_15 - MID: 9 Result: 0 2023-03-22 09:37:48,619 MQTT udi_interface.interface ERROR interface:_startMqtt: MQTT Connection error: An exception of type RuntimeError occurred. Arguments: ('threads can only be started once',) Traceback (most recent call last): File "/var/polyglot/.local/lib/python3.9/site-packages/udi_interface/interface.py", line 530, in _startMqtt self._mqttc.loop_forever() File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 1756, in loop_forever rc = self._loop(timeout) File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 1164, in _loop rc = self.loop_read() File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 1556, in loop_read rc = self._packet_read() File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 2439, in _packet_read rc = self._packet_handle() File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 3039, in _packet_handle return self._handle_connack() File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 3138, in _handle_connack on_connect( File "/var/polyglot/.local/lib/python3.9/site-packages/udi_interface/interface.py", line 322, in _connect self._outThread.start() File "/usr/local/lib/python3.9/threading.py", line 894, in start raise RuntimeError("threads can only be started once") RuntimeError: threads can only be started once 2023-03-22 09:42:10,821 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-03-22 09:42:13,468 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.55 Starting... 2023-03-22 09:42:13,510 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.1.18 [ISY: 5.5.9, Slot: 15] 2023-03-22 09:42:13,512 MainThread udi_interface.interface INFO interface:__init__: Connect: Network Interface: {'addr': '172.16.1.210', 'netmask': '255.255.255.0', 'broadcast': '172.16.1.255'} 2023-03-22 09:42:13,515 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:1888 2023-03-22 09:42:13,519 MainThread udi_interface.interface WARNING interface:start: No node server version specified. Using deprecated server.json version 2023-03-22 09:42:13,521 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: controller not found in database. 2023-03-22 09:42:13,523 MainThread udi_interface DEBUG Controller:init_typed: enter 2023-03-22 09:42:13,525 MainThread udi_interface.custom INFO custom:_save: Sending data customtypedparams to Polyglot. 2023-03-22 09:42:13,526 MainThread udi_interface DEBUG Controller:init_typed: exit 2023-03-22 09:42:13,528 MainThread udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2023-03-22 09:42:13,529 MainThread udi_interface.interface INFO interface:addNode: Adding node Notification Controller(controller) [None] 2023-03-22 09:42:13,536 MainThread udi_interface.interface INFO interface:setController: Using node "controller", driver "ST" for connection status. 2023-03-22 09:42:13,598 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2023-03-22 09:42:13,599 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:0d:b9:53:2c:34_15 - MID: 1 Result: 0 2023-03-22 09:42:13,610 MQTT udi_interface.interface ERROR interface:_startMqtt: MQTT Connection SSLError: EOF occurred in violation of protocol (_ssl.c:2488), Will retry in a few seconds. Traceback (most recent call last): File "/var/polyglot/.local/lib/python3.9/site-packages/udi_interface/interface.py", line 530, in _startMqtt self._mqttc.loop_forever() File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 1756, in loop_forever rc = self._loop(timeout) File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 1181, in _loop rc = self.loop_write() File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 1577, in loop_write rc = self._packet_write() File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 2464, in _packet_write write_length = self._sock_send( File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 649, in _sock_send return self._sock.send(buf) File "/usr/local/lib/python3.9/ssl.py", line 1174, in send return self._sslobj.write(data) ssl.SSLEOFError: EOF occurred in violation of protocol (_ssl.c:2488) 2023-03-22 09:42:16,694 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2023-03-22 09:42:16,695 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:0d:b9:53:2c:34_15 - MID: 9 Result: 0 2023-03-22 09:42:16,697 MQTT udi_interface.interface ERROR interface:_startMqtt: MQTT Connection error: An exception of type RuntimeError occurred. Arguments: ('threads can only be started once',) Traceback (most recent call last): File "/var/polyglot/.local/lib/python3.9/site-packages/udi_interface/interface.py", line 530, in _startMqtt self._mqttc.loop_forever() File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 1756, in loop_forever rc = self._loop(timeout) File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 1164, in _loop rc = self.loop_read() File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 1556, in loop_read rc = self._packet_read() File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 2439, in _packet_read rc = self._packet_handle() File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 3039, in _packet_handle return self._handle_connack() File "/var/polyglot/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 3138, in _handle_connack on_connect( File "/var/polyglot/.local/lib/python3.9/site-packages/udi_interface/interface.py", line 322, in _connect self._outThread.start() File "/usr/local/lib/python3.9/threading.py", line 894, in start raise RuntimeError("threads can only be started once") RuntimeError: threads can only be started once

I had another nodeserver updated yesterday. When I updated it, I had the same issue. I had another (nonrelated) issue and had to restart pg3. They all came back with versions. @stevehoyt Did you try restarting pg3? Not update- just restart it from the menu in Pg3

I assume when a new update comes out for the ones that are not showing it, it will alert you have a new version. I also view by date and can see that way if a new version has come out most of the time

The latest version of Polisy is for EISY only so you should be at the latest I have a DEV polisy. I did not have KASA on it. I installed it. Watched it come up and SAID VERSION for about 5 seconds and then it goes away and just says production. Not sure whats going on. Strange. But I confirmed its not my polisy or pg3 for sure or an upgrade issue

I am running on Polisy and 3.1.18 is the latest for Polisy. Are you running on EISY? If so then yes there is an upgrade. I am only running ONE of your other nodeservers (WirelessTags) It shows version for me. See screenshot I also just updated one other nodeserver and it shows the latest version so its not an update issue.

thanks for your message. we will have to see what @bpwwer says about this. May be a bug or may be intentional. If intentional then how can we tell what version we have. I dont see it anywhere else?

It does not show version number. I confirmed its the correct installed. Before this it showed 3.0.18 and now no version but it is 3.0.20. I attached screenshot and log. See it just shows production and not the version number. Kasa_3-20-2023_84549-AM.zip

What does this mean for the Node Server.... Authentication update Dear Netatmo developer, As of today, when you refresh an Access Token using the associated endpoint https://api.netatmo.com/oauth2/token, Netatmo servers respond with a couple of tokens : an Access Token and a Refresh Token. If the previous Access Token is still valid, the newly returned access token is identical but its expiration time is extended for 3 hours. In any case, the refresh token is not renewed. Starting from the 17/04/2023, this behavior will change to to be compliant with the recommendations of the RFC of the OAuth2 Authorization Framework (section 10.4) and improving the security of the data of our users. When refreshing tokens, Access Token and Refresh Token will be automatically renewed and former tokens invalidated. What does it means for me ? If you were already updating the tokens provided when refreshing your tokens, this change will not impact you. If you do not update the refresh token when refreshing your Access Token, your users will be disconnected after 3 hours as the former tokens will become invalidated. To fix it, you need to update the tokens as soon as you get the newly generated ones. Sincerely, Legrand - Netatmo - Bticino

Thanks. Just curious.

in pg3 Node Server list it shows Timedata was updated last night 2/28/23 at 23:14 but when I check its the same version that i have had for a while. Is this due to just a reupload of the same version?

You might be onto something. I tried healing network and 4 devices failed after it had to retry 1/2 of them at least once. Tried again and different ones failed. Rebooted and healed fine with no retries. Tried the locks and they all worked perfectly the first time. After that the status started getting slower each time I locked and unlocked. Oh and when I rebooted I had the admin console open. The locks all showed no status. Slowly they all came in one at time within a minute (And I was not doing a query on restart) I will update my ticket with this post