I recently bought one of these babies and two weeks in it’s still working great! The installation was super easy - just connect two wires, screw the backplate in place of the old thermostat, and snap the new one into it (can be done in 5 min flat). The DTH from here works great with my SmartThings setup; thanks @gouroufui :
Unfortunately what I got instead was the STE402+ which is neither ZigBee nor Z-Wave enabled. On that note, I am still baffled as to why the STZB402+ (ZigBee version) supports fan forced baseboard heaters whereas the STZW402+ (Z-Wave version) doesn’t. @gouroufui, do you have any idea why that’s the case? I typically prefer Z-Wave devices over ZigBee ones when I have the choice but in this case that wasn’t even an option.
In any case, I have three more of these on order which will round off my smart heating system made up of four STZB402+ thermostats, a few Aeotec Gen 6 sensors scattered throughout my house, a Z-Wave plug-in switch connected to the hot water pump, and a bunch of apps + rules. So far it’s looking very promising and a bargain when compare to installing a central HVAC system (might still go with that one day for the AC but not really required here in Seattle).
Unfortunately, I have no insight on why Alexa responds this error message.
Our Stelpro thermostat is hooked on SmartThings platform with a limited set of options.
The Alexa-SmartThings integration is hidden from us developpers.
I asked SmartThings for some clue on how to make our thermostats Alexa compatible and they couldn’t be of any help.
I won’t share the god’s secrets, but here is what I can tell:
Despite being very similar in look and features, both Z-Wave and Zigbee have different electronic designs.
Stelpro Z-Wave thermostat does not support fan forced heaters due to some technical constraints.
The ZigBee version does include other electronic components which enabled us to support the fan-forced heaters.
Yes, but it’s Z-Wave, this post is for zigbee.
Anyway, please give a try to the following z-wave device handler.
It’s a work in progress, but it might work for you.
Sure. I am not able to control the thermostat using Google home and that’s the reason I bought this thermostat in the first place (since the smartthings+Home integration worked well per the reviews). When do you expect to get this functionality back? It will be great if that is restored asap.
I’m working on a fix for the z-wave device (see my post above).
If it works fine, I will port the change to the zigbee device handler.
Please keep in mind that this product was released prior to any Google Home integration with SmartThings, it was not design to be compatible with Google Home in the first place.
If anyone out there has some tips on how SmartThings is working with Google Home, feel free to contact me.
I’ve asked SmartThings already, but no answer so far.
Thanks. I received and installed my new replacement thermostat and the cyclic noise is gone, phew! Thanks for the prompt support. I want to order 2 more of these for other rooms, but will wait for the Google Home integration before I buy.
That’s working great for my z-wave. Alexa is able to report the current temperature and change the setpoint. I was unable to set the mode eco / comfort via Alexa but I don’t really use the mode setting anyway.
Is there a reason the device handlers in your github repository are *.txt and not *.groovy? If they were *.groovy the github / smartthings integration would allow for slightly easier / quicker updates.
The reason why the device handler is in .txt, is very simple, it’s the format that was used when I saved it.
Would it be much simpler to have it in .groovy?
I thought that the github / smartthings integration was made only by doing a copy/paste of the code…
So why the format is important?
Hi @akashr and @JamesW , please see my post above.
There is a beta version to make the Stelpro Ki ZigBee thermostat compatible with Google Home and Alexa, please give it a try.
Just installed the Stelpro Ki STZB402+ Zigbee Baseboard Line Voltage Thermostat so I can control my fan forced electric heater in my garage with Alexa and SmartThings. Installation was a snap and paired right up to my smartthings hub that is about 30 feet away. I definitely like that fact that I don’t need the hub like I do for the Sinopé system I bought last year.
The one problem I am seeing is I can’t say Alexa, set thermostat to 70 degree. Getting that to work would be awesome. To work around it I just created a routine for turning it on and off as needed.
I’ve downloaded the most recent device handler and can not get any of the commands to work. For instance:
"Set (thermostat name) to 80 degrees - Response “that command does not work on…”
“What temperature is (thermostat name)” - Response “I’m not sure what went wrong”
JF - thanks for working on adding Alexa support to the device handler! I’ve been using Alexa Helper which works great…but it would be so nice to have this functionality through the thermostat device handler itself. I think it would make things a lot smoother. I have 3 of the Zigbee Stelpro and 1 of the Z-Wave Stelpro thermostats through-out the house. Your posts and support on the forums has been invaluable in setting the thermostats up.
I’m experiencing the same issue as James with my Zigbee Thermostats and the beta device handler. When I ask for the temperature Alexa says “I’m not sure what went wrong” and when I say “Set the bedroom/kitchen/bathroom to 72 degrees” Alexa responds “that command doesn’t work on…” I tried turn the bedroom heat on and that worked (but it could have worked because that’s the same command I use with Alexa helper).
I’d be happy to help out in any way I can since I have 3 of these. I can send you logs, etc. as you work on getting the device handler working with Alexa.
and that’s the reason I bought this thermostat in the first place (since the smartthings+Home integration worked well per the reviews). When do you expect to get this functionality back? It will be great if that is restored asap.