Scenes Don't Really change the temperature

[ffpllc]

I have 16 thermostats installed (Venstar 1 day thermostats connecting to a ISY994i) they control the electric baseboard heaters throughout the house. I setup two scenes, one for turning them on when I am coming to the house and one for turning them off when I leave the house.

 

When I trigger the scene the thermostats in the admin console will all show the setpoint as having been changed but when I right click and query the thermostat (or go over to the thermostat and look at it) the setpoint never changed.

 

I ended up creating a program that will set the mode of all the thermostats to Heat and then setpoint to every thermostat to what I want it to be. When I right click the program and 'Run Then' the thermostat setpoints are set correctly.

 

Having it work one way or the other is already a great thing - but ultimately having the ability to just turn on the scene and have it work would be ideal. Scenes are less clunky on the web page on a phone.

 

Thanks in advance for your help.

 

--------------------------------------------------------------------------------

Stephan

[Michel Kohanim]

Hello Stephan,

 

Can you change the setpoint on those thermostats at all from ISY?

 

Please try: right mouse click | Diagnostics | Query Inteon Engine and then retry on a few thermostats.

 

With kind regards,

Michel

[ffpllc]

Hi Michel,

 

Yes I can set the setpoints on all the thermostats without a problem, the program that I created also sets the setpoints without a problem. When I use the scenes however they don't set the setpoint. If I look at the individual thermostats in the admin console they reflect the scene's setpoint immediately, but if I right click on the thermostat and click query it refreshes and shows me the original setpoint. So the admin page thinks that it changed the setpoint but in actuallity it didn't.

 

When I run the program that sets the setpoint it gets set correctly, also if I click on the individual thermostats and increase/decrease the setpoint there it also works correctly. It also works if I go to the web page and click the up/down arrows on that site.

 

As far as I can tell, the scenes are the only thing that doesn't seem to work for me.

 

BTW - on a side note, when I originally setup the thermostats to work with the ISY, the only way I could get them to work correctly with it was to do the right mouse click | Diagnostics | Query Insteon Engine - then they communicated with the ISY without a problem. I don't know if that's something that is normal but it was something I needed to do for the first set of thermostats I installed, then I did it with every thermostat and they all were able to communicate with the ISY without a problem... well aside from this scene thing.

[Michel Kohanim]

Hello ffpllc,

 

Thank you. We did fix an issue with thermostat scenes in 3.3.10. If you have not done so yet, please install 3.3.10, remove the thermostats from the scene and then add them back.

 

With kind regards,

Michel

[ffpllc]

Thanks Michel, this is a brand new install I bought the ISY a couple of weeks ago.

 

Just to make sure I did help about in the admin console and it says firmware v.3.2.6 and the UI says v.3.2.6 as well.

 

Is that what you are referring to?

[Michel Kohanim]

Hi ffpllc,

 

Yes, that's what I mean. I think if you upgrade to 3.3.10, it might solve the problem.

 

With kind regards,

Michel

[ffpllc]

Ok great, I'll give it a try.

 

Is this something that wouldn't be a problem if I do remotely?

 

Or would you recommend I do this while physically at the house?

 

Thanks

[LeeG]

ffpllc

 

UDI recommends updating the ISY image when local. The ISY supports it being done remotely but that introduces issues associated with external internet performance. Best to be done when local.

[ffpllc]

ok I'll update it when I head over there this weekend. I'll keep you posted!

[Xathros]

ok I'll update it when I head over there this weekend. I'll keep you posted!

 

If you have remote access to a PC local to the ISY, you can work remotely via that PC and satisfy the local upgrade recommendation. This is how I do almost all of my ISY updates as I don't get the time to play with the ISY when I'm home... That said, if something goes wrong and there is nobody there to power cycle the ISY for you, you may be down till you can get back to that site. A few people have reported their ISY's becoming unresponsive and needing a power cycle after the upgrade. I personally have never run into that.

 

-Xathros

[ffpllc]

Thanks Xathros,

 

Good idea, I do have a PC I can remote and I'm tempted to but just in case I'll wait until tonight when I get to the house.

[wrj0]

...if something goes wrong and there is nobody there to power cycle the ISY for you, you may be down till you can get back to that site. A few people have reported their ISY's becoming unresponsive and needing a power cycle after the upgrade. I personally have never run into that.

Some of us have powered our ISY through an Elk relay just for these rare events. A quick initiation of an Elk rule to force an output to momentarily interrupt power to the ISY allows the needed remote reset. Helps with the WAF, especially when traveling away from home.

[Xathros]

]Some of us have powered our ISY through an Elk relay just for these rare events. A quick initiation of an Elk rule to force an output to momentarily interrupt power to the ISY allows the needed remote reset. Helps with the WAF, especially when traveling away from home.

wrj0-

 

I have a DinRelay that can power cycle my ISY, Router and Cable Modem as needed. I have my ISY test for internet access and if that test fails 3 consecutive times, it will power cycle the modem and router. If I lose contatct with the ISY, I can log into the relay and power cycle the ISY.

 

I don't think this is a common configuration but is well worth mentioning for those that like to work remotely or have an ISY managing a vacation home that remains unoccupied for long stretches of time.

 

-Xathros

[ffpllc]

I upgraded the firmware on my ISY to 3.3.10 and I upgraded my UI to 3.3.9 (LOVE the new interface BTW) but unfortunately none of the upgrades helped with my scene correctly turning on thermostats.

[LeeG]

The Admin Console (UI) should be at the same level as the ISY Firmware. It is likely the fix for the thermostat Scene problem fixed at 3.3.10 was in the Admin Console, not the ISY itself.

 

Once the UI (Admin Console) is at 3.3.10 the Scene will have to be created again as it is the Admin Console that sets the data in the Scene link records.

[Michel Kohanim]

Hello ffpllc,

 

I am so very sorry to hear. At this point, I strongly suggest you contact our tech support team so that we can schedule a call and figure out what's going on. I think you have already waited too long for a resolution.

 

With kind regards,

Michel

[ffpllc]

ok I'm now using the same version on both the admin and the firmware. I created a new test scene but it still doesn't work - when I requery the thermostat the setpoint changes back to what it was before I turned the new test scene on.

[Michel Kohanim]

Hello Stephan,

 

Ok, we have now tried on multiple Venstar thermostats and multiple SmartHome thermostats and cannot reproduce this issue at all.

 

Are you sure you followed LeeG's recommendation to remove the thermostat from ISY and then add it back in and retry?

 

With kind regards,

Michel

[ffpllc]

oh I didn't remove the thermostat from the ISY, I just created a new scene and added an existing thermostat to it. I'll try that when I go back up this weekend, and if that doesn't work I'll call tech support.

 

Thanks for everyone's help!