macjeff

All I know is that I switch the trigger of the routines to virtual buttons from ISY variables and they worked perfectly when the ISY variables were not triggering.

Open your old file in a text editor. The addresses are in there. Most end with /desc

I did notice it said DISCONNECTED for a while also with a red banner. All I did is refresh the page and then it said connected. I also see this if I try to restart a couple node servers in a row it gets confused. I will hit restart on one. go back to dashboard, go to another and sometimes it still says name of previous Node server. Again refresh the browser works. I know its not your issue here but it slows me down having to refresh all the time.

If you need any help with it let me know. I have 99 buttons installed and using over 70 of them!!! Install Node server Put in your access code (see Node server to get one) Name your buttons Then in Alexa create a routine (or if existing routing there is a change trigger option under the ... menu in each routine) Then in the ISY go to that button and click the PUSH BUTTON button. The routine will trigger. Even when Alexa was down it worked perfectly.

maybe they need to move off those buggy Amazon Web Servers LOL Just kidding. I saw app update for iOS today also. But yes I have seen intermittent issues. I gave in and used a Pg3 Node server called Virtual Buttons to trigger alexa rather than use variables as motion or contact sensors. It continues to work flawlessly. I also setup a program that updates a variable every hour and that variable should trigger alexa to say TEST SUCCESSFUL and send me a notice (of course not overnight LOL). It missed a few so they are having issues. But virtual buttons works every time.

check your ISY. Mine restarted after running it and I did not realize it. Make sure you can get in with admin console. I think the restart was from all the other package updates But also try reloading the page as sometimes the cache messes things up. If its still not working then wait for @bpwwerto respond. I would personally try a reboot of the entire polisy. One more thing. Did you wait when updating for the 4 or 5 beeps. It took a while for mine to update. Just some thoughts.

@bpwwer was correct when he said if you lose your connections you can see them in the old save file. Copy and paste them into the ISY FINDER and when all are back do a NEW SAVE and then you will have them saved and then they should work if you need to import. @Geddy is most likely correct that this was intentional but we discovered it before any announcement. It is a new JAVA app and does not like the old saved configs so something changed. Once you have the new version everything works as expected. Only issue is if you had a link to the JAVA app (stored in JAVA bundles kind of hidden) then your link wont work. But I am running it now along with the new 3.1.14 pg3. Only issue I saw is for some ODD reason after installing Pg3 my single Node server left in PG2 was not responding. I just restarted that Node server and all is fine. I am waiting for @simplextechto update it. Fingers crossed!!!!

Thanks. I will look at the file. That saves me time!!!

If you don’t mind trying something. If you happen to have an old set of saved locations when you use the save command in the admin sonsole launcher, try to load them back in and it’s not working. I will have to look up what they all were. If they are all the same location as you may have to delete one before you love them.

Something changed today.

I used the start app which redownloads the latest launcher.

I noticed the same thing. So I reinstalled the app and it still Ioxlquncher. it also lost all my saved IP addresses which included the portal and external IP I had to save them using the safe command in the old launcher but they won’t load in the new one so it must be a totally different app jeff

Will it hurt anything that we did the update packages when it was not ready. I assume it just did not even see the update so it just did the other FreeBSD stuff. But let me know if I need to do anything special once you get it fixed. thanks!!!

Ok well let me know when to try again. thanks

tried again. Still on 3.1.13. And I am using the Upgrade Packages button inside admin console. It worked for 3.1.12 and 3.1.13 but cant get to 3.1.14

Same here. Even restarted PG3 after and still says 3.1.13 and the reboot ISY is still there.

I can confirm this is fixed now. Thanks to all those who called Amazon like I didn’t put in trouble tickets to get them moving on this

just to be perfectly clear the problem is not about controlling devices. That works fine. The problem is when you have a variable set as a motion sensor or probably a motion sensor in general. It reports correct status to Alexa so it’s not a skill issue but the routine is never triggered from the skill. I spent almost 2 hours on the phone with Amazon screen sharing with me and they can’t figure out what’s going on so at least they issued a ticket to engineering. I just wanted to see if other people have the issue and it looks like there are some that do and some of the posts hear that say they don’t have any issues are talking about device controls not variable set as motion sensors.

Amazon says no other reports. Last time (About a year ago) I had the same issue and took a while for them to agree that there was an issue. It finally just started working.

This has happened before and Amazon fixed it internally. I did report issue to them. Here are the facts.... They worked 24 hours ago and nothing changed on my end When motion is triggered on my end the ISY does report to Alexa and the device in the alexa shows the status. Asking alexa to turn things on and off work fine. The issue is ROUTINES are not triggering. I created a new one. Variable shows motion then say this. Variable in alexa shows motion but routine does nothing I have a lot of these routines based on Variables set as motion sensors and none of them are triggering. Workaround is a Node server called Virtual Buttons. It works fine. For a test I did reboot ISY on Polisy but no luck. I disabled and re-enabled the skill- no luck Added a new device along with new skill-no luck If anyone else has this issue it would be great. THANKS!!

so this is normal behavior and no way to fix it? I guess I can deal with it. I dont reboot PG3 much.

It is now. Just when it restarts it gives the error reading the JSON file. Then the log stops even in debug. About 5 min later (and my polls are 300 and 600 so maybe that has something to do with it), the log starts back up and at that point it works. So I guess I just have to be patient but was concerned about the error

update- about 15 min later the log started again. I have no other devices connecting to it. Not sure what happened. Maybe its a limit on how often it checks?

Was running 3.1.12 30 min ago and about an hour ago I had an alarm and it shows up in logs. I updated PG3 and rebooted it and all node servers working but this one. It says connected (And I have restarted it) but this is all I get in the log (xxxx for passwords but they are correct and I did not change them) and then the log stops and nothing else happens. in ISY it says Unknown/Not in User for my partition 2022-11-03 13:58:59,302 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2022-11-03 13:59:01,932 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.49 Starting... 2022-11-03 13:59:01,941 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.1.13 [ISY: 5.4.4, Slot: 2] 2022-11-03 13:59:01,943 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'} 2022-11-03 13:59:01,944 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:1888 2022-11-03 13:59:01,947 MainThread udi_interface.interface WARNING interface:_get_server_data: get_server_data: failed to read file server.json: [Errno 2] No such file or directory: 'server.json' Traceback (most recent call last): File "/var/polyglot/.local/lib/python3.9/site-packages/udi_interface/interface.py", line 537, in _get_server_data with open(Interface.SERVER_JSON_FILE_NAME) as data: FileNotFoundError: [Errno 2] No such file or directory: 'server.json' 2022-11-03 13:59:01,952 MainThread udi_interface INFO evlvistans:<module>: Starting EnvisaLink-HW node server... 2022-11-03 13:59:01,954 MainThread udi_interface.interface WARNING interface:send: MQTT Send waiting on connection :: {'config': {'version': '3.0.3'}} 2022-11-03 13:59:02,001 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2022-11-03 13:59:02,002 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:0d:b9:53:2c:34_2 - MID: 1 Result: 0 2022-11-03 13:59:02,013 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 1 - QoS: (0,) 2022-11-03 13:59:05,146 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message getAll 2022-11-03 13:59:05,148 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING getAll 2022-11-03 13:59:05,150 Thread-2 udi_interface.custom DEBUG custom:load: CUSTOM: load {'hostname': '172.16.1.211', 'password': 'xxxxx', 'usercode': 'xxxx', 'numzones': '43', 'smartzonetracking': '1'} 2022-11-03 13:59:05,151 Command udi_interface.custom DEBUG custom:load: CUSTOM: load {} 2022-11-03 13:59:05,152 Thread-2 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking hostname / 172.16.1.211 2022-11-03 13:59:05,154 Command udi_interface.interface DEBUG interface:_handleInput: Key nsdata should be passed to node server. 2022-11-03 13:59:05,155 Thread-2 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking password / user 2022-11-03 13:59:05,158 Command udi_interface.interface DEBUG interface:_handleInput: Key oauth should be passed to node server. 2022-11-03 13:59:05,159 Thread-2 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking usercode / 1226 2022-11-03 13:59:05,165 Thread-2 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking numzones / 43 2022-11-03 13:59:05,165 Thread-2 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking smartzonetracking / 1 2022-11-03 13:59:05,185 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message getNsInfo 2022-11-03 13:59:05,187 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING getNsInfo 2022-11-03 13:59:05,206 MainThread udi_interface.interface DEBUG interface:setCustomParamsDoc: Sending customparamsdoc to Polyglot. 2022-11-03 13:59:05,207 MainThread udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'key': 'customparamsdoc', 'value': '<h2>EnvisaLink Vista Node server Configuration</h2>\n\n<h3>Advanced Configuration:</h3>\n\n<ul>\n<li>key: shortPoll, value: polling interval for connection status of Envisalink and zone timers (defaults to 30 seconds)</li>\n<li>key: longPoll, value: interval for watchdog timer resets if watchdog timer is disabled (see below, defaults to 600 seconds)</li>\n</ul>\n\n<p>NOTE: The alarm panel reports zone and partition status changes immediately and other state changes are reported in keypad updates every 4 or 5 seconds, so frequent polling for state in shortpoll is not required. longpoll needs to be less than 20 minutes to prevent EnvisaLink from rebooting.</p>\n\n<h3>Custom Configuration Parameters:</h3>\n\n<h4>Required:</h4>\n\n<ul>\n<li>key: hostname, value: locally accessible hostname or IP address of EnvisaLink or DUO device (e.g., "envisalink.local" or "192.168.1.145")</li>\n<li>key: password, value: password for EnvisaLink device</li>\n<li>key: usercode, value: user code for disarming alarm panel (e.g., "5555")</li>\n</ul>\n\n<h4>Optional:</h4>\n\n<ul>\n<li>key: numpartitions, value: number of partition nodes to generate (defaults to 1)</li>\n<li>key: numzones, value: number of zone nodes to generate (defaults to 8)</li>\n<li>key: disablewatchdog, value: 0 or 1 for whether EyezOn cloud service watchdog timer should be disabled (defaults to 0 - not disabled)</li>\n<li>key: zonetimerdumpflag, value: numeric flag indicating whether dumping of the zone timers should be done on shortpoll (1), longpoll (2), or disabled altogether (0) (defaults to 1 - shortpoll)</li>\n<li>key: smartzonetracking, value: 0 or 1 for whether Node server should use a heuristic to track zone status (open, closed) or just rely on EnvisaLink\'s zone status reporting (defaults to 0 - do not track)</li>\n</ul>\n\n<p>NOTE: On Node server start, the child nodes for the Alarm Panel are created based on the numbers configured. The disablewatchdog should be enabled if the EnvisaLink is firewalled to prevent the EnvsiaLink from rebooting after 20 minutes.</p>\n'}]} 2022-11-03 13:59:05,209 MainThread udi_interface.interface INFO interface:updateProfile: Sending Install Profile command to Polyglot. 2022-11-03 13:59:05,210 MainThread udi_interface.interface DEBUG interface:send: PUBLISHING {'installprofile': {'reboot': False}} 2022-11-03 13:59:05,251 MQTT udi_interface.interface INFO interface:_message: custom data response {'customparamsdoc': '<h2>EnvisaLink Vista Node server Configuration</h2>\n\n<h3>Advanced Configuration:</h3>\n\n<ul>\n<li>key: shortPoll, value: polling interval for connection status of Envisalink and zone timers (defaults to 30 seconds)</li>\n<li>key: longPoll, value: interval for watchdog timer resets if watchdog timer is disabled (see below, defaults to 600 seconds)</li>\n</ul>\n\n<p>NOTE: The alarm panel reports zone and partition status changes immediately and other state changes are reported in keypad updates every 4 or 5 seconds, so frequent polling for state in shortpoll is not required. longpoll needs to be less than 20 minutes to prevent EnvisaLink from rebooting.</p>\n\n<h3>Custom Configuration Parameters:</h3>\n\n<h4>Required:</h4>\n\n<ul>\n<li>key: hostname, value: locally accessible hostname or IP address of EnvisaLink or DUO device (e.g., "envisalink.local" or "192.168.1.145")</li>\n<li>key: password, value: password for EnvisaLink device</li>\n<li>key: usercode, value: user code for disarming alarm panel (e.g., "5555")</li>\n</ul>\n\n<h4>Optional:</h4>\n\n<ul>\n<li>key: numpartitions, value: number of partition nodes to generate (defaults to 1)</li>\n<li>key: numzones, value: number of zone nodes to generate (defaults to 8)</li>\n<li>key: disablewatchdog, value: 0 or 1 for whether EyezOn cloud service watchdog timer should be disabled (defaults to 0 - not disabled)</li>\n<li>key: zonetimerdumpflag, value: numeric flag indicating whether dumping of the zone timers should be done on shortpoll (1), longpoll (2), or disabled altogether (0) (defaults to 1 - shortpoll)</li>\n<li>key: smartzonetracking, value: 0 or 1 for whether Node server should use a heuristic to track zone status (open, closed) or just rely on EnvisaLink\'s zone status reporting (defaults to 0 - do not track)</li>\n</ul>\n\n<p>NOTE: On Node server start, the child nodes for the Alarm Panel are created based on the numbers configured. The disablewatchdog should be enabled if the EnvisaLink is firewalled to prevent the EnvsiaLink from rebooting after 20 minutes.</p>\n'} 2022-11-03 13:59:05,271 Thread-7 udi_interface DEBUG classes:start: In start()... 2022-11-03 13:59:05,293 MQTT udi_interface.interface INFO interface:_message: Successfully set key = customparamsdoc 2022-11-03 13:59:05,706 MQTT udi_interface.interface INFO interface:_message: Profile installation finished

Mine had same issue. A reboot fixed it for me but about a year ago mine died and i had to get a new one. UDI is about to release their own daughter Z-Wave/Zigsbee board. I would get that.