macjeff

what verson of the ISY There is a 5.4.0 and a 5.4.0_2 and 5.4.0_3. sudo service isy stop sudo pkg upgrade isy sudo service isy start should bring in 5.4.0_3 which I think is newest. Wonder if 5.4.0 even has issue. I actually just realized I only did this test on _2 and _3. But it worked for others including me several times.

Maybe the reason you lose devices is because of IFTTT. I dont use it. Can you not use fake motion sensor variables instead? Like when my garage door opens I sent GarageDoorOpen to 1 and GarageDoorRelay to 1. I have a routine that announces when grarage door relay is 1 as Jeff's Garage Door Opened and then when its zero Jeff Garage Door closed. Then the GarageDoorOpen variable is used at midnight. If its 1 that means the garage door was left open so alexa announces it. I know I could set a program to close it. We tried that and my wife left the van back hatch door open and the garage door hit it. close to 1000 in damage to the door. So I do the alert and close it manually after looking at camera.

Yes Amazon alexa support is pretty much saying dont use the browser. As I said my guess is a support nightmare with all the browsers- Edge, Explorer, Chrome, Firefox, Safari, and others like Opera.

No but you can easily create my test. And you can try discover devices. Create a variable named TEST In the portal expose the variable to alexa as a motion sensor called Test Variable with 1 being motion Discover devices on alexa. Set your variable to 1 while watching the device on the phone in your alexa app The device should show motion within a couple seconds. Change variable back to zero. Now it should show no motion;. Create a routine If Test Variable shows motion, then announce something like TEST SUCCESSFUL on your alexa. Now change variable to 1 again. Sometimes I had to do this twice but once it works it keeps working on all of them If it does not work disable the skill and immediately re-enable it. Try again. My tests works every time. 5.3.0 does not need this. Tested on 5.4.0_1, 5.4.0_2, and 5.4.0_3 and you may have found another bug with IFTTT. I know Michel said devices are basically being blacklisted because the Polisy sends stuff so fast compared to old ISY. So maybe IFTTT is not fast enough and comes in too late. I am just guessing. But try without IFTTT and if it works now we have a new issue to report with IFTTT

I use the app and lost no devices. Amazon is trying to push people out of the browser to the app so they dont have to support the browser. I like the browser still for some things but I think Routines is removed from browser. I know you dont need it for this task though. But thats for posting you did not lose devices. I remember years ago that did happen to me and I complained. The other day I deleted some devices and added new ones with similar names. When I asked alexa to do something she said there were multiple devices with that name. I went in and the old ones were still there. I manually deleted all of those and then discovered devices. And thats another point. Even if you delete every device you can just discover devices again and they come right back. There is a chance the program would be messed up. Its the portal thats the real brain here.

3 of us have done this and none of us lost devices. You have to immediately re-enable the skill and no devices are lost. No routines are changed. We are talking Skill called ISY optimized for Smart home v3. I just called Amazon support. They said it USED to be that way but now even if you delete a device you must go in and manually delete it. So I tried 3 times in a row. Just DONT discover devices until after you re-enable it. No devices lost on my end. So if you are losing devices you have another problem or you are deleting them off the portal and not the alexa account. The user below posted on this forum and I worked with him doing the same thing and it worked. This is what fixes it. If you are worried screenshot all your devices and routines first. Save your spokens out of the portal. I did all that before the first test but have not needed them once. garybixler

I helped a couple people off the forum and it worked for then. I just did the test again. Rebooted ISY. Routines would not trigger. Disabled the skill and then re-enabled it. Boom it worked. You DONT delete your devices. DONT disable the forum. Just open the alexa app. Go to skills. Search for ISY v3. then hit the disable button. Then hit the enable button. Then authorize it with your portal account. Then it will give you success. When you close that it will ask you to discover devices. Does not hurt to do that but I also tested without and it still works. As long as you DONT touch the portal your devices will be fine. During testing I must have done this 20 times.

I am working with Michel on this. I helped a couple of you so far in Private Messages. Go into Alexa Skills Disable Alexa Skill Immediately re-enable skill. You dont have to discover devices unless you just added a new device. Problem will be fixed UNTIL you restart ISY or Restart Polisy and then you have to do the same. This started in 5.4.0 and they now have 5.4.0_3 but the issue still exists. I created a test variable I can turn on and a routine in alexa that fires when that variable is 1. So I will be testing with tech support.

I am a beta tester for a living so I guess its part patience but I also dive into the bug to give a good report. Sorry if it came off wrong. Tested and working now. thanks

Deleted it totally Reinstalled same slot 3.0 (says 3.01 on install screen but 3.0 after install). Tried a different slot - still 3.0. It has to be a bad upload or something

No matter what I do I cant get it to update. I restarted nodeserver three times. Takes a while but still says 3.0 when you go to config,. Restarted Pg3. Still 3.0. There was a purple air update to 2.01 and that updated on restart of Pg3. Do I need to erase and reload the entire nodeserver?

Did you wait at least 15 min before rebooting. It has to reflash and I made the same mistake and rebooted too early. Just repeat procedure.

Talked to Michel at UD. He said do the 6 quick pushes of the reset button and then walk away for 15 min. Dont do what I did and get impatient. It will reflash and then reboot (you should hear a beep) but I did not. Wait a good 15 min before logging back in even though the light may go away sooner. Worked for me.

I have the flashing light also. But dont want to do this if it will clear anything else. Does Universal Devices agree to do this?

Amazon said they have over 100 tickets and created a master ticket so it looks like its on their end for this one!!!

I am calling Amazon. You should probably call too. I confirmed it is seeing motion on its side but not responding to it.

I use variables. If garage door is closed set variable to 1. When alexa sees variable one it announces the garage door was closed. Seems to be issue on Alexa side but strange it started almost the exact time of upgrade.

THANK YOU You saved me hours of testing. Thinking it was on my end. I have put a ticket in with UDI. I will mention you in the ticket in case they need other logs. Now there is a chance Amazon has the issue and it happened at the same time but if that was the case my controls would not work and they do.

Can someone please test this. Run a program that exposes a variable to alexa as a motion sensor and have alexa run a routing and say something. It was working just before 5.4 update. Not working now. I even created a new one. Variable setup in ISY and expose to alexa as motion sensor and 1 is activation Discover devices In alexa routing put if motion sensor is activated then say something or do something run program in ISY to set variable to 1 I watch the variable change to one but nothing happens in Alexa. **Controlling alexa devices does work Its just the variables

I have another topic for this last weekend. Pg2 and Pg3 have this issue. Some fields will come in and update. Others will be blank. Most commands like for valves and stuff wont work. You can update there

First I did clear JAVA cache so thats not the issue. Waited 3.5 hours for update ** seems like blank fields dont fill in but the ones that were not blank are updating I have a more complex system than most so maybe my issue is it needs more time before PG2 and Pg3 initializes the fields in the the ISY. Maybe this can be a setting? Using PurpleAir as example I went to Pg3 and looked at the DC node I sent picture of above and all the values are there but 30 min after update they are all still blank. Even if it takes a while to come in there has to be a way to force the values to come in even if the nodeserver only updates once a day. (Query All should do that) Like if you have a program to put a siren off if some value is not a certain amount then the siren might go off. So I would rather have the last known value than no value. I took a loot at logs and there are errors (see at bottom of post). I restarted purple air (not all of Pg3) and it started up with NO ERRORS and it is now updating fine. Nodeservers that are not working . Most nodeservers seem to have these errors. And the errors seem to be close on all the ones by the same author PG2 same issue Linktap- Data was in fields but would not update and no commands worked. Had to resatart this one. Could not wait. Everything worked after restart Hue- Some fields missing Netatmo- Status says true but all other fields in modules blank Ecowitt- Controller online field is blank. Other fields are fine and updating Pg3 nodeservers I am using and whats missing: Climacell- Only missing Nodeserver online field. Others seem to be updating but blank ones stay blank Weatherbit- Only missing Nodeserver online field Others seem to be updating but blank ones stay blank NOAA- missing 1/2 the fields Others seem to be updating but blank ones stay blank OpenWeatherMap- Only missing Nodeserver online field Others seem to be updating but blank ones stay blank Notification- This one is strange. Would not send ANY notifications but all fields were fine. Restarted the nodeserver and then all of them sent. I can confirm all notifications were working before the ISY was restarted. Wireless Tag- Perfect!! No issues Ecobee- Perfect!! No issues Weatherflow- Perfect!! No issues Kasa- Perfect!! No issues Harmony Hub- Seems fine ST Inventory- Perfect!! No issues Timedata- Perfect!! No issues Purple Air- TOTALLY BLANK until restart as noted above and error log below 2022-03-01 07:39:18,214 Command udi_interface ERROR udi_interface:write: Exception in thread 2022-03-01 07:39:18,219 Command udi_interface ERROR udi_interface:write: Command 2022-03-01 07:39:18,219 Command udi_interface ERROR udi_interface:write: : 2022-03-01 07:39:18,220 Command udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2022-03-01 07:39:18,220 Command udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.8/threading.py", line 932, in _bootstrap_inner 2022-03-01 07:39:18,226 Command udi_interface ERROR udi_interface:write: self.run() 2022-03-01 07:39:18,227 Command udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.8/threading.py", line 870, in run 2022-03-01 07:39:18,230 Command udi_interface ERROR udi_interface:write: self._target(*self._args, **self._kwargs) 2022-03-01 07:39:18,231 Command udi_interface ERROR udi_interface:write: File "/var/polyglot/.local/lib/python3.8/site-packages/udi_interface/interface.py", line 667, in _parseInput 2022-03-01 07:39:18,236 Command udi_interface ERROR udi_interface:write: self._handleInput(key, input[key], None) 2022-03-01 07:39:18,236 Command udi_interface ERROR udi_interface:write: File "/var/polyglot/.local/lib/python3.8/site-packages/udi_interface/interface.py", line 798, in _handleInput 2022-03-01 07:39:18,239 Command udi_interface ERROR udi_interface:write: self.nodes_internal[item['address']].query() 2022-03-01 07:39:18,239 Command udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/00:0d:b9:53:2c:34_13/nodes/purpleair.py", line 86, in query 2022-03-01 07:39:18,241 Command udi_interface ERROR udi_interface:write: for node in self.nodes: 2022-03-01 07:39:18,242 Command udi_interface ERROR udi_interface:write: AttributeError 2022-03-01 07:39:18,243 Command udi_interface ERROR udi_interface:write: : 2022-03-01 07:39:18,243 Command udi_interface ERROR udi_interface:write: 'Controller' object has no attribute 'nodes'

I just did my upgrade and will leave things. A few nodeservers are fine like WeatherFlow which is Pg3. But look at the screenshots attached. NOAA is especially bad. PurpleAir is totally empty. I am not doing it now but as before I would leave an hour or two and nothing so I restarted Pg3 and then they are all fine. So it might be weather ones are slow to respond but I did a Query on NOAA and got an error. I attached a screenshot of that also.

Couldn’t have said it better myself. I would be fine to wait for next update if it could get the last update. PG3 was not rebooted so should still have current data. ISY was rebooted but a lot of fields are empty and even a manual query does not bring the data in. This causes programs to not run correctly or run when they should not. Yes a reboot of PG3 fixes the issue but hope this is not the solution Jeff

When I do this most the time I’m just choosing restart from within IoP. I didn’t know that also rebooted the other services.

So is there any way to automate this. Sometimes I do a reboot and then walk away. I guess I will have to remember to reboot PG3 every time