macjeff

rg

Can you at least show the latest. The winter storm warning came out many hours after the advisory. And I checked both and they have issue times and dates.

Video attached. We had a winter weather advisory upgraded to a winter storm warning. So basically there are two warnings at the same time. We also had a wind advisory but that never shows up in the video at all. So two issues- One is what if there are two advisories/warnings at the same time. Second what if one is upgraded. The problem is they dont delete the old one so really the upgraded one overlaps the other and probably only way to know is the other is newer. So I would always display the most serious one unless you can display them all. Ignore the error that pops up. I hit query too many times in a row I think 808604954_ScreenRecording2022-03-12at2_39_51PM.mov

I can confirm the backup button seems to do nothing

See screenshot. I have several of these for aquariums and hot tub. They all are missing two fields. Maybe its not being reported for this device as my regular tags are filled in. But if thats the case can you put N/A or something in the fields. When I see blank fields it makes me think its not querying all the data.

I assume you dont need the log now?

Old version 3.1.3 now installs and starts up. Thats better than nothing!! Will watch for a new upload of 3.1.4 (later timestamp) thanks

Yes. Almost every Node server I own was updated today. They all updated fine EXCEPT wireless tag. Its stuck at 3.1.3 and wont start anymore. As a test I tried to install it again in another slot and after 5 minutes nothing happens and that slot is still available. I had this happen with other nodeservers. ST Inventory, Ecobee, etc. and they had to do something and then it worked about a day later. But for now I am down with Wireless Tags because I cant get back to the 3.1.3 version and yes I did update Pg3 to latest version BEFORE I did the updates today due to the install bugs it said it fixed.

Yep that pretty much sends it up but I think its the speed of the packets. Either way the refresh does not seem to hold so for now if you have to restart your ISY there is one more step. Good news is if you are away and there is a power outage you can go into Alexa app and disable and reenable from remote

I read it as the last thing you did was install the _03 so I was wondering if that changed anything.

That works also. I sent the command to list all so people could use it to check everything and its simple But you are good!!! Now try the disable and re-enable fast. and hopefully it fixes IFTTT If not then use variables with the Messaging command

Just ssh in and type pkg version It will list all packages. Isy should have the _3 after it. But your right the console does not show the _subversion.

For all fairness, when it first came out the SAY option was the only option. I worked with them to allow messages to all devices. So no one should have to use IFTTT for messaging purposes unless there is some other need.

You dont use SAY. Say is for only the alexa you are talking to so thats why IFTTT can only use one. You have to use MESSAGING. Use messaging. Under that choose send announcement. Type what you want to say Hit next and then it asks you which devices. Choose ALL DEVICES and then it announces in all of them. Screenshots below

Thanks for posting Let me send a better instructions since I was mistaken 5.4.0_2 and 5.4.0_3 fix the issue not 5.4.0 even. I mis-spoke earlier and apologize. sudo service isy stop sudo pkg upgrade isy sudo service isy start pkg version check ISY is now 5.4.0_3 NOW it may work right away or it may not. If not go to Alexa app, skills, search for ISY optimized for Smarthome v3, disable it. IMMEDIATELY reenable it. Now it should work. If you reboot your ISY or your Polisy reboots due to power failure (You should put your Polisy on a battery backup but not the PLM) then you will have to do the alexa step again most likely

I dont use it either. I think it used to be the only way. Now using real motion, contacts, or locks or a variable is the way I think is superior but thats my opinion and I dont want to be attacked for my opinion

No. ISY shows the current x.x.x version not the _version. You would have seen it in the log as it was installing with SSH It would say do you want to install with 5.4.0_3 at the end and you say Y and it installs Sudo and do PKG VERSION and it will show you all the versions. My ISY shows _03

I know that inside alexa the device is being changed but Michel has told me he is 100% sure the devices are being blacklisted when the ISY reboots. They have to write in some throttling so this does not happen. For many of us (and every time for me) all I have to do is disable and re-enable the skill after each ISY reboot. That is a band aid until the permanent fix comes out. If it does not solve IFTTT then I cant help. Maybe someone will find a fix for that. But I literally spent all day Thursday and Friday and even restored my ISY from backup trying to fix this. I can confirm it does not work although Amazon does see the motion sensor or locks change in their app so the data is getting there but at that point the routine wont trigger due to blacklist. btw...I do know how they work. I was on the prototype team for Alexa when all the Echo could do is tell you the weather and play music and tested for UD all the way including routines. I have a master ticket in with Amazon on this and upper level can see the issue but they said its the Skill. Universal Devices said they will work on it but it may not be right away. So I came up with the workaround. I am sorry if it does not work for you, but it has for many.

You are posting in the wrong topic then. The topic is "Routines using ISY variables as motion sensors have stopped working" We are talking about ISY Variables used as motion sensors (and actually real motion and contact sensors too as well as LOCKs) do not trigger routines The IFTTT should be in another topic about IFTTT. That may still be broken but for the topic of this forum the fix we have has worked on several installs. If its not on yours I will try to help but I cant support IFTTT as I dont know it.

I dont even have an IFTTT account and have about 50 different anoucements with routines. You use Variables. A lot faster than IFTTT. Set variable to 1 when an event you want to announce occurs in a program Expose the variable to alexa as a motion sensor with motion value of 1. Create routine (SEE SCREENSHOT) where when the motion sensor (fake variable sensor) detects motion announce. I chose all devices and also send a notification to the phone. IFTTT is slow. I tried it once and killed it.

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.