macjeff

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.

For those of you reporting the issue with update problems, somehow after running previous updates through the update packages button it was pointing to the wrong location for some of the updates. It’s not some thing I did but they fixed it. I’m wondering if this could be the same issue some others are having and UD have to get in and fix where are the updates or grabbed from I’m sure some update I ran in the past mess something up. Personally I’m going to wait to do the update until Sunday so that if anything goes wrong I can get in touch with tech-support on Monday.

I totally missed this reply. I have total connect, envisilink, and a vista 128p. I am having an issue with the board sending me messages via total connect and the touchscreen that there is a power outage but there is not. I put a voltage tester on the board and one on the power supply and when it says it loses power its perfect. Even the technician sees the same thing. So I just got a new 128bpt board in and they are replacing (we already tried a new power supply). Not sure if thats throwing anything off but I did call EyeZon and they said the envisilink is NOT showing any downtime so it does not see the issue that honeywell is reporting

I set to debug. I will let it run a little and then send you the log

I am seeing unhandled command in the log..... 2022-10-03 21:31:12,112 MQTT udi_interface.interface INFO interface:_message: Successfully set zone24 :: GV1 to 17715 UOM 58 2022-10-03 21:34:30,788 Thread-101 udi_interface INFO classes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D5 2022-10-03 21:35:55,889 Thread-101 udi_interface INFO classes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D5 2022-10-03 21:36:11,000 MQTT udi_interface.interface INFO interface:_message: Successfully set zone02 :: GV1 to 103790 UOM 58 2022-10-03 21:36:11,184 MQTT udi_interface.interface INFO interface:_message: Successfully set zone03 :: GV1 to 15 UOM 58 2022-10-03 21:36:11,224 MQTT udi_interface.interface INFO interface:_message: Successfully set zone04 :: GV1 to 16960 UOM 58 2022-10-03 21:36:11,358 MQTT udi_interface.interface INFO interface:_message: Successfully set zone05 :: GV1 to 4010 UOM 58 2022-10-03 21:36:11,460 MQTT udi_interface.interface INFO interface:_message: Successfully set zone06 :: GV1 to 8465 UOM 58 2022-10-03 21:36:11,563 MQTT udi_interface.interface INFO interface:_message: Successfully set zone07 :: GV1 to 2525 UOM 58 2022-10-03 21:36:11,663 MQTT udi_interface.interface INFO interface:_message: Successfully set zone08 :: GV1 to 93805 UOM 58 2022-10-03 21:36:11,760 MQTT udi_interface.interface INFO interface:_message: Successfully set zone09 :: GV1 to 27255 UOM 58 2022-10-03 21:36:11,855 MQTT udi_interface.interface INFO interface:_message: Successfully set zone12 :: GV1 to 97690 UOM 58 2022-10-03 21:36:11,957 MQTT udi_interface.interface INFO interface:_message: Successfully set zone14 :: GV1 to 4095 UOM 58 2022-10-03 21:36:12,062 MQTT udi_interface.interface INFO interface:_message: Successfully set zone18 :: GV1 to 38620 UOM 58 2022-10-03 21:36:12,162 MQTT udi_interface.interface INFO interface:_message: Successfully set zone21 :: GV1 to 99860 UOM 58 2022-10-03 21:36:12,260 MQTT udi_interface.interface INFO interface:_message: Successfully set zone24 :: GV1 to 18015 UOM 58 2022-10-03 21:40:20,149 Thread-101 udi_interface INFO classes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D9 2022-10-03 21:41:10,980 MQTT udi_interface.interface INFO interface:_message: Successfully set zone02 :: GV1 to 104090 UOM 58 2022-10-03 21:41:11,122 MQTT udi_interface.interface INFO interface:_message: Successfully set zone03 :: GV1 to 5 UOM 58 2022-10-03 21:41:11,205 MQTT udi_interface.interface INFO interface:_message: Successfully set zone04 :: GV1 to 17260 UOM 58 2022-10-03 21:41:11,296 MQTT udi_interface.interface INFO interface:_message: Successfully set zone05 :: GV1 to 4310 UOM 58 2022-10-03 21:41:11,398 MQTT udi_interface.interface INFO interface:_message: Successfully set zone06 :: GV1 to 8765 UOM 58 2022-10-03 21:41:11,500 MQTT udi_interface.interface INFO interface:_message: Successfully set zone07 :: GV1 to 2825 UOM 58 2022-10-03 21:41:11,594 MQTT udi_interface.interface INFO interface:_message: Successfully set zone08 :: GV1 to 94105 UOM 58 2022-10-03 21:41:11,699 MQTT udi_interface.interface INFO interface:_message: Successfully set zone09 :: GV1 to 27555 UOM 58 2022-10-03 21:41:11,801 MQTT udi_interface.interface INFO interface:_message: Successfully set zone12 :: GV1 to 97990 UOM 58 2022-10-03 21:41:11,898 MQTT udi_interface.interface INFO interface:_message: Successfully set zone14 :: GV1 to 4395 UOM 58 2022-10-03 21:41:11,998 MQTT udi_interface.interface INFO interface:_message: Successfully set zone18 :: GV1 to 38920 UOM 58 2022-10-03 21:41:12,100 MQTT udi_interface.interface INFO interface:_message: Successfully set zone21 :: GV1 to 100160 UOM 58 2022-10-03 21:41:12,196 MQTT udi_interface.interface INFO interface:_message: Successfully set zone24 :: GV1 to 18315 UOM 58 2022-10-03 21:46:11,007 MQTT udi_interface.interface INFO interface:_message: Successfully set zone02 :: GV1 to 104390 UOM 58 2022-10-03 21:46:11,351 MQTT udi_interface.interface INFO interface:_message: Successfully set zone03 :: GV1 to 10 UOM 58 2022-10-03 21:46:11,465 MQTT udi_interface.interface INFO interface:_message: Successfully set zone04 :: GV1 to 17560 UOM 58 2022-10-03 21:46:11,508 MQTT udi_interface.interface INFO interface:_message: Successfully set zone05 :: GV1 to 4610 UOM 58 2022-10-03 21:46:11,548 MQTT udi_interface.interface INFO interface:_message: Successfully set zone06 :: GV1 to 9065 UOM 58 2022-10-03 21:46:11,550 MQTT udi_interface.interface INFO interface:_message: Successfully set zone07 :: GV1 to 3125 UOM 58 2022-10-03 21:46:11,638 MQTT udi_interface.interface INFO interface:_message: Successfully set zone08 :: GV1 to 94405 UOM 58 2022-10-03 21:46:11,739 MQTT udi_interface.interface INFO interface:_message: Successfully set zone09 :: GV1 to 27855 UOM 58 2022-10-03 21:46:11,839 MQTT udi_interface.interface INFO interface:_message: Successfully set zone12 :: GV1 to 98290 UOM 58 2022-10-03 21:46:11,942 MQTT udi_interface.interface INFO interface:_message: Successfully set zone14 :: GV1 to 4695 UOM 58 2022-10-03 21:46:12,037 MQTT udi_interface.interface INFO interface:_message: Successfully set zone18 :: GV1 to 39220 UOM 58 2022-10-03 21:46:12,138 MQTT udi_interface.interface INFO interface:_message: Successfully set zone21 :: GV1 to 100460 UOM 58 2022-10-03 21:46:12,240 MQTT udi_interface.interface INFO interface:_message: Successfully set zone24 :: GV1 to 18615 UOM 58 2022-10-03 21:49:26,371 Thread-101 udi_interface INFO classes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D5 2022-10-03 21:51:10,919 MQTT udi_interface.interface INFO interface:_message: Successfully set zone02 :: GV1 to 104690 UOM 58 2022-10-03 21:51:11,049 MQTT udi_interface.interface INFO interface:_message: Successfully set zone03 :: GV1 to 15 UOM 58 2022-10-03 21:51:11,148 MQTT udi_interface.interface INFO interface:_message: Successfully set zone04 :: GV1 to 17860 UOM 58 2022-10-03 21:51:11,233 MQTT udi_interface.interface INFO interface:_message: Successfully set zone05 :: GV1 to 4910 UOM 58 2022-10-03 21:51:11,316 MQTT udi_interface.interface INFO interface:_message: Successfully set zone06 :: GV1 to 9365 UOM 58 2022-10-03 21:51:11,489 MQTT udi_interface.interface INFO interface:_message: Successfully set zone07 :: GV1 to 3425 UOM 58 2022-10-03 21:51:11,531 MQTT udi_interface.interface INFO interface:_message: Successfully set zone08 :: GV1 to 94705 UOM 58 2022-10-03 21:51:11,632 MQTT udi_interface.interface INFO interface:_message: Successfully set zone09 :: GV1 to 28155 UOM 58 2022-10-03 21:51:11,734 MQTT udi_interface.interface INFO interface:_message: Successfully set zone12 :: GV1 to 98590 UOM 58 2022-10-03 21:51:11,834 MQTT udi_interface.interface INFO interface:_message: Successfully set zone14 :: GV1 to 4995 UOM 58 2022-10-03 21:51:11,937 MQTT udi_interface.interface INFO interface:_message: Successfully set zone18 :: GV1 to 39520 UOM 58 2022-10-03 21:51:12,036 MQTT udi_interface.interface INFO interface:_message: Successfully set zone21 :: GV1 to 100760 UOM 58 2022-10-03 21:51:12,134 MQTT udi_interface.interface INFO interface:_message: Successfully set zone24 :: GV1 to 18915 UOM 58 2022-10-03 21:56:10,936 MQTT udi_interface.interface INFO interface:_message: Successfully set zone02 :: GV1 to 104990 UOM 58 2022-10-03 21:56:11,056 MQTT udi_interface.interface INFO interface:_message: Successfully set zone03 :: GV1 to 20 UOM 58 2022-10-03 21:56:11,150 MQTT udi_interface.interface INFO interface:_message: Successfully set zone04 :: GV1 to 18160 UOM 58 2022-10-03 21:56:11,251 MQTT udi_interface.interface INFO interface:_message: Successfully set zone05 :: GV1 to 5210 UOM 58 2022-10-03 21:56:11,334 MQTT udi_interface.interface INFO interface:_message: Successfully set zone06 :: GV1 to 9665 UOM 58 2022-10-03 21:56:11,448 MQTT udi_interface.interface INFO interface:_message: Successfully set zone07 :: GV1 to 3725 UOM 58 2022-10-03 21:56:11,550 MQTT udi_interface.interface INFO interface:_message: Successfully set zone08 :: GV1 to 95005 UOM 58 2022-10-03 21:56:11,647 MQTT udi_interface.interface INFO interface:_message: Successfully set zone09 :: GV1 to 28455 UOM 58 2022-10-03 21:56:11,748 MQTT udi_interface.interface INFO interface:_message: Successfully set zone12 :: GV1 to 98890 UOM 58 2022-10-03 21:56:12,010 MQTT udi_interface.interface INFO interface:_message: Successfully set zone18 :: GV1 to 39820 UOM 58 2022-10-03 21:56:12,053 MQTT udi_interface.interface INFO interface:_message: Successfully set zone14 :: GV1 to 5295 UOM 58 2022-10-03 21:56:12,055 MQTT udi_interface.interface INFO interface:_message: Successfully set zone21 :: GV1 to 101060 UOM 58 2022-10-03 21:56:12,150 MQTT udi_interface.interface INFO interface:_message: Successfully set zone24 :: GV1 to 19215 UOM 58 2022-10-03 22:01:10,944 MQTT udi_interface.interface INFO interface:_message: Successfully set zone02 :: GV1 to 105290 UOM 58 2022-10-03 22:01:11,054 MQTT udi_interface.interface INFO interface:_message: Successfully set zone03 :: GV1 to 10 UOM 58 2022-10-03 22:01:11,160 MQTT udi_interface.interface INFO interface:_message: Successfully set zone04 :: GV1 to 18460 UOM 58 2022-10-03 22:01:11,248 MQTT udi_interface.interface INFO interface:_message: Successfully set zone05 :: GV1 to 5510 UOM 58 2022-10-03 22:01:11,350 MQTT udi_interface.interface INFO interface:_message: Successfully set zone06 :: GV1 to 9965 UOM 58 2022-10-03 22:01:11,450 MQTT udi_interface.interface INFO interface:_message: Successfully set zone07 :: GV1 to 4025 UOM 58 2022-10-03 22:01:11,550 MQTT udi_interface.interface INFO interface:_message: Successfully set zone08 :: GV1 to 95305 UOM 58 2022-10-03 22:01:11,655 MQTT udi_interface.interface INFO interface:_message: Successfully set zone09 :: GV1 to 28755 UOM 58 2022-10-03 22:01:11,747 MQTT udi_interface.interface INFO interface:_message: Successfully set zone12 :: GV1 to 99190 UOM 58 2022-10-03 22:01:11,847 MQTT udi_interface.interface INFO interface:_message: Successfully set zone14 :: GV1 to 5595 UOM 58 2022-10-03 22:01:11,947 MQTT udi_interface.interface INFO interface:_message: Successfully set zone18 :: GV1 to 40120 UOM 58 2022-10-03 22:01:12,052 MQTT udi_interface.interface INFO interface:_message: Successfully set zone21 :: GV1 to 101360 UOM 58 2022-10-03 22:01:12,151 MQTT udi_interface.interface INFO interface:_message: Successfully set zone24 :: GV1 to 19515 UOM 58 2022-10-03 22:01:44,683 Thread-101 udi_interface INFO classes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D9 2022-10-03 22:05:52,439 Thread-101 udi_interface INFO classes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D9 2022-10-03 22:06:10,935 MQTT udi_interface.interface INFO interface:_message: Successfully set zone02 :: GV1 to 105590 UOM 58 2022-10-03 22:06:11,106 MQTT udi_interface.interface INFO interface:_message: Successfully set zone04 :: GV1 to 18760 UOM 58 2022-10-03 22:06:11,148 MQTT udi_interface.interface INFO interface:_message: Successfully set zone05 :: GV1 to 5810 UOM 58 2022-10-03 22:06:11,287 MQTT udi_interface.interface INFO interface:_message: Successfully set zone06 :: GV1 to 10265 UOM 58 2022-10-03 22:06:11,369 MQTT udi_interface.interface INFO interface:_message: Successfully set zone07 :: GV1 to 4325 UOM 58 2022-10-03 22:06:11,486 MQTT udi_interface.interface INFO interface:_message: Successfully set zone08 :: GV1 to 95605 UOM 58 2022-10-03 22:06:11,588 MQTT udi_interface.interface INFO interface:_message: Successfully set zone09 :: GV1 to 29055 UOM 58 2022-10-03 22:06:11,686 MQTT udi_interface.interface INFO interface:_message: Successfully set zone12 :: GV1 to 99490 UOM 58 2022-10-03 22:06:11,783 MQTT udi_interface.interface INFO interface:_message: Successfully set zone14 :: GV1 to 5895 UOM 58 2022-10-03 22:06:11,883 MQTT udi_interface.interface INFO interface:_message: Successfully set zone18 :: GV1 to 40420 UOM 58 2022-10-03 22:06:11,986 MQTT udi_interface.interface INFO interface:_message: Successfully set zone21 :: GV1 to 101660 UOM 58 2022-10-03 22:06:12,089 MQTT udi_interface.interface INFO interface:_message: Successfully set zone24 :: GV1 to 19815 UOM 58 2022-10-03 22:10:34,574 Thread-101 udi_interface INFO classes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D9 2022-10-03 22:11:10,938 MQTT udi_interface.interface INFO interface:_message: Successfully set zone02 :: GV1 to 105890 UOM 58 2022-10-03 22:11:11,118 MQTT udi_interface.interface INFO interface:_message: Successfully set zone03 :: GV1 to 15 UOM 58 2022-10-03 22:11:11,201 MQTT udi_interface.interface INFO interface:_message: Successfully set zone04 :: GV1 to 19060 UOM 58 2022-10-03 22:11:11,295 MQTT udi_interface.interface INFO interface:_message: Successfully set zone05 :: GV1 to 6110 UOM 58 2022-10-03 22:11:11,401 MQTT udi_interface.interface INFO interface:_message: Successfully set zone06 :: GV1 to 10565 UOM 58 2022-10-03 22:11:11,496 MQTT udi_interface.interface INFO interface:_message: Successfully set zone07 :: GV1 to 4625 UOM 58 2022-10-03 22:11:11,595 MQTT udi_interface.interface INFO interface:_message: Successfully set zone08 :: GV1 to 95905 UOM 58 2022-10-03 22:11:11,697 MQTT udi_interface.interface INFO interface:_message: Successfully set zone09 :: GV1 to 29355 UOM 58 2022-10-03 22:11:11,799 MQTT udi_interface.interface INFO interface:_message: Successfully set zone12 :: GV1 to 99790 UOM 58 2022-10-03 22:11:11,895 MQTT udi_interface.interface INFO interface:_message: Successfully set zone14 :: GV1 to 6195 UOM 58 2022-10-03 22:11:12,004 MQTT udi_interface.interface INFO interface:_message: Successfully set zone18 :: GV1 to 40720 UOM 58 2022-10-03 22:11:12,097 MQTT udi_interface.interface INFO interface:_message: Successfully set zone21 :: GV1 to 101960 UOM 58 2022-10-03 22:11:12,195 MQTT udi_interface.interface INFO interface:_message: Successfully set zone24 :: GV1 to 20115 UOM 58 2022-10-03 22:12:35,954 Thread-101 udi_interface INFO classes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D9 2022-10-03 22:12:36,509 Thread-101 udi_interface INFO classes:process_command: Unhandled command received from EnvisaLink. Command: A0, Data: F700D5 2022-10-03 22:12:44,225 MQTT udi_interface.interface INFO interface:_message: Successfully set zone07 :: ST to 1 UOM 25

Airthings keeps going down. It says too many requests. See log. I am still having issues with ISY rebooting and Michel said its a Node server flooding it with info. Maybe its this one but it seems to be dead. Will work after restart for a while. I dont see anything strange in level 3 device communications except my alarm system throwing errors (bad board and have to get a new one) so I disabled that. But take a look at Airthings please and let me know Airthings-C_10-1-2022_112858_AM.zip

ran the latest update and immediately got this error back again. It seems to be when I update from test flight manually. Usually I have auto updates.

Look up 20158 There are 3 within 10 miles of each other. All three are pretty close right now in low 30's. So I guess I dont understand what the 2.5 is as the same 3 in purple are show 1-3 not in the 30's. Thats what I dont understand. They may not match but thats 10+ times difference.

Then there must be different measurements because the site shows 31 now (Was 32) and that matches what weather apps say. So I am confused.

This question will show my lack of understanding of Air Quality. I was asked for the local AQI for my house. I went to https://www.airnow.gov/?city=Hamilton&state=VA&country=USA and got 32 as my AQI. They said should be 0-50 which is good Where in purple air is this? see screenshot

yes I was unable to stop it or restart it. Restarting PG3 has fixed it.

Setup- Running PG3 ping and IOP. Polisy is on a UPS. We have had both power outages and network outages but known network outage on Friday for about an hour Now nothing was updating. I have TWO logs. One before and one after restarting ping but I got the same thing. So I restarted pg3. after reboot everything was fine. So the issue may be with Pg3 but since pretty sure Bob did both the ping pg3 update and pg3 itself I am posting here. Feel free to move the post.Ping_8-28-2022_93603_AM.zipPing_8-28-2022_93603_AM.zip Ping_8-28-2022_94645_AM.zip I am getting errors uploading logs. will also send to you in PM Jeff

Fix confirmed!!! THANKS!!

I attached the last few min of the log where I am trying to get Node server updates done. I did not do anything yet other than log into pg3 and I got red message could not load node servers. I tried re-logging into portal no luck Tried another browser- no luck Rebooted PG3- same issue but they all do seem to be connected and working. And one even updated that needed an update after the reboot pg3-current.log

I am 100% sure its ST Inventory. Turned it off since yesterday and not one issue. Turned it back on just now and errors came back.