macjeff

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.

actually your correct. Yesterday it was one long beep and then 4 beeps about 30 seconds or so later. Today its just one long beep. Did you try it a second time? I still think that means no updates. 4 beeps it says means update complete.

Thanks @Bumbershoot I am going to be in meetings a lot today so I appreciate you clearing up any confusion. I hope Michel can chime in and let us know what the beeps are. I also send them an email and if they reply there I will repost the answer here later. Its just good to know what the beeps mean so you know if there is a problem or not. I also asked for a way to let Admin console know. Its hard to hear the beep from my office!!!

Inside the ADMIN CONSOLE in 5.4.4 or later there is a button called UPGRADE PACKAGES. I ran it yesterday after Michel said DONT USE SSH anymore to update. (see my post about OS crash for his explanation) When clicking on this i get different results. There have been talks about this button but I cant find an explanation of the beeps other than 4 beeps and its done. If its on here I cant find it. So here are my results..... When done I got 4 quick beeps. That means update is done. I know that part. As a test today, I just ran it again and got one long beep. I waited like 5 min after and no more beeps. an hour later I tried again and a long beep. My theory is the LONG beep means no updates to be run? Everything is working. I just want to make sure I understand the beeps!!!

Got my Polisy back up and running thanks to Michel. So there is a feature ONLY in the non plus versions (and the new firmware) that has a MOLD field in the app. It alerts you if MOLD conditions are favorable. Can you add that? Again its NOT in the Wave Plus which is upsetting. Also I am going to get a View Plus eventually. Does it support it? Jeff

Mine has nothing to do with node servers. Or at least not using one. For example I have a button to turn off all lights in the house that is program based. I hit the button and waited about 10 seconds and nothing happened. I hit it again and repeated a few times. Gave up and went to turn off lights and then about a minute later they started turning off. I wanted the kitchen light on so I turned it back off about a minute or so later it turned off. I realized the programs were spooled and it was getting to each one. So I had to wait it out before I could have the light on. I know thats my fault for hitting the button multiple times but the first one should not have taken a minute to start.

SSH wont work if you SSH'd to do the updates. I have been doing SSH here for so many years. Read the post from Michel. He will probably have to help you get back in as he is me. Things will continue to work unless you reboot the system so dont make my mistake and talk to him before rebooting. As he said, and I have learned my lesson, from now on use the admin console to do all updates. No more SSH for updates.

I agree with you. There has been two other reports. It may have been the timing of when I did this and they already fixed the issue online. The fix is going to be something UDI has to help with.

On another forum other users are reporting this issue. I asked them to post here. I think its a freebsd issue that prevents it from booting. One of my units it is not even listening on port 22 for SSH. the other responds but wont accept the password even after reset.

what cable would I need?

Please email support. AND DONT REBOOT Polisy. Once you do you will have no access because HTTP stays up until you reboot. I made the same mistake on TWO polisys. Please post on this thread also. I think this is all the same issue but this discussion is more about possible out of space. Thats not the issue the updates caused

there has to be another way into the Polisy. I tried a USB monitor but no drivers it does power up but no drivers. I have a ticket in and talking to UD tomorrow. Whatever updates are coming out from freeBSD is what did both units in. And one was right out of the box. If I had another chance I would update one by one only what is needed but the problem is out of the box the freebsd is old version 13 and all the other packages from UDI are all old. You would think a reset would load a flashed OS to restart as new but it only clears settings. Oh both units Ping just fine so they are online. Just not responding to SSH or any other method I have tried.

on both polisy now. Both reset so the password is just admin Last login: Mon Jul 4 01:04:11 on ttys000 macjeff@MacBook-Pro-Retina-2018 ~ % ssh admin@172.16.1.210 ssh: connect to host 172.16.1.210 port 22: Connection refused macjeff@MacBook-Pro-Retina-2018 ~ % or this macjeff@MacBook-Pro-Retina-2018 ~ % ssh admin@172.16.1.61 (admin@172.16.1.61) Password for admin@polisy: (admin@172.16.1.61) Password for admin@polisy: (admin@172.16.1.61) Password for admin@polisy: admin@172.16.1.61: Permission denied (publickey,keyboard-interactive). macjeff@MacBook-Pro-Retina-2018 ~ %

I did. Already got a response they had not seen this. But now I have seen it twice. And one was a brand new polisy out of the box. I was forced to run updates to get the firmware and everything up to date.

Well I bought a new polisy as a backup a few months ago. Hooked that up. Firmware was on 5.2.2 so I ran Pkg update and pkg upgrade. Again it downloaded a lot of updates and again it finished and then when I rebooted I am locked out Something is going on here. Now I am totally down with two units.