Thanks Aidan
I read there is up to 12 hours propagation time to reach subscribers. I’ll check again this afternoon and let you know.
Regards
Jim
Thanks Aidan
I read there is up to 12 hours propagation time to reach subscribers. I’ll check again this afternoon and let you know.
Regards
Jim
Thanks for sharing this Aidan, I’ve not had chance to look into this yet but this looks really useful.
Will
NP @Willboyes ,
The most recent invitation in this chat should still work.
Let me know if not. (I will see if I can delete the earlier faulty one to avoid confusion.)
Cheers, Aidan
Hi Aidan
Just to confirm, the driver updated itself at some point during the day today. I see the new settings and I am getting updates every 0.1 degrees of change.
Regards
Jim
Yes Aidan SRT321 only on the channel I created from your source code
Is anyone experience major battery drain. I seem to be. One the thermostat I get the wireless icon constantly flashing which the documentation say it’s trying to connect to the boiler switch bit they are definitely connected as when I turn the dial up and Boiler switch turns on and when I turn thermostat down the switch turns off. I wonder if this trying to constantly connect is causing the battery drain. Batteries lasting 2 or 3 weeks at present. Used to last months. Also tried excluding and repairing with no joy
Hi @NoonDawg ,
First a check on the driver version you are using for your SRT321??
Are you using ‘Secure SRT321 Thermostat’ driver?
Next, what ‘Settings’ are you using?
I am using
‘Reporting interval 15’
‘Temperature reporting delta 5’
‘Polling interval 12’
and have fairly good battery life (currently showing 79% after 3 months).
I have routines that change the heating temperature 4 times a day. (morning on/off; evening on/off).
@jaidank
Yes that is the driver.
Same settings as you.
Draining at 2% per day at present.
Same 4 on/off timer settings too.
Is your wireless icon flashing? As I’ve only noticed this since changing from DTH to driver but it may have been doing it before that but I hadn’t noticed.
Early days but hopefully I’ve fixed the issue with better install instructions. It’s stopped the icon flashing so hoping this resolves the battery drain issue. I probably used this years ago when I first setup with smartthings DTH but didn’t when I set up using drivers.
Hope this helps others too. Instructions are for Fibaro controller but it’s same procedure
@NoonDawg
No, my wireless icon was not flashing.
I was going to ask about distances between Thermostat, Actuator, and SmartThings.
I sited my actuator in my kitchen with a cable through a brick wall to the valve being controlled.
I did this for a better signal but also to be able to see the on/off state of the actuator.
Hopefully you are sorted now (the Secure documentation was not great either).
Hi @jaidank, any idea when I have a secure srt321, but the productId doesn’t seem to match. Looking from graph.api.smartthings.com I get:
Data:
Raw Description:
zw:S type:0806 mfr:0059 prod:0001 model:0005 ver:1.00 zwv:4.05 lib:02 cc:5E,72,86,80,84,31,43,85,70,5A,73,59,42,40,20 ccOut:40,25
So its looking like mine is productId 5.
I can’t get it to recognize it as your edge driver, only installs as “Z-Wave Thermostat” and no possibility to change the driver in the smartthings app.
Hi @lvikstro ,
As soon as I can get my development environment up and running again I will add a fingerprint for your mfr:0059 prod:0001 model:0005 and publish an update.
Cheers, Aidan
Postscript: I have updated the SRT321 driver but am struggling to fingure out how to update the channel with the updated driver. Bear with me.
PostPostscript: I have updated the driver:
Secure SRT321 Thermostat ID: 12ab013a-546b-47c2-a9b6-0a043f1ce8b4 Ver: 2023-03-04T17:03:08.265842616
in 551fb634-c607-45b4-b45f-be13a1040a7b channel
Hi @lvikstro ,
I have updated the driver:
Secure SRT321 Thermostat
ID: 12ab013a-546b-47c2-a9b6-0a043f1ce8b4
Ver: 2023-03-04T17:03:08.265842616
in 551fb634-c607-45b4-b45f-be13a1040a7b channel
@jaidank
It hasn’t updated yet, and I seem to be registered for this channel: channels/884c23ca-3ef7-4187-899f-99c997cb3b46/hub/…
Do I need another invite to get to that “551fb634-c607-45b4-b45f-be13a1040a7b” channel? I tried to just change the url to have that channel guid instead to be able to install that instead, but it doesn’t open like that.
Hi @lvikstro ,
I tried and tried to update the SRT 321 driver in the older channel.
Gave up and managed to create an invitation to my later channel (that includes some test work):
─────────────────────────────────────────────────────────────────────────────
Id 15fdcfcf-1b45-469e-95d0-91f8e908e8fc
Name lvikstro
Profile Id 61a79569-e8fd-4a4d-9b9c-a4a55ccdd15e
Expiration
Accept URL SmartThings. Add a little smartness to your things.
─────────────────────────────────────────────────────────────────────────────
@jaidank: Thank you… The invite worked and I get the list of my hubs from that channel page, but “enroll” doesn’t work. It just return back to the page with all hubs as “enroll” again. I tested to “unenroll” and “enroll” again in the other (884…) and that worked without problems. Any idea?
Same using the smartthings cli
This work:
smartthings edge:channels:enroll -C 884c23ca-3ef7-4187-899f-99c997cb3b46
This doesn’t:
smartthings edge:channels:enroll -C 551fb634-c607-45b4-b45f-be13a1040a7b
In case you would like some help with updates/or give me the right to make my own fork from your code I’m willing to help/create my own fork. My github username is the same as here (lvikstro) if you wan’t to invite there.
Hi @lvikstro
As you might have realised by now, I find it much easier to write code than navigate arcane development tools/environments.
The current code, including the addition to fingerprints.yml, are in my github: jaidank/SmartthingsEdge if you want to copy it for yourself.
I searched for some way to invite you but same comment as above.
Cheers, Aidan
Thank you very much, I now forked your repo and created my own channel and driver from your code. Re-added the SRT321 and now it got added with the driver. Now just to get it to actually work also, it is showing in smartthings and logcat showing output when I manually change on the thermostat, but the UI in smartthings doesn’t reflect it.
2023-03-05T15:25:58.481359904+00:00 TRACE Secure SRT321 Thermostat Received event with handler unnamed
2023-03-05T15:25:58.482595237+00:00 INFO Secure SRT321 Thermostat <ZwaveDevice: 2de9d871-ea35-4369-93d5-68ab68d2b584 [10] (Termostat)> received Z-Wave command: {args={precision=1, scale=“CELSIUS”, setpoint_type=“HEATING_1”, size=2, value=24.0}, cmd_class=“THERMOSTAT_SETPOINT”, cmd_id=“REPORT”, dst_channels={}, encap=“NONE”, payload=“\x01\x22\x00\xF0”, src_channel=0, version=1}
2023-03-05T15:25:58.567580570+00:00 TRACE Secure SRT321 Thermostat Found ZwaveDispatcher handler in secure_srt321_thermostat
2023-03-05T15:25:58.585327237+00:00 INFO Secure SRT321 Thermostat <ZwaveDevice: 2de9d871-ea35-4369-93d5-68ab68d2b584 [10] (Termostat)> emitting event: {“attribute_id”:“heatingSetpoint”,“capability_id”:“thermostatHeatingSetpoint”,“component_id”:“main”,“state”:{“unit”:“C”,“value”:24.0}}
2023-03-05T15:25:58.589829570+00:00 DEBUG Secure SRT321 Thermostat Secure SRT321 Thermostat device thread event handled
The other way i.e. changing in UI:
2023-03-05T15:27:19.558482439+00:00 TRACE Secure SRT321 Thermostat Received event with handler capability
2023-03-05T15:27:19.572631773+00:00 INFO Secure SRT321 Thermostat <ZwaveDevice: 2de9d871-ea35-4369-93d5-68ab68d2b584 [10] (Termostat)> received command: {“args”:{“setpoint”:23},“capability”:“thermostatHeatingSetpoint”,“command”:“setHeatingSetpoint”,“component”:“main”,“positional_args”:[23]}
2023-03-05T15:27:19.577985773+00:00 TRACE Secure SRT321 Thermostat Found CapabilityCommandDispatcher handler in secure_srt321_thermostat
2023-03-05T15:27:19.579171439+00:00 INFO Secure SRT321 Thermostat <ZwaveDevice: 2de9d871-ea35-4369-93d5-68ab68d2b584 [10] (Termostat)> emitting event: {“attribute_id”:“heatingSetpoint”,“capability_id”:“thermostatHeatingSetpoint”,“component_id”:“main”,“state”:{“unit”:“C”,“value”:23}}
2023-03-05T15:27:19.592371439+00:00 TRACE Secure SRT321 Thermostat Z-Wave command(85f57a46) queued for radio transmission: CC:Thermostat Setpoint, CID:0x01
2023-03-05T15:27:19.593426773+00:00 INFO Secure SRT321 Thermostat <ZwaveDevice: 2de9d871-ea35-4369-93d5-68ab68d2b584 [10] (Termostat)> sending Z-Wave command: {args={scale=“CELSIUS”, setpoint_type=“HEATING_1”, value=23}, cmd_class=“THERMOSTAT_SETPOINT”, cmd_id=“SET”, dst_channels={}, encap=“AUTO”, payload=“\x01\x01\x17”, src_channel=0, version=1}
2023-03-05T15:27:19.661864439+00:00 DEBUG Secure SRT321 Thermostat Secure SRT321 Thermostat device thread event handled
2023-03-05T15:27:23.762540441+00:00 TRACE Secure SRT321 Thermostat Z-Wave command(85f57a46) transmit status: TRANSMIT_COMPLETE_NO_ACK
But nothing seems to change on the display of the thermostat.
I set the “polling interval” to 1 now during testing
This driver is not perfect. I does take up to an hour to ‘settle in’.
It may be that yours is an updated version of mine, with subtle differences.
But, with the code you are in a position to debug it using the CLI
Good luck,
Aidan
Thank you very much… I’ll try to understand, debug and hopefully fix if there is something I can do something about…
When I added the association with my ssr303 (setting pin 1 to “on” and after getting the association setting back to “off”) it immediately took all my settings, so I’ll play around a bit with it and hopefully getting it to work reliably.
At the moment I have a vera with a 6 year old version of this running at the summer cabin and would like to switch them out to smartthings and this new one. So hopefully getting it to work reliably so I can switch out the old hardware.
Ahh,
If you compare Association groups between your model:
https://manual.zwave.eu/backend/make.php?lang=en&sku=SECESRT321-5&cert=%20ZC08-11010003
And my model:
https://manual.zwave.eu/backend/make.php?lang=en&sku=SEC_SRT321&cert=ZC10-16015001
Thermostat Set Point seems to have moved from 4 to 5 and Nodes to receive unsolicited Sensor Multilevel Reports is removed.
You have a bit of coding to do.