macjeff

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.

I just checked and they are all 1 under ST BUT I also looked and my false is now true in ISY. I have done nothing to it since I filed the ticket. STRANGE

I have a program that alerts me if a Node server is offline and its telling me Wireless Tags is offline. As you can see in the ISY it shows FALSE as connected (See screenshot) In PG3 it shows connected (see screenshot) I restarted the Node server. In logs I see invalid drivers for some of the tags. BUT The data for all the tags is correct, Also attached my logs Not sure whats wrong. I did just upgrade to the latest version 3.1.6 a day or two ago but my program just reported tonight. WirelessTag_6-27-2022_85625_PM.zip

I know your speaking to someone else but I have no green icons (the need to write data ones) in my tree. The delay for me is not only programs but standard insteon Motion Sensors (Gen 1) sense motion and it may be a minute later they turn on. And some programs take a while to trigger. This has been an issue for a while. Learned to live with it.

I had one this week where the delay was like 30 seconds. I have created a ticket a while back but it closed due to inactivity. So I have no update to post.

Thanks!!!!

that makes sense as I was told UDX was dependent on PG2 and once my last Node server is ported NOT to disable PG2 until told its ok. I wont touch anything for now but I assume the upgrade packages does the sudo pkg update and then upgrade for you like the GUI did in PG2 (for those who dont like SSH) Like yours my Upgrade BIOS is greyed out. Wonder if we should enable TPM or not. Again I am waiting to touch any of these but curious.

and I emailed Michel to ask what it changes/fixes.

there is no official announcement nor did it show up in my ISY. But I did this in SSH and its working fine!!! sudo service isy stop sudo service udx stop sudo pkg update sudo pkg upgrade sudo service udx start sudo service isy start then I had to delete all JAVA cache or it will throw an error. Then use the start.jnlp to redownload the isy launcher. Wait a little while for it to start up and query on restart. then run ISY launcher and log in. Worked for me and working fine (So far)

I did talk to their people. They are having issues being blocked by some email services. Mine is icloud (apple) so I added a second gmail account. PUSH was turned off so I turned it on so it should give me a push notification. But still would be nice to know on the ISY side. thanks.

I just realized my tag manager was down for 3 days. My ISY reports stuff to me and I noticed each report was the same temp for a while. So I looked and the tag manager had been unplugged. The Node server was still online. Everything says True and connected Is there not a way to know the tag manager is down. I am also surprised they dont tell you in the wireless tags app. Jeff

Thanks. Perfect.

Is there release notes on Pg3? Like saw a new version .62 today and curious what was fixed. Would like to bookmark it if there is a forum or wiki on the version history

I had this issue. Assuming you did delete the PG2 stuff before going to pg3 sometimes it did not delete from ISY. Go to ISY and under the Node server menu I think you go down to configure. See if any of those are there and if so delete them from ISY. Then add them in Pg3. This happened twice. Once when doing the original conversion and once when deleting a Node server when I had the admin console open at same time. Both times the delete in the admin console fixed it ** make sure its deleted from both pg2 and pg3 first before deleting from ISY. The only reason you should have to do this is if all else fails.

That did not work for me. I had to manually do each node. The restore did not work but that was several months ago

It’s kind of a headache but worth the effort. You have to delete it from PG2 And then immediately add again to PG3. On most of the node servers everything was fine because the names and everything are exactly the same but in a few of them I had to a tweak some programs.

Update… Just tried to pg2 version and it works fine so my issues are only with the PG 3 version

My token is in there and as soon as I enter it all of my cakendars show up in the gray section so I know it’s talking to it. I listed all of my calendars like you did and waited and nothing happened and then I restarted the node server and now all the calendar names are gone From the gray area. Giving up for now I have to head out for now

That’s probably why it’s not working for me. Is there any chance you could send me an example of exactly how to put it in there under custom configurations. I know my counter names will be different but I wanna make sure I have them today and tomorrow correct. There are no instructions after you get the original authentication done which is working but then it’s stuck