My version looks like yours (#1) and yes, I’m able to control the temperature.
However, as I mentioned in my post, the VSP buttons and switches do not work. They just hang saying “Turning On” until I do something to change the screen. Any thoughts or suggestions? Thanks much!
Just a quick update, the SmartApp is working VERY Good now.
The PE653 decided to run it’s internal schedule today. And I was notified it did so with this SmartApp SMS Monitoring. Also a cool benifit is, if I have a Power Failure when the power is restored I get Text Messages if it came back up in a different state (which it usually does). So just using it to monitor things is really nice.
I added Install Instructions to the header of the source code (it’s similar to installing the DTH).
So it does 3 things now:
Turns your PE653 Circuit buttons into a “Remote” for your IntelliFlo VSP Pump Speeds (no PE953 or Phone needed)
Note: When PE653 is connected through RS485 to an IntelliFlo both the PE653 becomes useless (for the pump) and the pump Control Panel is also disabled, so you have no physical control over the pump (really dumb). This gives you that physical local control back.
You can schedule Circuits or Speeds (with optional SMS Text Feedback on each event).
Monitor via SMS Text any Circuit or Speed change.
@jawzz, thanks for the update. Please set Debug=Low in the settings and then capture two logs: one for turning on a switch circuit and another selecting a VSP speed, then post here. I presume these functions work fine from your remote?
Yes, they work from my remote just fine.
Here is the log for the circuit turn on (actually off in this case):
c22a5e8a-68d3-4f3b-9aaa-54dd50f99707 7:49:40 AM: debug ManufacturerProprietary event, [1]:40 [4]:84 payload: 05 40 02 02 84 00 10 02 04 00 02 01 51 4F 00 07 2E 14 00 00 00 03 04 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c22a5e8a-68d3-4f3b-9aaa-54dd50f99707 7:49:40 AM: debug ManufacturerProprietary event, [1]:40 [4]:84 payload: 05 40 02 02 84 00 10 02 04 00 02 01 51 4F 00 07 2E 14 00 00 00 03 04 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c22a5e8a-68d3-4f3b-9aaa-54dd50f99707 7:49:37 AM: debug <<<<< rspFlg=true dly:1000/1000
<<<<< Event: "off" to child: 04-ep4:Water Feature
<<<<< Event: [name:switch4, value:off, isStateChange:true, displayed:true, descriptionText:(switch4 set to off), linkText:Pool Controller]
<<<<< Event: [name:clock, value:07:46, displayed:false, descriptionText:PE653 Clock: 07:46, isStateChange:true, linkText:Pool Controller]
c22a5e8a-68d3-4f3b-9aaa-54dd50f99707 7:49:37 AM: debug ManufacturerProprietary event, [1]:40 [4]:84 payload: 05 40 02 02 84 00 10 02 04 00 02 01 51 4F 00 07 2E 14 00 00 00 03 04 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c22a5e8a-68d3-4f3b-9aaa-54dd50f99707 7:49:37 AM: debug ManufacturerProprietary event, [1]:40 [4]:84 payload: 05 40 02 02 84 00 10 02 04 00 02 01 51 4F 00 07 2E 14 00 00 00 03 04 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c22a5e8a-68d3-4f3b-9aaa-54dd50f99707 7:49:37 AM: debug <<<<< rspFlg=false dly:1000/1000
<<<<< Dev cmd: MultiInstanceCmdEncap(command: 1, commandClass: 37, instance: 4, parameter: [0]) --> 600604250100, delay 1000
<<<<< HubAction: 910005400102870301, delay 1000
<<<<< HubAction: 910005400101830101
And here is the log for the VSP:
c22a5e8a-68d3-4f3b-9aaa-54dd50f99707 7:47:54 AM: debug ManufacturerProprietary event, [1]:40 [4]:84 payload: 05 40 02 02 84 00 10 02 0C 00 02 01 51 4F 00 07 2D 14 00 00 00 03 04 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c22a5e8a-68d3-4f3b-9aaa-54dd50f99707 7:47:54 AM: debug ManufacturerProprietary event, [1]:40 [4]:84 payload: 05 40 02 02 84 00 10 02 0C 00 02 01 51 4F 00 07 2D 14 00 00 00 03 04 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c22a5e8a-68d3-4f3b-9aaa-54dd50f99707 7:47:52 AM: debug ManufacturerProprietary event, [1]:40 [4]:87 payload: 05 40 02 02 87 00 10 02 01 01 02 07 03 04 00 02 00 10 04 00 04 00 05 20 07 2D 14 01 00 00 20 00 00 00 00 00 00 00 00 00
c22a5e8a-68d3-4f3b-9aaa-54dd50f99707 7:47:52 AM: debug ManufacturerProprietary event, [1]:40 [4]:87 payload: 05 40 02 02 87 00 10 02 01 01 02 07 03 04 00 02 00 10 04 00 04 00 05 20 07 2D 14 01 00 00 20 00 00 00 00 00 00 00 00 00
c22a5e8a-68d3-4f3b-9aaa-54dd50f99707 7:47:49 AM: debug <<<<< rspFlg=false dly:1000/1000
<<<<< Dev cmd: MultiInstanceCmdEncap(command: 1, commandClass: 37, instance: 19, parameter: [255]) --> 6006132501FF, delay 1000
<<<<< HubAction: 910005400102870301, delay 1000
<<<<< HubAction: 910005400101830101
Note that there is a lot of variability in the number of ManufactureProprietaryEvent entries; I’ve seen anywhere from 2-6.
Hope this helps.
@jawzz, thanks for the logs. For the SW4->off case are you sure the UI button did not turn to “off”? The logs show an event being sent for SW4 which should changed it from Turning Off to Off. everything for this one looks right.
For the VSP I will have to look deeper. Please double check to see that there were no more log entries above the top one as there should have been a similar pair of events.i will also decide the Manufacturers message to see if it shows the VSP state change.
You should also see these events if you select the “events” tab for the DTH in the mobile App.
Yes, I also note significant variation in the number of the manufacturers messages, but this does not seem to have any negative effects.
I have published the latest update to the DTH. This contains the following updates:
Please give it a try and post any feedback.
I just installed my PE653 but was not able to pair it. It is 3.4 and the hub is v2. I clicked on “Add a Thing” in the app and then hit the include button on the device and it blinked a couple times but nothing happened on my ST. The PE653 is about 80 feet from my house but there is a Z-Wave bulb registered to my network that is only about 20 feet away.
Any ideas for diagnosing this?
To make sure my installation was fine, I tried pairing the PE953 to PE653 and it paired fine and it seemed to function properly.
Hi mswlogo, I just saw your earlier posts on range issues. I am unable to pair my PE653 that is about 80 ft from the house (about 100 ft from ST). Is the range extender still the best way to make this work? If so, then why did you disconnect yours? Thanks.
See a post I made around Jun 29 post 609 that I did for pairing. I posted a procedure from Vera forums that helped pair everything. It’s a bit tricky.
Initially I moved the hub to the garage which was closest to PE653 and that’s when I paired it. Later I replaced it with an extender and moved hub back to living room. It was working but I had little glitches.
Then I remoted the antenna on 653 and moved hub to bedroom that was almost as close as garage and removed extender. Now it’s working much better. Not sure what change really improved it.
Are the “schedules” SmartThjng schedules or the same Schedules PE953 creates?
Yes, for the first time this will allow a SmartApp to configure the schedules in the 653 ( when complete).
I have never experienced the issues you have described with 653 schedules. Mine are very reliable and never forget. I wonder if you might have a hardware issue?
Anyone else having these issues?
Reporting on v3.04:
The logic to determine the version and to set temp must be working because that problem has gone away.
Waiting on the solar temp to hit 129° so I can confirm the 7-bit overflow fix. ETA 2pm unless the storms roll in.
I’m interested in the programmatic schedule setting. My use-case would be to automatically set the pump schedules based on season. I have never trusted ST to control the pump (to answer the other question: schedules once set in the PE653 have never failed me); but I do use ST to manage the light and cleaner, waterfall valves. The infrequent use of ST to change the PE653 schedules without needing the PE953 would be helpful and my distrust of ST is alleviated since I can confirm the schedule change.
@KeithR Oops! Temp went negative once it overflowed. No change in appearance from v3.03.
Weird, I even tried forcing mine negative to pre-test. Oh Well. Could you grab a log when you tap the “Pool temp” (the big one) please? You should see a couple ManufacturerProprietary messages and one or more “events”. If you don;t see an event for either SolarTemp or FreezeTemp just wait a few minutes until the temp changes. Thanks!
The circuit switches are working fine - they function correctly and turn to off (or on). I regenerated and rechecked the VSP logs and there are no additional entries. Also, I looked at the Recently tab and don’t see anything for the VSP actions, whereas I do for the circuit events.
mswlogo, thanks. It appears there are three options:
It seems solutions (1) and (3) require Cat5 cable (either for ST or for the antenna). Would I just run 100ft of Cat5 from one position to the other? Thanks.
The Schedule in PE653 has been stable for past 3 days. Not sure what’s going on. But it always goes a little nuts if I touch ANYTHING. I’m hoping with SmartThings network more stable maybe that will be stable too. Everything has been good for past 3 days.
I updated to latest 3.04 08/09/2018, I have no heater. When it’s time to heat, it’s time to close the pool ;).
How does the Color Light thing work? I have one of those LED lights that if you toggle power (or use the remote) it changes mode/color, but it’s some “off” brand.
I set the Circuit the Light is On (Cir 4). And I click the Color Button on the Main Panel and the Slider pops up but there is no “Ok” button. Just a X to close it. When I close it, it doesn’t appear to have saved the slider value. If I open it again it’s always on 0. On Android it shows a 0 and iPhone there is no number showing on the main screen.
That’s great news on updating schedule within PE653.
HI, noob to SmartThings (havent bought a hub yet but am enticed by the new WiFi Mesh + Hub solution). Long time Vera (Since V1). I was a kickstarter backer for SmartThings and have the original hub but never moved off of Vera… Anyway the one device that I want to make sure is working is the Multiwave (Pe653). Seems like from the thread it is but wasn’t clear on the Intermatic Firmware version I need. I have 3.7 running on vera with all devices working, including Variable control for Pentair pumps and support for the 5043… I only have a single speed pump plus heater that I really need to work, the other is not needed for my current setup. So stable and take the plunge?
@KeithR Sorry for the delay. It had cooled down last night when I got home, so I waited until it warmed today. The app is showing -128 , although when I hit the Pool Temp, it briefly flashed +127 then back to -128.
I see the logs indicated v3.03, so I double-checked the DTH and it is indeed 3.04.
1:24:25 PM: debug <<<<< rspFlg=true dly:1000/1000
<<<<< Event: [name:airTempSolar, value:-128, unit:F, displayed:false, isStateChange:true, linkText:Pool PE653, descriptionText:Pool PE653 air temp solar is -128°F]
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:24:25 PM: debug ManufacturerProprietary event, [1]:40 [4]:84 payload: 05 40 02 02 84 02 10 02 09 00 02 01 59 5C 80 0D 14 14 00 00 00 03 04 01 0E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:24:24 PM: debug <<<<< rspFlg=true dly:1000/1000
<<<<< Event: [name:airTempSolar, value:127, unit:F, displayed:false, isStateChange:true, linkText:Pool PE653, descriptionText:Pool PE653 air temp solar is 127°F]
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:24:24 PM: debug ManufacturerProprietary event, [1]:40 [4]:84 payload: 05 40 02 02 84 02 10 02 09 00 02 01 59 5C 7F 0D 14 14 00 00 00 03 04 01 0E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:24:23 PM: debug ManufacturerProprietary event, [1]:40 [4]:87 payload: 05 40 02 02 87 02 10 02 01 01 02 07 03 04 00 46 01 13 04 00 04 00 00 25 0D 14 14 01 00 10 21 00 00 00 00 00 00 00 00 00
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:24:22 PM: debug ManufacturerProprietary event, [1]:40 [4]:87 payload: 05 40 02 02 87 02 10 02 01 01 02 07 03 04 00 46 01 13 04 00 04 00 00 25 0D 14 14 01 00 10 21 00 00 00 00 00 00 00 00 00
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:24:22 PM: warn CME: CAN'T FIND CHILD DEVICE: 24-ep7:swVSP1
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:24:22 PM: debug zwaveEventCmdEncap cmd=MultiInstanceCmdEncap(command: 3, commandClass: 37, instance: 16, parameter: [0])
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:24:22 PM: debug multiinstancev1.MultiInstanceCmdEncap cmd=MultiInstanceCmdEncap(command: 3, commandClass: 37, instance: 16, parameter: [0])
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:24:22 PM: debug >>>>> MultiInstanceCmdEncap(command: 3, commandClass: 37, instance: 16, parameter: [0]) - description:zw device: 24, command: 6006, payload: 10 25 03 00
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:24:21 PM: debug <<<<< rspFlg=false dly:1000/1000
<<<<< Dev cmd: MultiInstanceCmdEncap(command: 2, commandClass: 37, instance: 16, parameter: []) --> 6006102502, delay 1000
<<<<< HubAction: 910005400102870301, delay 1000
<<<<< HubAction: 910005400101830101
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:24:21 PM: debug +++++ getChanState(16)
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:24:21 PM: debug +++++ getTestCmds
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:24:20 PM: debug ..... ConfigurationReport - got parameter=19
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:24:20 PM: debug >>>>> ConfigurationReport(configurationValue: [211, 2, 253, 2], parameterNumber: 19, reserved11: 0, scaledConfigurationValue: -754778878, size: 4) - description:zw device: 24, command: 7006, payload: 13 04 D3 02 FD 02
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:24:19 PM: debug <<<<< rspFlg=true dly:1000/1000
<<<<< Event: [value:1, name:temperatureOffsets, displayed:true, isStateChange:false, linkText:Pool PE653, descriptionText:Pool PE653 temperature offsets is 1]
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:24:19 PM: debug >>>>> ConfigurationReport(configurationValue: [1, 1, 0, 0], parameterNumber: 3, reserved11: 0, scaledConfigurationValue: 16842752, size: 4) - description:zw device: 24, command: 7006, payload: 03 04 01 01 00 00
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:24:18 PM: debug <<<<< rspFlg=true dly:1000/1000
<<<<< Event: [value:0, name:firemanTimeout, displayed:true, isStateChange:false, linkText:Pool PE653, descriptionText:Pool PE653 fireman timeout is 0]
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:24:18 PM: debug >>>>> ConfigurationReport(configurationValue: [0, 0], parameterNumber: 2, reserved11: 0, scaledConfigurationValue: 0, size: 2) - description:zw device: 24, command: 7006, payload: 02 02 00 00
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:24:17 PM: debug <<<<< rspFlg=true dly:1000/1000
<<<<< Event: [value:1, name:operationMode, displayed:true, isStateChange:false, linkText:Pool PE653, descriptionText:Pool PE653 operation mode is 1]
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:24:17 PM: debug >>>>> ConfigurationReport(configurationValue: [1, 2], parameterNumber: 1, reserved11: 0, scaledConfigurationValue: 258, size: 2) - description:zw device: 24, command: 7006, payload: 01 02 01 02
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:24:16 PM: debug ManufacturerSpecificReport !!!
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:24:16 PM: debug >>>>> ManufacturerSpecificReport(manufacturerId: 5, manufacturerName: Intermatic, productId: 1619, productTypeId: 20549) - description:zw device: 24, command: 7205, payload: 00 05 50 45 06 53
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:24:15 PM: debug >>>>> VersionReport(applicationSubVersion: 4, applicationVersion: 3, zWaveLibraryType: 6, zWaveProtocolSubVersion: 78, zWaveProtocolVersion: 2) - description:zw device: 24, command: 8612, payload: 06 02 4E 03 04
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:24:14 PM: debug >>>>> ThermostatSetpointReport(precision: 0, reserved01: 0, scale: 1, scaledValue: 96, setpointType: 7, size: 1, value: [96]) - description:zw device: 24, command: 4303, payload: 07 09 60
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:24:13 PM: debug >>>>> ThermostatSetpointReport(precision: 0, reserved01: 0, scale: 1, scaledValue: 96, setpointType: 1, size: 1, value: [96]) - description:zw device: 24, command: 4303, payload: 01 09 60
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:24:13 PM: debug <<<<< rspFlg=false dly:1000/1000
<<<<< Dev cmd: ThermostatSetpointGet(reserved01: 0, setpointType: 1) --> 430201, delay 1000
<<<<< Dev cmd: ThermostatSetpointGet(reserved01: 0, setpointType: 7) --> 430207, delay 1000
<<<<< Dev cmd: VersionGet() --> 8611, delay 1000
<<<<< Dev cmd: ManufacturerSpecificGet() --> 7204, delay 1000
<<<<< Dev cmd: ConfigurationGet(parameterNumber: 1) --> 700501, delay 1000
<<<<< Dev cmd: ConfigurationGet(parameterNumber: 2) --> 700502, delay 1000
<<<<< Dev cmd: ConfigurationGet(parameterNumber: 3) --> 700503, delay 1000
<<<<< Dev cmd: ConfigurationGet(parameterNumber: 19) --> 700513, delay 1000
<<<<< HubAction: 910005400102870301, delay 1000
<<<<< HubAction: 910005400101830101
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:24:13 PM: debug +++++ refresh() DTH:Ver 3.03 state.Versioninfo=Versions: Firmware v3.4 DTH: Ver 3.03 zWaveLibraryType: 6 zWaveProtocol: v2.78
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:24:07 PM: debug <<<<< rspFlg=true dly:1000/1000
<<<<< Event: [name:clock, value:13:20, displayed:false, descriptionText:PE653 Clock: 13:20, isStateChange:true, linkText:Pool PE653]
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:24:07 PM: debug ManufacturerProprietary event, [1]:40 [4]:84 payload: 05 40 02 02 84 02 10 02 09 00 02 01 59 5C 80 0D 14 14 00 00 00 03 04 01 0E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:24:04 PM: debug ManufacturerProprietary event, [1]:40 [4]:87 payload: 05 40 02 02 87 02 10 02 01 01 02 07 03 04 00 46 01 13 04 00 04 00 00 25 0D 14 14 01 00 10 21 00 00 00 00 00 00 00 00 00
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:24:01 PM: warn CME: CAN'T FIND CHILD DEVICE: 24-ep7:swVSP1
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:24:01 PM: debug zwaveEventCmdEncap cmd=MultiInstanceCmdEncap(command: 3, commandClass: 37, instance: 16, parameter: [0])
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:24:01 PM: debug multiinstancev1.MultiInstanceCmdEncap cmd=MultiInstanceCmdEncap(command: 3, commandClass: 37, instance: 16, parameter: [0])
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:24:01 PM: debug >>>>> MultiInstanceCmdEncap(command: 3, commandClass: 37, instance: 16, parameter: [0]) - description:zw device: 24, command: 6006, payload: 10 25 03 00
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:24:01 PM: debug >>>>> MultiInstanceCmdEncap(command: 3, commandClass: 37, instance: 16, parameter: [0]) - description:zw device: 24, command: 6006, payload: 10 25 03 00
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:23:59 PM: debug <<<<< rspFlg=false dly:1000/1000
<<<<< Dev cmd: MultiInstanceCmdEncap(command: 2, commandClass: 37, instance: 16, parameter: []) --> 6006102502, delay 1000
<<<<< HubAction: 910005400102870301, delay 1000
<<<<< HubAction: 910005400101830101
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:23:59 PM: debug +++++ getChanState(16)
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:23:59 PM: debug +++++ getTestCmds
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:23:29 PM: debug <<<<< rspFlg=true dly:1000/1000
<<<<< Event: [name:airTempFreeze, value:92, unit:F, displayed:false, isStateChange:true, linkText:Pool PE653, descriptionText:Pool PE653 air temp freeze is 92°F]
<<<<< Event: [name:airTempSolar, value:-128, unit:F, displayed:false, isStateChange:true, linkText:Pool PE653, descriptionText:Pool PE653 air temp solar is -128°F]
<<<<< Event: [name:clock, value:13:19, displayed:false, descriptionText:PE653 Clock: 13:19, isStateChange:true, linkText:Pool PE653]
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:23:29 PM: debug ManufacturerProprietary event, [1]:40 [4]:84 payload: 05 40 02 02 84 02 10 02 09 00 02 01 59 5C 80 0D 13 14 00 00 00 03 04 01 0E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:23:28 PM: debug ManufacturerProprietary event, [1]:40 [4]:87 payload: 05 40 02 02 87 02 10 02 01 01 02 07 03 04 00 46 01 13 04 00 04 00 00 25 0D 13 14 01 00 10 21 00 00 00 00 00 00 00 00 00
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:23:27 PM: debug ..... ConfigurationReport - got parameter=19
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:23:27 PM: debug >>>>> ConfigurationReport(configurationValue: [211, 2, 253, 2], parameterNumber: 19, reserved11: 0, scaledConfigurationValue: -754778878, size: 4) - description:zw device: 24, command: 7006, payload: 13 04 D3 02 FD 02
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:23:25 PM: debug <<<<< rspFlg=true dly:1000/1000
<<<<< Event: [value:1, name:temperatureOffsets, displayed:true, isStateChange:false, linkText:Pool PE653, descriptionText:Pool PE653 temperature offsets is 1]
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:23:25 PM: debug >>>>> ConfigurationReport(configurationValue: [1, 1, 0, 0], parameterNumber: 3, reserved11: 0, scaledConfigurationValue: 16842752, size: 4) - description:zw device: 24, command: 7006, payload: 03 04 01 01 00 00
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:23:25 PM: debug <<<<< rspFlg=true dly:1000/1000
<<<<< Event: [value:0, name:firemanTimeout, displayed:true, isStateChange:false, linkText:Pool PE653, descriptionText:Pool PE653 fireman timeout is 0]
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:23:25 PM: debug >>>>> ConfigurationReport(configurationValue: [0, 0], parameterNumber: 2, reserved11: 0, scaledConfigurationValue: 0, size: 2) - description:zw device: 24, command: 7006, payload: 02 02 00 00
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:23:23 PM: debug <<<<< rspFlg=true dly:1000/1000
<<<<< Event: [value:1, name:operationMode, displayed:true, isStateChange:false, linkText:Pool PE653, descriptionText:Pool PE653 operation mode is 1]
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:23:23 PM: debug >>>>> ConfigurationReport(configurationValue: [1, 2], parameterNumber: 1, reserved11: 0, scaledConfigurationValue: 258, size: 2) - description:zw device: 24, command: 7006, payload: 01 02 01 02
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:23:22 PM: debug ManufacturerSpecificReport !!!
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:23:22 PM: debug >>>>> ManufacturerSpecificReport(manufacturerId: 5, manufacturerName: Intermatic, productId: 1619, productTypeId: 20549) - description:zw device: 24, command: 7205, payload: 00 05 50 45 06 53
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:23:20 PM: debug >>>>> VersionReport(applicationSubVersion: 4, applicationVersion: 3, zWaveLibraryType: 6, zWaveProtocolSubVersion: 78, zWaveProtocolVersion: 2) - description:zw device: 24, command: 8612, payload: 06 02 4E 03 04
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:23:19 PM: debug >>>>> ThermostatSetpointReport(precision: 0, reserved01: 0, scale: 1, scaledValue: 96, setpointType: 7, size: 1, value: [96]) - description:zw device: 24, command: 4303, payload: 07 09 60
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:23:18 PM: debug >>>>> ThermostatSetpointReport(precision: 0, reserved01: 0, scale: 1, scaledValue: 96, setpointType: 1, size: 1, value: [96]) - description:zw device: 24, command: 4303, payload: 01 09 60
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:23:17 PM: debug <<<<< rspFlg=false dly:1000/1000
<<<<< Dev cmd: ThermostatSetpointGet(reserved01: 0, setpointType: 1) --> 430201, delay 1000
<<<<< Dev cmd: ThermostatSetpointGet(reserved01: 0, setpointType: 7) --> 430207, delay 1000
<<<<< Dev cmd: VersionGet() --> 8611, delay 1000
<<<<< Dev cmd: ManufacturerSpecificGet() --> 7204, delay 1000
<<<<< Dev cmd: ConfigurationGet(parameterNumber: 1) --> 700501, delay 1000
<<<<< Dev cmd: ConfigurationGet(parameterNumber: 2) --> 700502, delay 1000
<<<<< Dev cmd: ConfigurationGet(parameterNumber: 3) --> 700503, delay 1000
<<<<< Dev cmd: ConfigurationGet(parameterNumber: 19) --> 700513, delay 1000
<<<<< HubAction: 910005400102870301, delay 1000
<<<<< HubAction: 910005400101830101
7c7d52be-86ac-4e2f-8e53-59210d4566c5 1:23:17 PM: debug +++++ refresh() DTH:Ver 3.03 state.Versioninfo=Versions: Firmware v3.4 DTH: Ver 3.03 zWaveLibraryType: 6 zWaveProtocol: v2.78 Charles, I double checked the “version” string and the new code is definitely 3.04, so since the logs show 3.03, I can only conclude that you may have missed a step. Are you sure you remembered to “publish” after saving? Please publish again and retry.