DaveStLou

I started over and added only the lamps and Alexas in the four groups. I can say "turn on the light" in each room and that works, but not "turn on the lamp". I added ceiling light to one room and when I say turn on light, all of the lights come on - only in that room. Which is progress. I am still unable to call out individual lights within the room without giving it the full name (e.g. living room ceiling light or living room lamp). I guess I was thinking I could request individual devices in that room by the name I chose from @TomL's comment below. I haven't been able to get them to respond by the name I assign the device at all. Hmmm

I just tried renaming the lamps in the four groups I set up in the Alexa app: Bedroom, Living Room, Upstairs, Downstairs. There's a corresponding Alexa device in each group. I renamed the lamps in each group to "lamp". Next I asked the living room Echo to "turn on lamp". Alexa said okay and nothing appeared to happen. I check other rooms and found the bedroom lamp was on. I tried telling the same living room Echo to "turn on living room lamp" and, of course, the correct lamp turn on. Seems like I'm missing something on making this work.

I've used Alexa with ISY for years but I haven't tweaked Alexa settings much during that time - just added devices. I saw this thread and decided to give rooms a try. I have my ISY devices, scenes, etc., generally set up in ISY portal with the room in the name (e.g. Bedroom Lamp, Living Room Lamp, Game Room Lamp, etc.). This includes several A/V devices I've mapped through the ISY portal referencing programs, variables, etc. I assigned devices (including an Alexa devices) to groups by location (living room, kitchen, bedroom, upstairs, downstairs). I then went into the Alexa app on my phone and shorted the names there removing the room reference (e.g. lamp, TV, ceiling lights, fan, etc.) In practice though, saying Alexa turn on the lamp to the Amazon device in the bedroom for instance, turns on the lamp in the living room. Do the names have to remain unique for this to work? If so, it seems to defeat the convenience of just saying the device (One more thing to remember!). I've double checked that the Alexa devices are in the same room group as the ISY devices I'm trying to control. What am I missing?

"i.HVAC.Temp.Current" is the name I gave my variable. If you name yours likewise then you will see this when click on the then section

Go to Programs tab, then Variables tab under that. Press [Add] button, rename if you want by clicking in the Name of the newly created variable. Remember to press the [Save] button before you go anywhere else to use your newly created variable. If you ever rename in the future, it's the Save button that changes the name also in any program you've used it in. Nice feature - easy to forget to do.

Hi @Eric, Welcome to the forum. If I correctly understand what you're trying to do, I don't think you need to use the REST API. You can do this with a program, like I do. I created a Integer Variable which I named "i.HVAC.Temp.Current". In my case it's variable 22. Then I created a program like this: If 'Tstat / Thermostat' Temperature >= -50.0° Then $i.HVAC.Temp.Current = 'Tstat / Thermostat' Temperature ° Else - No Actions - (To add one, press 'Action') The if clause causes it to run every time there's a change in temp from the thermostat. If I want to send the thermostat current temp by an email, I insert the variable i.HVAC.Temp.Current into the email which ends up looking like this ${var.1.22} which represents integer variable 22. You could do the same thing with state variables if you want to use it to trigger a program to send the email notification. State variable 1 ends up looking like this in the email: ${var.2.1}. Hope that helps.

I'm in a situation where I need to replace a fan on our deck and I'm considering alternatives to FanLincs. I have two fans that have been running FanLincs for a over a year but prior to that I went through at least 4 or 5 RMA'd replacements before I got these two. In my bedroom I have the luxury of a separate set of wires for the fan and light going to the switchbox so I used GE Zwave there. Good performance but not without issues as the pilot light is not programmable on the fan controller and it glows a little more than I like in a dark bedroom. So I too am interested in alternatives. Has anyone had any experience with Bond https://bondhome.io using off-the-shelf remote controlled fans?

There's so much about this detector that is mysterious. I've switched mine to line power instead of battery. When I attempt to calibrate the temperature. I set the temperature, press calibrate and then the temperature changes to some new, apparently random value. Haven't been able to get it to calibrate to the temperature I've set.

The Uniden U-bell looks very interesting. I ordered 1 too. I'm very interested in your experience. Perhaps start a new thread?

I send the data in 3 arrays and use Tasker and AutoNotification to create the notification. I don't have time right now to write up detailed instructions but there's more information on the AutoNotification site on exactly how to do that. Let me know if you have questions.

I have had this device for several months and much of remains a mystery to me as well, so I would appreciate an ISY-oriented manual too. Anyone answering @JacktheRipper's post, please include the differences between battery powered and plugged in.

Join Instructions Download the app https://joaoapps.com/join/ (platforms listed under step 2 include Android app and Chrome extension) Get an api key https://joaoapps.com/join/api/ and click the api key link. Join uses your Google credentials so if you get an authentication error, try signing out of Google (gmail etc) and sign in again. For each message you wish to send, create a network resource as follows 'https' 'post' host is 'joinjoaomgcd.appspot.com' port is 443 path see below timeout 3000ms (YMMV) mode is 'C Escaped' For your message go to https://joinjoaomgcd.appspot.com/ then click the Join API button. and then the SHOW button. It will construct the message for you including all available parameters. Just copy the url generated and place everything in the path field beginning with '/_ah/api/messaging/v1/sendPush?... I'll be glad to help if there are additional questions. I especially like the ability to launch Tasker tasks and send arrays of variable values.

It is similar. I'm traveling right now. I'll put some notes with details together when I get an opportunity.

I use Join for most all of my notifications. I still use Pushover for notifications that are more for logging. I find that Join's integration with Tasker allows me to do so much more on my Android phone than just notifications too. He's recently taken over development of Tasker: https://tasker.joaoapps.com For example I have a persistent notification on my phone that tells me who's home, temperature inside and HVAC set point and if it's running and weather data from my weather station via WeatherPoly and ISY network resources. Very flexible and powerful. Let me know if you have questions. I've been using it for some time now. I'm be happy to share what I know.

I tend to use a similar model to @paulbates. I use ISY scenes and programs the most since I prefer to have the predictable portions of my home automation done by ISY program if at all possible (e.g. turn off lights in occupied rooms after a period of time). My wife and I use Alexa for spontaneous, on-the-fly changes in what's on or off. Since I often incorporate the Harmony polyglot, it also helps to have ISY aware of what is going on as much as possible so I can act on it with other programs. Simply said, is use ISY for everything I can and only use Alexa scenes if there's no other way to do it within ISY.

I was confused by the wording. It's working as designed.

You're right. It's missing for me as well. I tried unlinking and linking again but no change. I'm also receiving and error in the portal "Devices are not available HTTP error 500"

It was removed in the last Portal update.

Mine first just showed the node server, I restarted the node server and it added the camera nodes automatically.

You can do by setting a variable to the percentage. Something like this: Set i.Bat.PorchSensor - [ID 0177][Parent 009A] If 'Front / PorchSensor2-Motion' Battery Level >= 0% Then $i.Bat.PorchSensor = 'Front / PorchSensor2-Motion' Battery Level % Else - No Actions - (To add one, press 'Action') Then using User Variables as explained in the Substitution Variables wiki you can put them in an email. I have been less than successful in getting the 2844-222 in particular to reliably report battery and temperature to my ISY at all but it works for my Z-Wave Motion Sensors.

Learning Python is on my post-retirement bucket list which a couple of years off.

I'm am interested in this as well. I have to reinstall Polyglot on my RPi for at least the second time.

I agree with @paulbates that best is subjective. In my case, I switched to an Insteon thermostat years ago and have been very happy with it. If you're used to working Insteon devices, it's a breeze to set up and work with programming on the ISY. It's also relatively easy to integrate with Alexa through the UDI portal.

The error was invalid access code even from the test link in the original email when I received the access code. I did disable and re-enable the skill but forgot to relaunch. I've done that now so I'll look for the access code email again.

Sent