dbuss

If you want to turn on a light using the light's given name, it needs to be the spoken you gave it in the ISY Alexa portal. When you assign a light to a group as I outlined, Alexa identifies it only as a light. So you have to say "turn on the light" or it won't recognize what you want to do. You could also ask Alexa to turn the same light by using the spoken you gave it in the ISY Alexa porTAL. For example. In a bedroom, I have a ceiling light and a bedside lamp. I have the ceiling light and the Alexa device in that bedroom in a group. If I say "Alexa, turn on the light", the light turns on. This is the only Alexa device that will turn on that ceiling light with that command. I do this for several rooms. That way all you have to remember is "Alexa, turn on the light" when you enter a room. If I want to turn on the bedside lamp I have to say, "Alexa, turn on the bedside lamp". Of course I can say "Alexa, turn on the bedside lamp from any Alexa device we have and the bedside lamp will turn on.

@DaveStLou, Here's how I set up my groups. 1.Open Alexa app on phone 2. Select devices 3. Press + in the upper right corner 4. Press add group 5. Select a room name from the list or create your custom room name 6. Press Next 7. Select the Alexa-enabled device you want in the group 8. Select the light from the device list that you want to turn on 9. Press save You're now done and should be able to go to the room with the selected Alexa device and say, "Alexa, turn on the light" and the light should turn on.

To make this work by saying Alexa turn on the light, you need a group with just the light you want to turn and the Alexa device you want to use for turning on that light. I have only made these groups from the Alexa phone app so.

You could control a scene that has the brightness level set to your liking.

I use polyglot to control Lifx and Hue bulbs and I can use the group feature to turn these lights on and off and the status of the polyglot node in the admin console changes accordingly. Sent from my SM-N950U using Tapatalk

When the group light is turned off or turned on the status in ISY admin console is changed. Sent from my SM-N950U using Tapatalk

@larryllix it's no different than manually switching on that light.

It works with only devices in that group. However, you can turn other lights on and off with that same echo device by using the Alexa spoken name. For example, if I walk ion the bedroom and say Alexa turn on the light, the ceiling light turns on. If I walk into the room and say Alexa turn on the bedside lamp, the bedside lamp turns on. Or I could say Alexa turn on any other device and it would turn that device on. As long as you have a spoken for that device in Alexa.

By using the group feature in the Alexa app you can assign individual echo devices and other devices like switches to a group. This allows you to walk the room with that group and say, "Alexa, turn on the light" and the light will turn on. It's a nice feature.

Does that sound right? Yes this correct. Don't have time to look at programs and see if they have support for ringing the bell and motion being detected but it sound reasonable they would. Programs do support the doorbell ringing and doorbell motion. Be sure to select "Control" in your program.

My adm console shows the same thing as yours. So, it seems like you have it set up properly. I have a notify program for my Ring doorbell and a Ring Stick-up cam and both work fine. I do use "control" in the "If" condition of the programs.

If you had the portal open when you added the devices to your ISY, pressing the refresh button on the ISY portal should add those devices to your device list.

http://www.cooperindustries.com/content/public/en/lighting/connected_systems/halo_home.html

@larryllix , Interesting, I use state variables defined as an MS and the routines work as expected. Did Alexa discover your state variable after you added it to Alexa in the portal?

I'm experiencing the same thing on my Samsung Note 8. It may update on itself after hours of leaving a location. Sent from my SM-N950U using Tapatalk

Polyglot cloud does not require a PC or RPI to run. You will need a computer to access the Polyglot Cloud dashboard. The dashboard is to Polyglot cloud as the admin console is to the ISY

My Elk works fine with 5.0.14.

It works great with the Alexa app.

@Michel Kohanim your efforts are greatly appreciated. It was more of an inconvenience than a serious problem. There are so many companies that could benefit greatly by modeling their customer service after yours. Thank you!!

I also tried changing from Fahrenheit to Celsius and back to Fahrenheit again with the same results. Stelpro tells me they don't support the ISY controller. So there's no help there. Sent from my SM-N950U using Tapatalk

I have two Stelpro thermostats controlling baseboard heaters. They have worked great. The issue I'm having is trying to change the setpoint using the admin console, Mobilinc, and AGave. When changing the setpoint on the thermostat manually, each click changes the setpoint by +-1 degree. In the admin console, each click of the setpoint of the up/down arrows changes the setpoint by +- .1 degree. To increase the thermostat setpoint by 1 degree using the admin console, the up arrow must be clicked at least five times to get to at least the current setpoint.5 setting. To decrease the thermostat setpoint by 1 degree the admin console down button must be clicked at least seven times to get to at least current setpoint.3 setting. Of course, the desired temperature can be manually entered into the admin console and that changes the thermostat temperature as expected. The larger problem is when trying to change the thermostat setpoint up or down using Mobilinc or Agave, one click of the up or down in button in both apps causes the thermostat setpoint to go to 86 degrees. This is the maximum setting for the thermostat. The only way to get the setpoint changed at this point is to use the admin console or manually change the setpoint on the thermostat. This happened at one of the upgrades, as when I first installed the thermostats this was not a problem. I think it happened when changing from 4.xxx to 5.xxx current I am using 5.014. Is there anything that can be done to remedy this situation?

Querying the device does not change the setting from 0. At least not for me.

Once you change the setting it will reflect the setting you changed to. Then you can change it to another setting if you wish to do so and it will reflect that setting. You need to make a change to get it to reflect something different than 0. However, when you close and reopen the admin console the reading will go back to 0, but the backlight will still be set at what it was set the last time.

I have the ability to set the backlight level in V5.0.14. What is the device you are trying to set the backlight level?

I agree, an Insteon siren or Z-Wave siren if your ISY has Zwave most likely would provide a higher level of reliability. You could also use both, a siren and a routine.