I only have SRT 323 and 321. No added complication of the 303, I use the 321 to trigger a virtual switch. My fingerprints (device id) from the old IDE and (new CLI) are:
Unfortunately, the channel invitation from @noondawg isn’t working, just spins after logging in.
Maybe someone else in the thread with channel experience can help but in parallel I will look at getting a channel up and running. I have the CLI installed, so let’s see.
I will work on my own channel with both SRT323 and SRT321 this evening (at work now).
Interesting that your SRT323 is also ‘mfr:0000 prod:0000 model:0000’ like mine. @NoonDawg , I think you channel is only SRT321, right?
Hi @Willboyes
Here is the invitation I have created (this is my next attempt):
Id [Invalid]
Name Willboyes
Profile Id [Invalid]
Expiration
Accept URL [Invalid]
Let me know how you get on.
The third driver, SRT Thermostat does not work.
Hi Jim,
I am venturing outside my knowledge base here but,
in the Smartthings app, when you click on your Smartthings hub icon;
then click on the 3 vertical dot menu, do you see a ‘Driver’ menu entry?
If so, click on ‘Driver’ and scroll down to ‘Channels your hub is registered to’.
Do you see any entries?
I presume you have enrolled in the Smartthings Edge Beta program!?!
Depending on what you see, I will carefully reread the invitation guide and have another go this evening.
Worst case, I will share the code on github, but you will need to use the Smartthings CLI to work with that.
Cheers,
Aidan
I have switched the 321 over to your driver. It is working a treat.
It was detected as the Secure SRT Thermostat so I had to change driver. No problem.
It took a little while to sync up but when it did, it looks like a great driver that completely matches the functionality of the stat (and some more) - the previous DTH was never really right, so I am over the moon with it.
Glad it worked for you.
The SRT321 was a bit tricky, the SRT323 more straightforward.
I would like if they both reported room temperature more regularly, but I do not want to be heavy on the batteries.
Cheers,
Aidan
Glad it’s all working for you.
I think 15m is the wake up interval.
I seem to remember that temperature reporting is based on temperature change; I would prefer hourly reporting (every 4th wake up).
The batteries on my SRT321 were reporting low (31%), so I replaced them.
Alas I had to reconnect to my hub and now it is all messed up.
I cannot change the setpoint from the app or see the current temperature (both showstoppers).
Oddly, I can see when the setpoint is changed physically (that was the thing I had most trouble with first time around).
I will make sure that my ongoing work does not impact the ‘Secure SRT Thermostat’ channel that you are using.
Hope you got your issues sorted. Some feedback from me after running for a few days.
SRT321 - As you mentioned, the temperature only seems to report when there has been a change of 1 degree. What this means for me is that any temperature reported is always something point six. Ie: 16.6, 17.6, 18.6 etc. Thermostat Mode reports OFF and Heat in real time which is perfect for my use case.
Strangely, like you my battery jumped immediately to 31% with the new driver. Can’t be absolutely sure but I think it was pretty full before switching over. I’ll replace the batteries soon and monitor.
SRT323 also reports temperature on change, but at 0.1 degree increments. Again thermostat mode changes come through in real time.
If the 321 can be configured to report at 0.1 intervals as well that would be perfect. I recall there were some config params that the stat could pick up when it reported in.
Hi Jim,
I did get things working again.
My issue was that I was not getting reliable ‘WAKE_UP’ events from the SRT321.
After reinstalling the driver, I would get a few ‘WAKE_UP’ then nothing.
This meant that my routine or app setpoint changes never got sent to the SRT321.
After updating the driver with reinstated logging, I found that changing Settings → Reporting interval caused ‘WAKE_UP’ events to be more reliable.
The danger of making the temperature reporting interval to ‘.1’ is it will impact battery life.
I seem to remember a recommendation of ‘.5’ somewhere in Secure documentation.
Certainly ‘1.0’ seems too coarse.
Currently there is no way of setting that value in my driver; I will explore adding it.
In my development SRT321 driver, I request the room temperature every hour (fourth 15m WAKE_UP).
If I get to a stable/sharable state, I will investigate updating the channel.
Re: SRT321 battery, mine had been fitted since March 1st.
Too early for me to compare Groovy vs Edge for battery life.
Cheers,
Aidan
Hi @burtonjk and @Willboyes
After much trial and error I have a new version of ‘Secure SRT321 Thermostat’.
This has Setting entries for:
Temperature reporting delta (tenths of a degree).
Polling Interval (wakeup iterations).
in addition to the existing Reporting interval (minutes).
