Hello all
Need help figuring out a weird behaviour, I was not able to resolve my problem despite several steps taken. I own 2 Aeotec V3 hubs (cottage and home) both homes had Stelpro Maestro thermostats model SMT402AD installed, they are both onzigbee channel 24
Installed Mariano’s edge driver ‘Zigbee Thermostat Mc’ on both hubs, and it works like a charm in home #1. For some reason, home #2 does not recognize the devices at all despite it being the same model number as in home #1 (I checked 3 times), it only sees it as a Zigbee Thing in home #2. I reset the devices multiple times, removed and tried reinstalling the zigbee things more than once. Somehow it just won’t connect !
Any advice on how to force in a driver to a device ? Or any other method would be appreciated. How can two hubs with the same firmware version using the same device models with the same driver act differently ? I am puzzled, below pictures if what I see
The devices have different firmware, causing them to have different fingerprints and one of the fingerprints is not yet included in any of the edge drivers. It can happen.
for whatever reason, the pairing for that specific device failed, leaving the manufacturer or model number either blank or all zeros. This also will cause the device not to match with any edge drivers. See the FAQ on that one:
——
Anyway, in either case, the first thing is to carefully check the fingerprint of the differing devices to see if they are the same or not. The information on how to do that is in the FAQ linked to above if you need it.
Thanks @JDRoberts for your quick reply. Took a look at the FAQ and the thermostat is close to the hub, technically it is within pairing range. It is true tho that the model number is blank as depicted in my screenshot… I’ll try something tomorrow and will swap the device from home#2 to home#1 and see if it works - home #1 hub has paired the exact same devices.
I will take a look if the device firmware as you suggested if can be updated in any way
I’ll keep you updated tomorrow once I have tried, stay tuned!
If the model number is blank, the pairing failed, and that’s why it’s only being paired as a “Zigbee thing.” It won’t match with any other edge driver until it has a valid fingerprint. So trying to pair it to the other hub makes sense, otherwise, you need to start looking at physical location or possible hyperlocal interference, such as from a Wi-Fi booster.
Hi again!
So I did the test with the other hub and the same thing happens… sees it Zigbee Thing
So the only other option to figure out the issue was to open the device case and see if the device is indeed the same as my other thermostats, turns out the model number indicated inside reads SMT402AD01, the other ones already paired are SMT402AD without the 01 which may explain the issue. Looks like some of them are more recent than the others, despite looking exactly the same on the outside. Tho glad to know there is no interference between wifi and zigbee on my network.
So @JDRoberts, my analysis points me in the same direction as you suggested, could be related to requiring a distinct fingerprint!
Next step is to ask @Mariano_Colmenarejo to kindly help me with this one by adding this below device to your Zigbee Thermostat Mc driver ? Thank you!!
It will update automatically in 12 hours maximum, but I think you can force the update trying to delete the old driver with paired devices, but I have not tried it
───────────────────────────────────────────────────
Name Zigbee Thermostat Mc
Version 2024-05-23T17:50:19.229726453
───────────────────────────────────────────────────
- id: "Stelpro/SMT402AD01" # Added M.colmenarejo
deviceLabel: Stelpro Thermostat
manufacturer: Stelpro
model: SMT402AD01
deviceProfileName: thermostat-stelpro-profile
wow faster than lightning ! @Mariano_Colmenarejo
I was already impressed by all your work, but having this done within 15 mins is definitely worth getting world guiness record award ha ha ha! I’ll try this today and will let you know
Hello @Mariano_Colmenarejo
I have been unsuccesful pairing my thermostat. I took a look at the driver fingerprints on your github repository for that specific driver - Zigbee Thermostat MC - and it looks like the fingerprints you posted above that match my device do not exist yet. Can you kindly take a look for SMT402AD01?
Thanks!
Your fingerprints are added in the driver version I posted.
───────────────────────────────────────────────────
Name Zigbee Thermostat Mc
Version 2024-05-23T17:50:19.229726453
───────────────────────────────────────────────────
It is not updated on github because I haven’t had time to do it.
It should be able to pair with the Zigbee Thermostat Mc driver.
Try pairing it near the hub and following the steps to put the thermostat in pairing mode
Thank you so much , it is the only channel I can find with a fingerprint that can detect this stelpro model, but the thermostat seems to be in heating mode only in smartthings even when it’s not, how can I fix this?
Hello @Mariano_Colmenarejo
I have the same behaviour with the thermostat SMT402AD model always at heating - It would be nice to have th eoption set it to OFF completely in the routines. At the moment the minimum we can set is 5 degrees celcius and does not allow lower than that.
According to manual and according stelpro profile in stock driver does not support ThermostatMode capability.
Does the physical thermostat have an on/off button? I don’t see it in the manual.
It seems that the way to indicate that the thermostat is heating (on) is the thermostatOperatingState capability in the App, which would correspond to turning On the indicator (8) or (3) on the physical thermostat when it is heating and turning it off when the current temperature exceeds the heat setPoint. Is this correct?
In the manual setting heat mode means setting the type of baseboard or fan heating to be used
Therefore, to make routines you would have to use the thermostatOperatingState capability with the values "Idle" for Off or “Heat” for On
To turn it off, I think, you have to set a temperature of 5°c. Or how do you put it to off on the physical thermostat if there is no off button or an off mode?. I haven’t this thermostat to check.
If this is not how thermostat works, explain to me how it works and I will try to find a solution.
The physical thermostat doesn’t have a “Off mode”. I was thinking the “Idle” / “Heating” specify when it’s running vs not heating as you said when it’s above/below setpoint.
I have another thermostat of the same model, which indicates “Idle” state in the ST Android app. Those states are not moving at all.
The Fan mode is different, it’s Off on this one, so not matching either.
I also have another similar model MaestroStat using the same profile, they also report idle when I force them to heat.
In other words, the profile State status seems to report something else than the state
When I added these thermostats I only added them to the driver and stelpro subdrivers of the stock driver.
Nobody told me that the operating heating or off state didn’t work, I’ll see how the subdriver handles it if you send me the CLI logs to see device messages
In any case it should be Stelopro who fixes it although it seems that these thermostats are discontinued in production.
the heating mode with fan or baseboard heater is something customized by stelpro and it is not possible to work in smartthings if stelpro does not expose and publish which cluster and custom attribute uses to handle it.
If you have a MaestroStat model thermostat then it should work with the stock driver and it would be smartthinhs who will fix it if it doesn’t work.
Try installing this driver version or wait 12 hour to auto update it.
Then re-install your device with this driver version to device reconfigure
───────────────────────────────────────────────────
Name Zigbee Thermostat Mc
Version 2024-12-18T20:34:13.044402479
───────────────────────────────────────────────────
Thanks for the explanation. And yes lol, I found the capability/attribute “thermostatOperatingState” on the other page
It is not auto refreshed like the humidity, I figure it is updated only when the refresh command is clicked, I will live with it now that I understand, guess Stelpro will not maintain these. Your update make it work good enough.
