I’d like to try to reproduce this myself. Any idea what is driving the Celsius display? Is this a setting on your device? Or your locale?
I don’t think the Intermatic supports anything but Fahrenheit from what I can see.
Thanks for your help.
Could you post the “before” version of this method? I would like to see the specific change that was made. That said, it appears as though the correct value is being sent to the 653, but for some reason It’s not being accepted.
It would be nice to change/program the schedules and RPMs via smartthings or hubitat. If the remote ever goes out as it has for some, it would be nice to do everything we can via Smarthings/Hubitat. As i have both. There is also an issue with Smartthings and 953/653 if its paired with ver. 1 hub and ver. 2 hub where the entire hub needs to be reset to defaut to re-add it between the 2 versions of the hub. Not sure they fixed that bug but hesitant to retry that again.
FYI version 3.4 does not work with vera. You need 3.3 or earlier or 3.9+. Ill update how 3.9 work with ST. But it would be nice to do everything on Smarthings and Hubitat directly without the remote. I live in the Midwest of US where the weather changes dymatically and would be nice to be able to switch the schedule etc. I am sure it would also be helpful for other peope with vacation homes.
Certainly. Here is the GitHub link to the driver that Dan looked at:
https://raw.githubusercontent.com/infofiend/Osram_gSpots/master/devicetypes/info-fiend/osram-gardenspot-mini-rgb-aap-version.src/osram-gardenspot-mini-rgb-aap-version.groovy
It’s always dangerous for me to look at code, so take it with a grain of salt, but all I see changed is a couple of instances of state.level changed to state.levelValue
I hooked back up my heater to switch 5 on the controller. It works fine with the intermatic remote but doesn’t work with Smartthings. It will report the correct temp setting to Smartthings but it is unable to change the temp using Smartthings.
Sorry, I think I’m missing something here. How was your heater hooked up before? Do you also have an expansion module? If so, is the behavior different? This sounds very similar to the issue that @CAL7 is having. Strange, because I can set the temperature just fine and my heater turns on and off exactly as you would expect. But again, my heater is connected to the expansion module. In any case, I don’t see why the way that the heater is connected would have an impact on whether the Set point can be changed over ZWave.
Mine was always hooked up the same way i just reconnected it for the season. I rarely ever used it with smartthing because i couldnt get it to work with it on newer code versions. It think i got it to work a long time ago but havent since. Unless it was when i had ver. 3.4 vs 3.9. It works with the remote just fine. I am connected to chanel 5, and it works just fine with the intermatic remote just not smartthings.
New DTH seems to work great with my VSP system. Can you make the font bigger? I cant seem to read them clearly on my 5.5" phone. Does anyone know how to alert when pool pump is still running after certain time and when in certain mode?
Glad to hear it! I’ve looked a bit and could not find any way to change font style or size. If anyone has any info please point me to it.
Is there anyway to fix my issue with the heater not working?
@magicshot, the symptoms you describe are the same as @CAL7. Turns out we live pretty close to each other so I am planning to visit him and capture some live ZWave traces to see what is different between the remote and SmartThings. We won’t be able to do that until next week so we’ll have to hold for now.
In the mean time, just to make sure we are looking at the same thing, if you could set your debug level to Low and capture a trace of changing the temperature, that might help.
Thank-you.
Do you recall what broke for Vera on v3.4? Was it a single function (like setting the temperature)? Or was it a broader failure? Since my heater is working, I remain optimistic I can overcome whatever is preventing this from working for you and @CAL7.
Hi,
So everything on my phone is in Celsius (I’m from Canada), by the main driver for the Celsius v. Fahrenheit is from the Smartthings internal settings.
To reproduce the problem, you can change the temperature scale:
Smarthings app > Settings > Temperature Scale > °C
When I open the device
Changing temperature setpoint pool:
After changing the setpoint:
Exiting and returning to the device directly after this:
Hitting refresh:
After that in the main screen:
After one refresh cycle:
@cslee, You can do it with a webcore piston, although there may be a simpler way.
For the text, I removed manually the icons in the handler, and changed the width and height, which make the text much bigger :
icon: "https://raw.githubusercontent.com/KeithR26/Intermatic-PE653/master/[...].png",
I don’t think smartthing will let you edit the font, other than changing the tile size.
@tijonx, Thanks so much for all the information and samples. I’ve already changed my settings and I’m seeing the same behavior. I’ll keep playing with it later today. Question, do you have a 953 remote? And what temperature scale does it display?Celsius? Or Fahrenheit?I haven’t seen a configuration setting in the remote to select temperature scale.
As for the font, I may just create new icons with large font text embedded in the icon. Sounds like this may be a common complaint.
The remote is in Fahrenheit and cannot be changed to Celsius as far as I know.
Maybe there a secret settings. I bought it from a Canadian supplier
This is a long shot, but here is something you could try in the mean time. In the function “setPoolSetpointInternal” and “setSpaSetpointInternal”, change the line:
deviceScale = 0 To
deviceScale = 1.
This does not work on my system but my firmware is backwards from the ZWave standard where 0 means Celsius and 1 means Fahrenheit. The 653 does not support Celsius, but my firmware only accepts 0. It has to be a defect in the firmware. Maybe something in your setup requires the opposite. Who knows. Worth a shot anyway.
Here is the debug when i change the temp:
60e8f97e-ec1a-4729-b73e-2c13ff502b80 10:53:30 PM: debug ManufacturerProprietary event, [1]:40 [4]:84 payload: 05 40 02 02 84 FF 10 02 00 00 00 01 49 49 FF 09 0B 01 00 00 04 03 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60e8f97e-ec1a-4729-b73e-2c13ff502b80 10:53:29 PM: debug ManufacturerProprietary event, [1]:40 [4]:87 payload: 05 40 02 02 87 FF 10 02 00 00 00 07 00 00 00 00 00 00 04 00 00 00 00 00 09 0B 01 01 00 00 20 00 00 00 00 00 00 00 00 00
60e8f97e-ec1a-4729-b73e-2c13ff502b80 10:53:28 PM: debug <<<<< rspFlg=true dly:1000/1000
<<<<< Event: [name:clock, value:09:11, displayed:false, descriptionText:PE653 Clock: 09:11, isStateChange:true, linkText:_Pool Controller]
60e8f97e-ec1a-4729-b73e-2c13ff502b80 10:53:28 PM: debug ManufacturerProprietary event, [1]:40 [4]:84 payload: 05 40 02 02 84 FF 10 02 00 00 00 01 49 49 FF 09 0B 01 00 00 04 03 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60e8f97e-ec1a-4729-b73e-2c13ff502b80 10:53:28 PM: debug >>>>> ThermostatSetpointReport(precision: 0, reserved01: 0, scale: 1, scaledValue: 55, setpointType: 1, size: 1, value: [55]) - description:zw device: 32, command: 4303, payload: 01 09 37
60e8f97e-ec1a-4729-b73e-2c13ff502b80 10:53:27 PM: debug ManufacturerProprietary event, [1]:40 [4]:87 payload: 05 40 02 02 87 FF 10 02 00 00 00 07 00 00 00 00 00 00 04 00 00 00 00 00 09 0B 01 01 00 00 20 00 00 00 00 00 00 00 00 00
60e8f97e-ec1a-4729-b73e-2c13ff502b80 10:53:26 PM: debug >>>>> ThermostatSetpointReport(precision: 0, reserved01: 0, scale: 1, scaledValue: 55, setpointType: 1, size: 1, value: [55]) - description:zw device: 32, command: 4303, payload: 01 09 37
60e8f97e-ec1a-4729-b73e-2c13ff502b80 10:53:25 PM: debug <<<<< rspFlg=false dly:1000/1000
<<<<< Dev cmd: ThermostatSetpointSet(precision: 0, reserved01: 0, scale: 0, scaledValue: 62, setpointType: 1, size: 1, value: [62]) --> 430101013E, delay 1000
<<<<< Dev cmd: ThermostatSetpointGet(reserved01: 0, setpointType: 1) --> 430201, delay 1000
<<<<< HubAction: 910005400102870301, delay 1000
<<<<< HubAction: 910005400101830101
60e8f97e-ec1a-4729-b73e-2c13ff502b80 10:53:25 PM: debug setPoolSetpointInternal degrees=62.0
I don’t think this is related to the new Device Handler. I’m just curious if anyone else has run into this or knows the cause.
But my PE653 seems to have forgot its schedule (done through PE953). It ran fine for a couple weeks. I’m currently remote on vacation and can luckily manually run the pump with SmartThings.