dbuss

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.

You should be able to use routines to accomplish what you want to. Have you read through this?

Before I installed the polyglot solution on my Chamberlain opener, I installed a GoControl/Linear GD00Z-4 Z-Wave Garage Door Opener Remote Controller . It doesn't control the garage door but does report the status of the garage door to the ISY and you can then use that status in your programs. It works well for me. Sent from my SM-N950U using Tapatalk

@deirwin , Did you perform network heal to your Z-Wave network after you moved your ISY? If not, you may want to do that and see if your Z-Wave communications improve.

It works perfectly now Benoit!! Thank you!!

Benoit, I have a similar situation with a routine that has a scene in it. The routine turns the scene off. If the scene is turned on when the routine is run, it turns off the scene as its supposed to. If the scene is off when the routine is run, the scene will flash on and then turn the scene off. When adding the scene to the routine, it will not allow the scene to be turned off. Instead, it can only be dimmed to 1%. It makes no difference if I run the routine manually or through Alexa, the results are the same.

@Tuckerdude , Make sure that Live Update is checked in your ISY Portal. I went through the same struggles as you are only to discover that Live Update was not checked. I checked Live Update and then followed these instructions from Benoit: Disable the skill, then re-enable the skill. Delete the routine and re-create the routine

@Deuce , It's good to hear the reprogrammed MS is working from the area it needs to work from. The other MS's will need to be put in linking mode to reprogram them.

@Deuce, The motion sensor that you reprogrammed, is it now outdoors near the others that are not working? If not, you may want to locate it an area similar distance and environment as the others to see if it still works from that area. If it was interference, then why would the MS not work, without reprogramming it, when you brought it closer to the ISY? I would bring one more MS closer to the ISY and see if you get the same results as the other one.

Does it seem reasonable that it connects and sees it but doesn't allow control and keeps giving the "error" because of bad communications? Yes Looks like I will order up a few of the NZW36s. I assume I don't need anything actually plugged into them just using them to help repeat the signal? They will repeat the signal without anything being plugged into them. Unfortunately, the only place between the door lock and ISY is next to the door about a foot away in an outlet and another outlet further down that hall. It's the front door of a foyer that is about 10' wide and 40' long. RF can be very unpredictable. There are instances that you think you will never get coverage and you do. Then there are those times that you think coverage should be no problem and it turns out to be a problem. About all, you can do is add devices until you get the coverage you want/need.

@watson524 , Z-Wave is a mesh network. The more devices you have, the better the communications will be between devices. Keep in mind battery-powered devices don't repeat the Z-Wave signal. So, you will need devices such as switches, outlets, repeaters, etc. to improve your mesh network.

@Watson, This is what you should see in your ISY.

@watson524 , The ISY is most likely too far away to add your lock. You will need to move your ISY closer to the lock or the lock closer to the ISY. They need to be very close, within a few feet to get the lock included. Once the lock is included you will be able to move them further apart.

@watson524 are you extending the deadbolt before trying to exclude or include? Schlage locks usually include or exclude easily in the ISY as long as they are close enough to the ISY.

@watson524 Here you go: https://support.smartthings.com/hc/en-us/articles/115002058563-How-to-exclude-Z-Wave-devices-in-the-SmartThings-app

@watson524 Yes, with the add or exclude window open on the ISY, extend the bolt on the lock and then perform the following: 1. Press the Schlage logo button. 2. Enter your programming code. 3.Press 0 You should then get a check mark if the lock was included or excluded and an X if the attempt was unsuccessful. I would exclude the lock from your Smart Things hub before trying to add it to your ISY.

@watson524 , As long as the exclude window was open in your ISY when you entered the information in your lock you should be good. That is the correct way to exclude a Schlage lock. You should now be able to add the lock to your ISY.