macjeff

it shows up in the store but I posted on your PG3 support thread Climacell is updated. PG3 used to tell me when there is an update. Now it is not. Going to leave it for the day on old version in case you want me to test something later. But that blue box saying upgrade is not there. I am clearly on 2.0 and 2.01 is out. Is that a bug in the new Pg3 .14 update? I did try another browser to make sure it was not cache

@bpwwer Noticed Climacell is updated. PG3 used to tell me when there is an update. Now it is not. Going to leave it for the day on old version in case you want me to test something later. But that blue box saying upgrade is not there. I am clearly on 2.0 and 2.01 is out.

you can always log into ISY portal and I think its under information you can get the address to plug into admin console so you can log in from outside the ISY location. I also open a port through the router to make sure I can get in but make sure you use a 5 digit port like 44444->8443 and/or 33333->8080 I would go with https though. 4 digit ports are more frequently hacked, but the ISY portal method is your safest. Jeff

If it’s formatted http//111.11.11.11:8080 or https//111.11.11.11:8443 then try a polisy or at least an IOP reboot. mine rebooted automatically for some reason but maybe it’s only because of another update

All I know is that I switch the trigger of the routines to virtual buttons from ISY variables and they worked perfectly when the ISY variables were not triggering.

Open your old file in a text editor. The addresses are in there. Most end with /desc

I did notice it said DISCONNECTED for a while also with a red banner. All I did is refresh the page and then it said connected. I also see this if I try to restart a couple node servers in a row it gets confused. I will hit restart on one. go back to dashboard, go to another and sometimes it still says name of previous Node server. Again refresh the browser works. I know its not your issue here but it slows me down having to refresh all the time.

If you need any help with it let me know. I have 99 buttons installed and using over 70 of them!!! Install Node server Put in your access code (see Node server to get one) Name your buttons Then in Alexa create a routine (or if existing routing there is a change trigger option under the ... menu in each routine) Then in the ISY go to that button and click the PUSH BUTTON button. The routine will trigger. Even when Alexa was down it worked perfectly.

maybe they need to move off those buggy Amazon Web Servers LOL Just kidding. I saw app update for iOS today also. But yes I have seen intermittent issues. I gave in and used a Pg3 Node server called Virtual Buttons to trigger alexa rather than use variables as motion or contact sensors. It continues to work flawlessly. I also setup a program that updates a variable every hour and that variable should trigger alexa to say TEST SUCCESSFUL and send me a notice (of course not overnight LOL). It missed a few so they are having issues. But virtual buttons works every time.

check your ISY. Mine restarted after running it and I did not realize it. Make sure you can get in with admin console. I think the restart was from all the other package updates But also try reloading the page as sometimes the cache messes things up. If its still not working then wait for @bpwwerto respond. I would personally try a reboot of the entire polisy. One more thing. Did you wait when updating for the 4 or 5 beeps. It took a while for mine to update. Just some thoughts.

@bpwwer was correct when he said if you lose your connections you can see them in the old save file. Copy and paste them into the ISY FINDER and when all are back do a NEW SAVE and then you will have them saved and then they should work if you need to import. @Geddy is most likely correct that this was intentional but we discovered it before any announcement. It is a new JAVA app and does not like the old saved configs so something changed. Once you have the new version everything works as expected. Only issue is if you had a link to the JAVA app (stored in JAVA bundles kind of hidden) then your link wont work. But I am running it now along with the new 3.1.14 pg3. Only issue I saw is for some ODD reason after installing Pg3 my single Node server left in PG2 was not responding. I just restarted that Node server and all is fine. I am waiting for @simplextechto update it. Fingers crossed!!!!

Thanks. I will look at the file. That saves me time!!!

If you don’t mind trying something. If you happen to have an old set of saved locations when you use the save command in the admin sonsole launcher, try to load them back in and it’s not working. I will have to look up what they all were. If they are all the same location as you may have to delete one before you love them.

Something changed today.

I used the start app which redownloads the latest launcher.

I noticed the same thing. So I reinstalled the app and it still Ioxlquncher. it also lost all my saved IP addresses which included the portal and external IP I had to save them using the safe command in the old launcher but they won’t load in the new one so it must be a totally different app jeff

Will it hurt anything that we did the update packages when it was not ready. I assume it just did not even see the update so it just did the other FreeBSD stuff. But let me know if I need to do anything special once you get it fixed. thanks!!!

Ok well let me know when to try again. thanks

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.