I’m using an android simulator and seeing the “�”. And it only seems to occur with the TH1300ZB DTH, not the others. It’s clear, if you go to the webpage and view it. It’s some codepoint issue or an extraneous control character or something similar, trust me. Whatever it is the Sinopé “é” and something to do with the temperature are both shown as the “�” in the TH1300ZB code in like 6 or so places. I see the same in either MS Edge or Google Chrome.
Here’s a screenshot of the TH1300ZB DTH code showing one of the “�”:
I read through much of this thread going back to day 1 but admit that I skipped through much of 2016 and 2017.
I personally live in a 100 unit condo building in Quebec.
Heating is through baseboard heaters but the building also has a cooling tower that feeds the central AC system in summer. Is there a smart product that can handle both?
In fact. I had bought a Nest only to find out it didn’t support baseboard heaters so I sold it through Kijiji. The products in this thread seem to support baseboard heaters but nowhere can I find anything that handles AC plus baseboard heat.
Since this seems to be the end-all thread on electric baseboard thermostat’s, I figured I’d post this here.
Moving to a new place in a few weeks and looking to replace all 15 thermostats with smart thermostats. I’ll be bringing over all of my light switches, door locks, sensors, etc… which are all zwave. Although with 15 thermostats and at least 1 in every room, I don’t envision there’d be any issues if I went Zigbee or Zwave. In fact, building a Zigbee network alongside the Zwave network may benefit me down the road if I want to add a device that’s Zigbee only.
The 2 devices I’m looking at are the Stelpro Ki STZW402+ (Zwave) and the Sinope TH1124ZB (Zigbee).
Feature wise, the 2 look like they will fit my needs. The Stelpro unit’s are currently on sale from aartech for $76.99CAD each while the Sinope unit’s are $89.99CAD. I reached out to Sinope to see if they could get closer to the Stelco pricing based on purchasing 15 units, and their response was to buy the web programmable units that were on sale but not compatible with Smartthings or to keep checking their site in case they go on sale(I was clear in my inquiry I was looking to integrate into Smartthings and to purchase right away). That’s not at all what I was looking to do, and quite honestly I was very disappointed in this response. @CharlieSinope there is definitely room for improvement here from your sales team.
So as it sits, I’m about ready to pull the trigger on 15 Stelpro Ki thermostats, but figured I’d check here first to see if there’s anybody with experience on both. Is there any reason to justify the additional $220 expense to use Sinope thermostats over Stelpro?
@MRobi, I don’t have experience with Stelpro units, but I have had 1 Sinope Zigbee baseboard thermostat and 1 Sinope Zigbee floor heating thermostat for about a year. Absolutely love them. No disconnection issues. Quiet relays. Crisp, automatically dimming displays. Outdoor temperature on displays is useful.
@yvesracine having used both, would there be one you would choose over the other, or if features and reliability are similar would you go for the lower priced of the 2?
That app looks interesting. I made a pretty good piston in webcore to control my single mini split and wasn’t looking forward to building that out to 15 baseboard heaters and grouping them all together. I’ll check it out, thanks!
You can go for the lower price unless you have issues with your zwave mesh network, then zigbee is a better bet…
About the smartapp above, you can elect a master tstat,and all slave thermostats will follow the main tstat’s mode and setpoints…
On top of it, you can create some virtual zone devices composed of 1 to many rooms (it can be for each room or a group of rooms). You can then input a delta temp (+/- degrees) for your colder/hotter rooms…
The smartapp can also automatically turn off or sets the thermostats to eco when they are not part of the scheduled zones (ex. turn off the basement/ground floor thermostats and keep only the upstairs thermostats at night)…
You just need to configure your rooms/zones/schedules and associate your tstats and any ST connected motion sensors (to detect if the room is occupied) for each room and you’re done.
For any future searchers reading through this thread, I opted to go with 15 of the Sinope TH1124ZB thermostats for the new house. Now we’re just waiting to move so I can get them all setup!
@yvesracine I’ve been reading about your ScheduleTstatZones app and it looks like there’s a ton of thought and development that’s gone into it. I do have a few questions regarding if it will work in my specific application, but instead of tying up this thread I’ll post them in the app’s thread.
@CharlieSinope I was having some issues with the custom DTHs for my TH1123ZB and TH1300ZB so I went to the Sinope website to see if there was an update. However, what I found seems to be in error or at least maybe really old.
The weird thing is that these URLs are different but the code appears to be identical. Although it mentions both thermostats in the fingerprint section, I noticed that there seemed to be fewer features and in the case of the floor heating thermostat, all of the settings for the floor are gone.
I am assuming that this is an error but can you assist in sorting this out and/or correcting it?
@CharlieSinope, can you give a non-tech guy a paint-by-numbers approach as to what I should do if I’m currently using drivers?
Should I delete the drivers and add Sinope thermostats via the app (the classic android Smarthings app doesn’t seem to list Sinope; but the new app does?). Should I add Sinope first and then remove the drivers or vice versa?
What if I’m using Webcore…will I lose my settings if I delete the driver and add the thermostats directly?
@CharlieSinope I just moved all of my thermostats over to the native integration and they now no longer show up in ANY thermostat control apps making them essentially non-programmable. Similar to v1.0.0 of the driver, the capability “thermostat” must be missing.
I was using v1.0.5 and like an idiot I deleted it before I noticed the missing functions.
EDIT: Thankfully they can still be programmed in webcore so I wrote myself a piston to handle this