hart2hart

You were restoring a PLM and it appears you stopped it and are going to start over. Restoring a PLM writes all the links to the new PLM and IoP then goes through one device at a time and replaces the old PLM address with the new PLM address inside the device. If you stop it mid process and it wasn’t just a hang before it really got started, I’d think your individual devices have a mix of old and new PLM address. Peace out.

It appears from reading that some of your individual switches etc may have had the Insteon address of the 2412 PLM written to them. Others may still have Insteon address of your 2413 in them. Hence your network is an odd state. When you start over, not only does Polisy need to get in proper state but all devices will eventually need the address of the PLM that’s in place. I don’t have advice but I’d evaluate it. Maybe ask UD.

I’m guessing you are in an odd state. Some of your devices have the 2413s PLM address and some were updated to the 2412 PLM address.

You will need to find or make a cable that goes from RJ45 to DB9. The RJ45 connectors on Polisy are Ethernet not rs232.

So funny and not trying to pick a fight but I didn’t get any notice from Google and I don’t have time to read every post from here. The one you quoted looked to mention elk in title. I would clearly have invested 5 minutes if I’d known. With 2FA in my experience, if the IP address changes, they ask you to authenticate again. which might negate the special app passcode. Wouldn’t that be an issue in the longer term? Xfinity changes mine at least once or twice a year. I’ve been using Spark email client for about a year since texting changed. FWIW I am moving this to an outlook.com account. Maybe just kicking can down the road but…

If you turn on two factor authentication for the account, where on ISY does it ask for credentials? If your ISP gives you a new IP address will it require authentication again? I considering moving notifications smtp to an outlook.com account.

I stopped getting Email notifications from ISY a couple days ago after like 12 years. I searched and it appears that Google has disabled simple username and password access to smtp. All this protection is killing me. I should be able to mark the account as non critical. Damn! Can others confirm they have the issue. ? If so, what are you using for smtp now?

Thanks. It's installed.

I'm having the same problem. It did not update since first thing this morning. I restarted the node and it didn't update. I pushed Query from ISY AC and it updated all. grabbed a log after restart and the query that includes not activity since this AM. I didn't get any of my message saying it was not authenticated etc. I'll upload to github but how do i upload log so its not open in case I missed covering up some sensitive data?

I had to refresh store before it showed the .14 version.

Thanks! It felt like that was what was happening. Just wanted to update you and make sure.

Thanks installed it - I think. I refreshed store and then restarted the node server. While it is connecting it says version is 3.0.14 for a few seconds but I can see it revert to 3.0.13 on the screen. Its likely running new version but just displaying 3.0.13.

Thanks. I’ll do whichever you prefer. Upgrade for second test machine or give it more time with you.

Thanks! I’ll be looking for the release.

It happened again today. I had to stop and start mode to get values to the ISY.

It works ok for me then just stops updating ISY until I restart it. What should I be concerned about in config. As I recall, the only settings I can alter is the polling intervals. Not if front of it now. What are suggested values so I can confirm I’m in line. The others config are flume credentials which are required to work. Thanks. I understand the api is odd. Let me know if I can provide anything via logging etc.

I have programs that start a counter and end the counter of gallons used for irrigation. The problem is the Node server is not sending data to the ISY. I restart the Node server and the proper amounts show up. I've got screen shots of before and after restart and a log but know it has some sensitive information inside. Let me know how you want me to transfer data to aid in debugging. Thanks, Paul

Thanks. Obviously not even close to a priority, it just hit me while I was testing.

Thanks it works great. For use cases where only a few lights change state, would it be worth considering grabbing the current state at start of restore , comparing before and after state, and only sending REST commands where they are different? Kinda a temporary scene? Add a Restore Differential button?

Okay, Ive got backup running or at least it goes through steps. The problem is when I send a restore command there is error in the log. 2022-05-28 14:41:12,522 Command udi_interface DEBUG backup:restore: getting custom data to restore: {'address': 'controller', 'cmd': 'RESTORE', 'query': {}} 2022-05-28 14:41:12,523 Command udi_interface.interface ERROR interface:_handleInput: _parseInput: failed controller.runCmd(RESTORE) can only concatenate str (not "int") to str Traceback (most recent call last): File "/var/polyglot/.local/lib/python3.8/site-packages/udi_interface/interface.py", line 795, in _handleInput self.nodes_internal[item['address']].runCmd(item) File "/var/polyglot/.local/lib/python3.8/site-packages/udi_interface/node.py", line 165, in runCmd fun(self, command) File "/var/polyglot/pg3/ns/00:21:b9:00:f1:fd_7/nodes/backup.py", line 123, in restore cmd = '/rest/nodes/' + address + '/cmd/DON/' + self.CustomData[address]['value'] TypeError: can only concatenate str (not "int") to str 2022-05-28 14:41:13,673 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message longPoll 2022-05-28 14:41:13,675 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING longPoll 2022-05-28 14:41:13,723 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll

Never though about it but in all normal programs, I got a next command. Only for this test have I not had a next command. LOL Thanks. I'll watch the Node server log to get a good estimate of how long it takes to process so I can pick a delay.

I created a simple test program to see how Backup Node server works internally to determine if it runs in line or is launched asynchronously so the program would immediately execute the next step. I performed a Run (Then) on the program, and it only ran 1-2 seconds (was green) so the wait obviously did not occur. SecSys:DSC Alarm Test If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Set 'Backup Ligthing State / Save_Restore lighting' Backup Wait 1 minute Else - No Actions - (To add one, press 'Action') I am trying to determine if a wait is needed after the Backup and if so how long of a wait to allow before turning on the All Lights scene to avoid getting wrong light states. Backup appeared to run asynchronously (based a long or short poll showing in Node server log almost immediately followed about 11 seconds later with a storm of log events naming lots of devices with Node server logging set at debug mode short segment follows with .... used show removed information) but as a side effect it ended program execution since no Wait 1 minute occurred. If that's true and as intended, I will need backup in its own program to be run from another program that has multiple sequential steps and with a wait after it is called to allow it time to complete. Please help me understand the timing and program execution requirements so I don't make wrong assumptions. The Node server says no configuration is needed and I assume that means it knows the ISY that it is running on. How about the long and shortpoll? Do they have a function and if so what? 2022-05-28 10:08:28,756 Command udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'key': 'customdata', 'value': {'xx xx xx x': {'name': 'Back Porch:Floods', 'value': 0}, .... }}}]} 2022-05-28 10:08:28,761 Command udi_interface DEBUG backup:query: Found node Yard:Bird Bath Bottom - Heate with type 2.57.68.0 category 2 and status 0 2022-05-28 10:08:28,762 Command udi_interface.custom DEBUG custom:__setitem__: CUSTOM: xx xx xx x = {'name': 'Yard:Bird Bath Bottom - Heate', 'value': 0} ... saving 2022-05-28 10:08:28,763 Command udi_interface.custom INFO custom:_save: Sending data customdata to Polyglot. ... 2022-05-28 10:08:28,786 Command udi_interface INFO backup:query: Query processed 169 devices. 2022-05-28 10:08:28,787 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING customdata 2022-05-28 10:08:28,790 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING customdata 2022-05-28 10:08:28,793 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING customdata 2022-05-28 10:08:28,973 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message customdata 2022-05-28 10:08:28,975 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING customdata 2022-05-28 10:08:29,012 MQTT udi_interface.interface INFO interface:_message: Successfully set key = customdata 2022-05-28 10:08:29,126 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message customdata 2022-05-28 10:08:29,127 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING customdata 2022-05-28 10:08:29,164 MQTT udi_interface.interface INFO interface:_message: Successfully set key = customdata 2022-05-28 10:08:29,376 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message customdata ... Thanks

On my pg3 dashboard, it said pg3 needs to be restarted after the iop upgrade.

Thanks. Just making sure it wasn’t something with my specific install. Already felt better that another person had seen the issue and it’s been running fantastic for several days.

I’ve Never updated browser. It was a Java setting.