macjeff

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.

Thanks!!!! Hopefully there is a fix or workaround

I was told there was another post about this but cant find it. If there is I will close this and move over. on ISY on Polisy In ISY ADMIN, I randomly got ALREADY SUBSCRIBED for a while. Since updating with the latest Polisy update those continued but now the same type of errors with UD Mobile. A reboot of the ISY always clears this or you can wait it out (hours) I put in a ticket and was told that others have found the issue was ST Inventory. They said its not gracefully disconnecting sometimes when it connects. (If you want more info see the ISSUE on GitHub - https://github.com/UniversalDevicesInc/UD-Mobile-iOS/issues/65) So I turned off ST Inventory on Friday with no issues all weekend. I just turned it back on (Monday) and within a couple minutes I get errors. I can easily reproduce (more than random) with UD Mobile on iOS. Just force quit the app and run it and you will see an error. If you repeat the steps a couple times it eventually gets in. Turn of ST Inventory and the errors go away. Errors seem to be only on local network but thats because outside the network I connect using ISY portal which maintains a connection. I did try the 1 hour short and 1 Day poll for ST Inventory but that did not help. Within a minute of turning the Node server on the errors come back. For now leaving it off as I only use that once and a while and when I do need it I can turn it on, get my data, and then turn it back off. its not used in any programs.

I had written a program to tell me when any of my units show RADON over a certain percent. Tonight it warned me. I checked the real logs at airthings and it was not even close to bad levels. I checked the ISY and all of my units had nothing in the connected (the Node server said connected but not the individual nodes for the devices). I looked at logs and showed lots of errors. Restarted and now stuff is fine but got my logs before I did. Sorry but I was only in ERROR mode. Switched to debug for future. Airthings-C_7-16-2022_110235_PM.zip

Got this from Purple Air. I guess it requires a Node server update but our keys should still work. Dear PurpleAir API Users, We are excited to let you know that we will be releasing a new version of the PurpleAir API on July 18, 2022. This new API provides access to historic data that is now hosted on Google’s BigQuery. It is important to note this update provides no functional changes to our current API at https://api.purpleair.com, but rather adds new history endpoints. What updates will the new version have? We added features that provide access to historical data. You’ll find documentation within the API site explaining how to use these new endpoints. Before the 18th, you may test them here: https://june2022.api.purpleair.com. This preview URL will go away, so please be sure only to use it until the main URL is updated. What do you need to do? If you use ThingSpeak for historic data, you will need to migrate your code to use the PurpleAir API instead. The ThingSpeak service will stop working in or around August 2022. We encourage you to get familiar with and switch to the new API’s history endpoints as soon as possible before ThingSpeak is no longer available. Rollback capability. If you experience any issues with the new version, for a limited time, the previous version of the API will be available at https://rollback.api.purpleair.com. Look out for future announcements. We are currently updating our API Terms of Service and Attribution guidelines. Please look out for an announcement in the coming weeks. Thank you, The PurpleAir Team Disclaimer You are receiving this email because you have signed up for a PurpleAir API key.

Thanks for the mention I guess. Lol. I was going for the world record but I guess that dream is gone. Lol and I only update every 2-3 days not seconds. Lol

From what I see it basically does the same thing as pushing the hidden button one time (Update Packages) but I could be wrong. I dont think he wants us to SSH anymore See the email they just sent out.

I am in the same boat. I did what I was told in the past and it came back to bite me. The rules change here daily LOL

He told me its the new Python doing it

Heard from Universal Devices when you click on button and you get one LONG beep that means nothing to be done. You can verify because when its working all three lights blink. When done only the one light is lit (facing front farthest to the left) if there are packages to be installed you will get 4 short beeps when done. I am confirming because some people reported 6 beeps total and some 5. All of them said the first one was long. But if thats the case and you always get a long beep, how do you know if its done or not? I have emailed for more confirmation, but to be safe I would listen for beeps and check the status lights

I agree. They hinted it was coming!!!

One thing is was told to leave it alone until the update finishes so its nice to know. but the main concern is why am I not getting the 4 beeps now. Just one. Hopefully it just means no update but I cant find any posts or documentation confirming that.