macjeff

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.

This AM I ran updates via ssh and there was over 100 freebsd updates. About 1-2 hours ago I tried to SSH in and got this message macjeff@MacBook-Pro-Retina-2018 ~ % ssh admin@172.16.1.210kex_exchange_identification: Connection closed by remote hostConnection closed by 172.16.1.210 port 22 I tried many times. I checked my IP which is reserved DHCP above the normal DHCP range given out. Everything else was working so I did backup of ISY and PG3. Confirmed nothing else is using that IP. So I rebooted polisy. I can ping it but now but cant get in Pg3, ISY admin, or SSH Well SSH now goes in but wont take my password or the default admin password so I dont think I am really in So essentially locked out. About to try the reset options.

I have it above the DHCP range. Trying that and then will start resetting. I am going to post outside this topic as was told by others this may be an OS issue

my Polisy just went totally down. Posted a topic but also sent Jimbo a PM. I need to make a decision. Start from scratch (with backups) or wait and have it down. I cant SSH, HTTP, HTTPS, no admin console. But I can ping it LOL

I am basically having this issue but mine i ran updates this AM. I tried to SSH in tonight and nothing worked but PG3 and everything else worked. Then I rebooted Polisy using the command in pg2. Now I cant get in at all. No SSH, No http, no https. no admin console BUT the IP responds to a ping I suspect corrupted OS. I have backups but wanted to know if any quick fix

It now says true so there seems to be a delay that is happening. Wireless Tags replaced my tag manager this week so the bug happened with old and new tag manager. But the losing internet so far has gone away. All 3 times this happened is when we lost power and the tag manager had to reboot (or I unplugged it to change tag managers) Then it says false for a while. It was at least 90 min last night then I went to bed and its fine today. I did try logging out and back in of the admin to see it thats the problem and tried Query and Query all. I also totally deleted and add the added the Node server back last week but that did not fix it either.

Its doing it again. ST is 0. Device was offline over an hour ago. My theory is the API is slow at reporting. I just checked and all my devices in the app show updated less than a minute ago and I just forced update and it works. In ISY Admin I tried Query and Query all no change Restarted Node server no change. Did notice the controller ST is true but its the tag manager thats showing false. So I am basing my "down" program now off the controller only now not the tag manager. I will check tomorrow and see if things change. Been almost 90 min since it was down and still says false. Also attached my logs again *** also notice the Invalid Driver error in my logs. WirelessTag_7-1-2022_92444_PM.zip

I did Query manually and that did not fix and I dont have a Query all anymore. Only on Startup. I used to but Michel told me it was not needed.