Z-Wave Multi Channel (PE653)

dbeckr50 · June 24, 2020, 7:49pm

I do have and use a PE953. I don't have a heater and don't use circuit 5. Logs when i clicked save preferences. I currently set my schedule with rule machine. Im not sure if the following is what you wanted. I could not find an "updated" button in the commands section so I clicked "quick get test commands" and got these logs.
2020-06-24 02:46:11.804 pm debug<<<<< rspFlg=true dly:1000/1000 <<<<< Event: [name:temperature, value:98, unit:F, displayed:true, isStateChange:true] <<<<< Event: [name:airTempFreeze, value:0, unit:F, displayed:true, isStateChange:true] <<<<< Event: [name:airTempSolar, value:0, unit:F, displayed:true, isStateChange:true] <<<<< Event: [name:clock, value:14:47, displayed:false, descriptionText:PE653 Clock: 14:47]

dev:692020-06-24 02:46:11.800 pm debug Event necessary. name:clock evt: "14:47" ==> dev:(null)

dev:692020-06-24 02:46:11.797 pm trace - 8: Map: [name:clock, value:14:47, displayed:false, descriptionText:PE653 Clock: 14:47]

dev:692020-06-24 02:46:11.794 pm trace - l -> [name:clock, value:14:47, displayed:false, descriptionText:PE653 Clock: 14:47]

dev:692020-06-24 02:46:11.791 pm debug Event necessary. name:airTempSolar evt: "0" ==> dev:(null)

dev:692020-06-24 02:46:11.788 pm trace - 7: Map: [name:airTempSolar, value:0, unit:F, displayed:true, isStateChange:true]

dev:692020-06-24 02:46:11.785 pm trace - l -> [name:airTempSolar, value:0, unit:F, displayed:true, isStateChange:true]

dev:692020-06-24 02:46:11.782 pm debug Event necessary. name:airTempFreeze evt: "0" ==> dev:(null)

dev:692020-06-24 02:46:11.779 pm trace - 6: Map: [name:airTempFreeze, value:0, unit:F, displayed:true, isStateChange:true]

dev:692020-06-24 02:46:11.776 pm trace - l -> [name:airTempFreeze, value:0, unit:F, displayed:true, isStateChange:true]

dev:692020-06-24 02:46:11.773 pm debug Event necessary. name:temperature evt: "98" ==> dev:(99)

dev:692020-06-24 02:46:11.769 pm trace - 5: Map: [name:temperature, value:98, unit:F, displayed:true, isStateChange:true]

dev:692020-06-24 02:46:11.766 pm trace - l -> [name:temperature, value:98, unit:F, displayed:true, isStateChange:true]

dev:692020-06-24 02:46:11.761 pm trace - 4: Map: [name:switch5, value:off, isStateChange:true, displayed:true, descriptionText:(switch5 set to off)]

dev:692020-06-24 02:46:11.759 pm trace - l -> [name:switch5, value:off, isStateChange:true, displayed:true, descriptionText:(switch5 set to off)]

dev:692020-06-24 02:46:11.755 pm trace - 3: Map: [name:switch4, value:off, isStateChange:true, displayed:true, descriptionText:(switch4 set to off)]

dev:692020-06-24 02:46:11.752 pm trace - l -> [name:switch4, value:off, isStateChange:true, displayed:true, descriptionText:(switch4 set to off)]

dev:692020-06-24 02:46:11.749 pm trace - 2: Map: [name:switch3, value:off, isStateChange:true, displayed:true, descriptionText:(switch3 set to off)]

dev:692020-06-24 02:46:11.747 pm trace - l -> [name:switch3, value:off, isStateChange:true, displayed:true, descriptionText:(switch3 set to off)]

dev:692020-06-24 02:46:11.744 pm trace - 1: Map: [name:switch2, value:off, isStateChange:true, displayed:true, descriptionText:(switch2 set to off)]

dev:692020-06-24 02:46:11.742 pm trace - l -> [name:switch2, value:off, isStateChange:true, displayed:true, descriptionText:(switch2 set to off)]

dev:692020-06-24 02:46:11.724 pm trace - 0: Map: [name:switch1, value:off, isStateChange:true, displayed:true, descriptionText:(switch1 set to off)]

dev:692020-06-24 02:46:11.721 pm trace - l -> [name:switch1, value:off, isStateChange:true, displayed:true, descriptionText:(switch1 set to off)]

dev:692020-06-24 02:46:11.718 pm debug+++++ delayBetweenLog parm[9] dly=1000 responseFlg=true

dev:692020-06-24 02:46:11.695 pm warnCME: CAN'T FIND CHILD DEVICE: 08-ep5:switch5

dev:692020-06-24 02:46:11.692 pm debug----- createMultipleEvents: devObj = null

dev:692020-06-24 02:46:11.687 pm warnCME: CAN'T FIND CHILD DEVICE: 08-ep4:switch4

dev:692020-06-24 02:46:11.684 pm debug----- createMultipleEvents: devObj = null

dev:692020-06-24 02:46:11.680 pm warnCME: CAN'T FIND CHILD DEVICE: 08-ep3:switch3

dev:692020-06-24 02:46:11.677 pm debug----- createMultipleEvents: devObj = null

dev:692020-06-24 02:46:11.673 pm warnCME: CAN'T FIND CHILD DEVICE: 08-ep2:switch2

dev:692020-06-24 02:46:11.670 pm debug----- createMultipleEvents: devObj = null

dev:692020-06-24 02:46:11.667 pm warnCME: CAN'T FIND CHILD DEVICE: 08-ep1:switch1

dev:692020-06-24 02:46:11.663 pm debug----- createMultipleEvents: devObj = null

dev:692020-06-24 02:46:11.653 pm debugpayload for switches is 0

dev:692020-06-24 02:46:11.650 pm debug+++++ process84Event payload: [5, 64, 2, 2, -124, -1, 16, 2, 0, 0, 0, 1, 98, 0, 0, 14, 47, 0, 0, 0, 0, 3, 3, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]

dev:692020-06-24 02:46:11.644 pm debug+++++ ManufacturerProprietary event, [1]:40 [4]:84 payload: 05 40 02 02 84 FF 10 02 00 00 00 01 62 00 00 0E 2F 00 00 00 00 03 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

dev:692020-06-24 02:46:09.632 pm errorjava.lang.NullPointerException: Cannot invoke method toJson() on null object on line 888 (parse)

dev:692020-06-24 02:46:09.622 pm debugConfigurationReport for Schedule: ep:1 sch=3 lst=null schLst=[1, null, null, null]

dev:692020-06-24 02:46:06.624 pm errorjava.lang.NullPointerException: Cannot invoke method toJson() on null object on line 888 (parse)

dev:692020-06-24 02:46:06.602 pm debugConfigurationReport for Schedule: ep:1 sch=2 lst=null schLst=[1, null, null]

dev:692020-06-24 02:46:03.633 pm errorjava.lang.NullPointerException: Cannot invoke method toJson() on null object on line 888 (parse)

dev:692020-06-24 02:46:03.617 pm debugConfigurationReport for Schedule: ep:1 sch=1 lst=null schLst=[1, null]

dev:692020-06-24 02:46:03.499 pm debug<<<<< rspFlg=false dly:1000/1000 Dev cmd: ConfigurationGet(parameterNumber:4) --> 700504, delay 1000 Dev cmd: ConfigurationGet(parameterNumber:5) --> 700505, delay 1000 Dev cmd: ConfigurationGet(parameterNumber:6) --> 700506

dev:692020-06-24 02:46:03.494 pm trace - 2: else: HubAction: ConfigurationGet(parameterNumber:6), format()=700506

dev:692020-06-24 02:46:03.490 pm trace - l -> ConfigurationGet(parameterNumber:6)

dev:692020-06-24 02:46:03.486 pm trace - 1: else: HubAction: ConfigurationGet(parameterNumber:5), format()=700505

dev:692020-06-24 02:46:03.483 pm trace - l -> ConfigurationGet(parameterNumber:5)

dev:692020-06-24 02:46:03.479 pm trace - 0: else: HubAction: ConfigurationGet(parameterNumber:4), format()=700504

dev:692020-06-24 02:46:03.475 pm trace - l -> ConfigurationGet(parameterNumber:4)

dev:692020-06-24 02:46:03.472 pm debug+++++ delayBetweenLog parm[3] dly=1000 responseFlg=false

dev:692020-06-24 02:46:03.469 pm debug+++++ getConfiguration() parmNo=6

dev:692020-06-24 02:46:03.465 pm debug+++++ getConfiguration() parmNo=5

dev:692020-06-24 02:46:03.462 pm debug+++++ getConfiguration() parmNo=4

dev:692020-06-24 02:46:03.458 pm debug+++++ getSchedules() endpoint=1 cnfNo=4

dev:692020-06-24 02:46:03.452 pm debug+++++ getTestCmds

dbeckr50 · July 3, 2020, 4:46pm

I failed to mention that I thank you for your work to make this device work with Hubitat, along with other contributors. It is the main reason I’m here. I saw your call a while back for a pe653 for testing. I have only one that I’m using but I would gladly contribute for purchasing you another.

keithriley · July 19, 2020, 8:48pm

Hubitat Pool Community, I have published a new release that adds enhancements and fixes issues reported by several of you. The new release can be downloaded here:

Here is a summary of the changes:

Added P5043 expansion detection. Improved P4043/P4243 expansion handling of Pool/Spa switch and Heater state.
Add deeper refresh() to poll() every 10 minutes
Added more specific log options and reduced base logging (recommend “Low” setting always)
Improve shared control by the DTH AND the PE953 remote.
Implemented Thermostat child device on ST (optional)
Fixed command sending when settings are updated()
Add support for Intermatic firmware v3.1 (old - most users on v3.4)
Numerous other minor bug fixes.
It is NOT necessary to patch this version if you have the 4043/4243 expansion to fix the pool/spa mode or heater display. This new version automatically detects the expansion type. If you had issues with either of these displays then look to this new version for relief.

The thermostat child device also has minor updates.

I will follow this with some individual posts directed to those of you whom (I hope) the new release will provide some benefit.

Keith

keithriley · July 19, 2020, 9:33pm

Bruce,

Version 4.0.2 posted above implements the firmware v3.1 adjustments we discussed. It should auto-detect v3.1 and shift where it pulls things like the temperature and other settings. I also noticed that some of the configuration commands were not being accepted by the controller.

When you get the chance please try out the new version and kick the tires. Please also capture some new logs when changing one of the preferences, like the debug level or temperature offset.

Best of luck!

Keith

keithriley · July 19, 2020, 9:39pm

@aarony, The new version I posted about (4.0.2) has several fixes in the configuration commands sent when you change settings. Please give it a try when you get a chance and let me know how it works. Please post logs if you have any issues.

Keith

ethelredkent · July 19, 2020, 11:04pm

Hey Keith,
It does not look like the offsets changed from the previous version.
manProp1 : [5, 64, 2, 1, -124, -1, 2, 0, 0, 1, 79, 0, 72, 14, 7, 0, 0, 0, 0, 3, 1, 0, 0, 0, 0, 0] -Old
manProp1 : [5, 64, 2, 1, -124, 83, 2, 0, 0, 1, 81, 0, 70, 15, 47, 0, 0, 0, 0, 3, 1, 0, 0, 0, 0, 0] New
Maybe it's failing on the routine that recognizes the Intermatic versions.
Should, I try to capture that part of the logic capturing in a debug log? If so how?
Cheers Bruce

State Variables

VersionInfo : Versions: Firmware v3.1 DTH: Ver 4.0.2 zWaveLibraryType: 6 zWaveProtocol: v2.78
ManufacturerInfo : ManufacturerInfo: manufacturerId: 5, manufacturerName: Intermatic, productId: 1619, productTypeId: 20549
size : 1
expansionVersion : none
precision : 0
schedules : []
lightCircuitsList : []
scale : 1
manProp1 : [5, 64, 2, 1, -124, 83, 2, 0, 0, 1, 81, 0, 70, 15, 47, 0, 0, 0, 0, 3, 1, 0, 0, 0, 0, 0]
firmwareVersion : 0.0
poolSetpointTemp : 1.0

Current States

ManufacturerInfo : ManufacturerInfo: manufacturerId: 5, manufacturerName: Intermatic, productId: 1619, productTypeId: 20549
VersionInfo : Versions: Firmware v3.1 DTH: Ver 4.0.2 zWaveLibraryType: 6 zWaveProtocol: v2.78
airTempFreeze : 15
airTempSolar : 55
clock : 00:00
lightColor : null
poolSetpoint : 51
poolSpaMode : disabled
spaSetpoint : 50
swVSP1 : disabled
swVSP2 : disabled
swVSP3 : disabled
swVSP4 : disabled
switch : off
switch1 : off
switch2 : off
switch3 : off
switch4 : off
switch5 : off
temperature : 70

aarony · July 20, 2020, 12:52am

That solved it! thanks.

CAL.hub · July 21, 2020, 2:16pm

Hi, Keith. Can you elaborate on what this does? I'm wondering if it perhaps improves the ability to set program schedules from HE.

P.S. I'm away for this week to escape the brutal heat you are enjoying.

keithriley · July 22, 2020, 9:17pm

Hi Charles,

This is more about the fact that originally the DTH was written (by bigpunk6) as though ONLY the DTH was in control of the PE653. It writes commands to it assuming the remote does not, and also assumes that if it last set a value, like a setpoint, that it must still be set the same, because no recognition of the PE953 remote. If you actually used the 953, then the DTH would be out of sync and changing setting could cause weird unexpected results, like setpoints way off.

Now the DTH periodically reads the 653 to get the latest values rather than assuming it "remembers" what they last were. I use both interchangeably and this is working better for me now. (I like the fact that the 953 is waterproof).

Keith

lewis.heidrick · July 22, 2020, 9:30pm

My wife breaks all kinds of electronics with water. I can't tell you how many things I've had to replace because she got them wet.

aarony · August 1, 2020, 11:04pm

After the update temperature has not been automatically updating. The Refresh button doesn’t seem to work, but quick get water temp does.

Also, I don’t know if it matters, but my airTempFreeze is set at 84.

keithriley · August 7, 2020, 4:28pm

@aarony, could you post a "Low" level log of pressing the Refresh button please, and then the QuickGetWaterTemp?

Thanks!

CAL.hub · August 7, 2020, 5:21pm

Hi, Keith.

You didn't ask - I kinda felt left out - but I thought there might be some use to you to see the logs from another system. I turned on low debugging and hit the quickGetWaterTemp button.

Thanks for keeping at this.

Charles

[dev:3234](http://192.168.1.140/logs#dev3234)2020-08-07 01:14:08.563 pm [debug](http://192.168.1.140/device/edit/3234)<<<<< rspFlg=true dly:1000/1000 0 Commands, 0 Delays, 1 Events <<<<< Event: "129" to airTempSolar (was: "130")

[dev:3234](http://192.168.1.140/logs#dev3234)2020-08-07 01:14:08.449 pm [debug](http://192.168.1.140/device/edit/3234)----- process84Event Firmware-PE653: 3.4 state.expansionVersion=3.4 EXPANSION_5043=true getP5043=true

[dev:3234](http://192.168.1.140/logs#dev3234)2020-08-07 01:14:08.438 pm [debug](http://192.168.1.140/device/edit/3234)>>>>> ManufacturerProprietary(type:84, payload: 05 40 02 02 84 53 10 02 01 00 02 00 59 5D 82 0D 0C 14 00 00 00 03 04 01 0E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 )

[dev:3234](http://192.168.1.140/logs#dev3234)2020-08-07 01:14:06.904 pm [debug](http://192.168.1.140/device/edit/3234)----- rspFlg=true No Commands or Events

[dev:3234](http://192.168.1.140/logs#dev3234)2020-08-07 01:14:06.809 pm [debug](http://192.168.1.140/device/edit/3234)>>>>> ManufacturerProprietary(type:87, payload: 05 40 02 02 87 53 10 02 01 01 02 07 03 04 00 48 00 12 04 00 04 00 00 25 0D 0C 14 01 00 00 20 00 00 00 00 00 00 00 00 00 )

[dev:3234](http://192.168.1.140/logs#dev3234)2020-08-07 01:14:05.296 pm [debug](http://192.168.1.140/device/edit/3234)----- rspFlg=true No Commands or Events

[dev:3234](http://192.168.1.140/logs#dev3234)2020-08-07 01:14:05.206 pm [debug](http://192.168.1.140/device/edit/3234)----- SensorMultilevelReport value=89 unit=1

[dev:3234](http://192.168.1.140/logs#dev3234)2020-08-07 01:14:05.200 pm [debug](http://192.168.1.140/device/edit/3234)>>>>> SensorMultilevelReport(precision:0, scale:1, sensorType:1, sensorValue:[89], size:1, scaledSensorValue:89) - raw[zw device: 41, command: 3105, payload: 01 09 59 , isMulticast: false]

[dev:3234](http://192.168.1.140/logs#dev3234)2020-08-07 01:14:04.783 pm [debug](http://192.168.1.140/device/edit/3234)<<<<< rspFlg=false dly:1000/1000 3 Commands, 2 Delays, 0 Events <<<<< Cmd to Device: SensorMultilevelGet() --> 3104, delay 1000 <<<<< HubAction: 910005400102870301, delay 1000 <<<<< HubAction: 910005400101830101

[dev:3234](http://192.168.1.140/logs#dev3234)2020-08-07 01:14:04.742 pm [debug](http://192.168.1.140/device/edit/3234)+++++ getWaterTemp()

[dev:3234](http://192.168.1.140/logs#dev3234)2020-08-07 01:14:04.740 pm [debug](http://192.168.1.140/device/edit/3234)+++++ quickGetWaterTemp

[dev:3234](http://192.168.1.140/logs#dev3234)2020-08-07 01:13:51.744 pm [debug](http://192.168.1.140/device/edit/3234)<<<<< rspFlg=true dly:1000/1000 0 Commands, 0 Delays, 3 Events <<<<< Event: "on" to poolSpaMode (was: "off") <<<<< Event: "130" to airTempSolar (was: "134")

[dev:3234](http://192.168.1.140/logs#dev3234)2020-08-07 01:13:51.597 pm [debug](http://192.168.1.140/device/edit/3234)----- process84Event Firmware-PE653: 3.4 state.expansionVersion=3.4 EXPANSION_5043=true getP5043=true

[dev:3234](http://192.168.1.140/logs#dev3234)2020-08-07 01:13:51.592 pm [debug](http://192.168.1.140/device/edit/3234)>>>>> ManufacturerProprietary(type:84, payload: 05 40 02 02 84 53 10 02 01 00 02 00 59 5D 83 0D 0C 14 00 00 00 03 04 01 0E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 )

[dev:3234](http://192.168.1.140/logs#dev3234)2020-08-07 01:13:50.627 pm [debug](http://192.168.1.140/device/edit/3234)----- rspFlg=true No Commands or Events

[dev:3234](http://192.168.1.140/logs#dev3234)2020-08-07 01:13:50.589 pm [debug](http://192.168.1.140/device/edit/3234)>>>>> ManufacturerProprietary(type:87, payload: 05 40 02 02 87 53 10 02 01 01 02 07 03 04 00 48 00 12 04 00 04 00 00 25 0D 0C 14 01 00 00 20 00 00 00 00 00 00 00 00 00 )

aarony · August 7, 2020, 6:26pm

Thanks Keith! Here is the output. I clicked refresh first then QuickGetWaterTemp.

dev:2962020-08-07 01:23:08.449 pm errorjava.lang.NullPointerException: Cannot invoke method toInteger() on null object on line 629 (parse)

dev:2962020-08-07 01:23:08.282 pm debug----- process84Event Firmware-PE653: 3.4 state.expansionVersion=null EXPANSION_5043=false getP5043=false

dev:2962020-08-07 01:23:08.275 pm debug>>>>> ManufacturerProprietary(type:84, payload: 05 40 02 02 84 53 00 00 05 00 00 01 59 5A 00 0D 11 01 00 00 08 03 04 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 )

dev:2962020-08-07 01:23:07.308 pm debug----- rspFlg=true No Commands or Events

dev:2962020-08-07 01:23:07.259 pm debug>>>>> ManufacturerProprietary(type:87, payload: 05 40 02 02 87 53 00 00 00 00 00 07 00 00 00 00 00 00 04 00 00 00 00 00 0D 11 01 01 00 00 20 00 00 00 00 00 00 00 00 00 )

dev:2962020-08-07 01:23:06.279 pm debug----- rspFlg=true No Commands or Events

dev:2962020-08-07 01:23:06.209 pm debug----- SensorMultilevelReport value=88 unit=1

dev:2962020-08-07 01:23:06.205 pm debug>>>>> SensorMultilevelReport(precision:0, scale:1, sensorType:1, sensorValue:[88], size:1, scaledSensorValue:88) - raw[zw device: 39, command: 3105, payload: 01 09 58 , isMulticast: false]

dev:2962020-08-07 01:23:06.077 pm debug<<<<< rspFlg=false dly:1000/1000 3 Commands, 2 Delays, 0 Events <<<<< Cmd to Device: SensorMultilevelGet() --> 3104, delay 1000 <<<<< HubAction: 910005400102870301, delay 1000 <<<<< HubAction: 910005400101830101

dev:2962020-08-07 01:23:06.069 pm debug+++++ getWaterTemp()

dev:2962020-08-07 01:23:06.066 pm debug+++++ quickGetWaterTemp

dev:2962020-08-07 01:22:52.602 pm errorgroovy.lang.GroovyRuntimeException: Cannot compare java.util.ArrayList with value '[0, 1]' and java.lang.String with value '5' on line 1322 (refresh)

dev:2962020-08-07 01:22:52.565 pm debug----- refreshInternal() DTH:Ver 4.0.2 state.Versioninfo=Versions: Firmware v3.4 DTH: Ver 4.0.2 zWaveLibraryType: 6 zWaveProtocol: v2.78

--- Live Log Started, waiting for events ---

keithriley · August 7, 2020, 6:49pm

@aarony, Oops, I see two exceptions in the log, both will need fixing. I'll dig in deeper this weekend and get back to you. At least this clarifies why this aren't working for you. Interesting that in the post from @CAL.hub, he is not getting the exceptions (nor am I), so something different is at work here...

(thanks Charles, I captured yours from a few years back and several posts since. #NotLeftOut)

Keith

keithriley · August 9, 2020, 8:45pm

@aarony I tracked down the two exceptions. I think you can easily fix both of them. It appears you do not have a "fireman timeout" set in the preferences for the Pool Control. Please select an appropriate value from the drop-down list. If it appears there is already one set, please change it to a different value, save and then set it to what makes sense for you (Usually either No Heater or No Cooldown. This is preventing the temps from being updated. Also it appears you have 2 lines selected in the Debug mode setting. This should not even be allowed (I will fix that) but make sure that only one line is selected at a time. This is also preventing some of the config commands from being sent. I can compensate for both of these in a new version but you can easily remove the cause for now.

Let me know how that works out,

Keith

aarony · August 10, 2020, 1:33pm

Keith. Thanks like always you solved it. Why is my airTempFreeze so high?

keithriley · August 13, 2020, 1:45pm

@aarony, now that we have those pesky exceptions sorted out (hopefully), let me ask you to repost new logs of both the key clicks (post #492). I'll make sure the numbers are being handled correctly. But one thing I'll say is that the PE653 essentially has 3 temperature inputs that can be connected to whatever sensors you want. That said, the 653 has specific purposes for each of them (ie: pool temp compared against thermostats, solar used to control valves, air used to protect against freeze). but the bottom line is that they are just sensors so you may need to check your wiring to ensure it is measuring what you need. But let's start with the logs.

Keith

aarony · August 13, 2020, 5:52pm

here you go. let me know what you think.

dev:2962020-08-13 12:48:26.104 pm debug <<<<< rspFlg=true dly:1000/1000 0 Commands, 0 Delays, 1 Events <<<<< Event: "86" to temperature (was: "85")

dev:2962020-08-13 12:48:25.553 pm debug ----- process84Event Firmware-PE653: 3.4 state.expansionVersion=none EXPANSION_5043=false getP5043=false

dev:2962020-08-13 12:48:25.544 pm debug >>>>> ManufacturerProprietary(type:84, payload: 05 40 02 02 84 53 00 00 05 00 00 01 56 55 00 0C 2A 01 00 00 08 03 04 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 )

dev:2962020-08-13 12:48:24.708 pm debug ----- rspFlg=true No Commands or Events

dev:2962020-08-13 12:48:24.625 pm debug >>>>> ManufacturerProprietary(type:87, payload: 05 40 02 02 87 53 00 00 00 00 00 07 00 00 00 00 00 00 04 00 00 00 00 00 0C 2A 01 01 00 00 20 00 00 00 00 00 00 00 00 00 )

dev:2962020-08-13 12:48:23.697 pm debug ----- rspFlg=true No Commands or Events

dev:2962020-08-13 12:48:23.535 pm debug ----- SensorMultilevelReport value=85 unit=1

dev:2962020-08-13 12:48:23.530 pm debug >>>>> SensorMultilevelReport(precision:0, scale:1, sensorType:1, sensorValue:[85], size:1, scaledSensorValue:85) - raw[zw device: 39, command: 3105, payload: 01 09 55 , isMulticast: false]

dev:2962020-08-13 12:48:23.409 pm debug <<<<< rspFlg=false dly:1000/1000 3 Commands, 2 Delays, 0 Events <<<<< Cmd to Device: SensorMultilevelGet() --> 3104, delay 1000 <<<<< HubAction: 910005400102870301, delay 1000 <<<<< HubAction: 910005400101830101

dev:2962020-08-13 12:48:23.402 pm debug +++++ getWaterTemp()

dev:2962020-08-13 12:48:23.399 pm debug +++++ quickGetWaterTemp

dev:2962020-08-13 12:48:17.697 pm debug ----- rspFlg=true No Commands or Events

dev:2962020-08-13 12:48:17.307 pm debug ----- process84Event Firmware-PE653: 3.4 state.expansionVersion=none EXPANSION_5043=false getP5043=false

dev:2962020-08-13 12:48:17.300 pm debug >>>>> ManufacturerProprietary(type:84, payload: 05 40 02 02 84 53 00 00 05 00 00 01 55 55 00 0C 2A 01 00 00 08 03 04 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 )

dev:2962020-08-13 12:48:16.322 pm debug ----- rspFlg=true No Commands or Events

dev:2962020-08-13 12:48:16.298 pm debug >>>>> ManufacturerProprietary(type:87, payload: 05 40 02 02 87 53 00 00 00 00 00 07 00 00 00 00 00 00 04 00 00 00 00 00 0C 2A 01 01 00 00 20 00 00 00 00 00 00 00 00 00 )

dev:2962020-08-13 12:48:15.270 pm debug ----- rspFlg=true No Commands or Events

dev:2962020-08-13 12:48:15.256 pm debug ----- ManufacturerSpecificReport: ManufacturerInfo: manufacturerId: 5, manufacturerName: Intermatic, productId: 1619, productTypeId: 20549

dev:2962020-08-13 12:48:15.250 pm debug >>>>> ManufacturerSpecificReport(manufacturerId:5, productId:1619, productTypeId:20549) - raw[zw device: 39, command: 7205, payload: 00 05 50 45 06 53 , isMulticast: false]

dev:2962020-08-13 12:48:14.254 pm debug ----- rspFlg=true No Commands or Events

dev:2962020-08-13 12:48:14.236 pm debug >>>>> VersionReport(zWaveLibraryType:6, zWaveProtocolVersion:2, zWaveProtocolSubVersion:78, applicationVersion:3, applicationSubVersion:4) - raw[zw device: 39, command: 8612, payload: 06 02 4E 03 04 , isMulticast: false]

dev:2962020-08-13 12:48:13.244 pm debug ----- rspFlg=true No Commands or Events

dev:2962020-08-13 12:48:13.215 pm debug ----- ThermostatSetpointReport: Report without previous requested change (setpointSet), setpoint=39

dev:2962020-08-13 12:48:13.212 pm debug ----- ThermostatSetpointReport: incoming requested state.spaSetpointTemp=null reported Setpoint=39 state.scale=1 setpointType=7

dev:2962020-08-13 12:48:13.206 pm debug >>>>> ThermostatSetpointReport(setpointType:7, precision:0, scale:1, size:1, value:[39], scaledValue:39) - raw[zw device: 39, command: 4303, payload: 07 09 27 , isMulticast: false]

dev:2962020-08-13 12:48:12.223 pm debug ----- rspFlg=true No Commands or Events

dev:2962020-08-13 12:48:12.191 pm debug ----- ThermostatSetpointReport: Report without previous requested change (setpointSet), setpoint=39

dev:2962020-08-13 12:48:12.188 pm debug ----- ThermostatSetpointReport: incoming requested state.poolSetpointTemp=null reported Setpoint=39 state.scale=1 setpointType=1

dev:2962020-08-13 12:48:12.181 pm debug >>>>> ThermostatSetpointReport(setpointType:1, precision:0, scale:1, size:1, value:[39], scaledValue:39) - raw[zw device: 39, command: 4303, payload: 01 09 27 , isMulticast: false]

dev:2962020-08-13 12:48:11.178 pm debug ----- rspFlg=true No Commands or Events

dev:2962020-08-13 12:48:11.173 pm debug ----- ConfigurationReport - got parameter=22 - spamode1, value=[0]

dev:2962020-08-13 12:48:11.170 pm debug >>>>> ConfigurationReport(configurationValue:[0], parameterNumber:22, size:1) - raw[zw device: 39, command: 7006, payload: 16 01 00 , isMulticast: false]

dev:2962020-08-13 12:48:10.179 pm debug ----- rspFlg=true No Commands or Events

dev:2962020-08-13 12:48:10.175 pm debug ----- ConfigurationReport - got parameter=3 - temperatureOffsets, value=[254, 0, 0, 0]

dev:2962020-08-13 12:48:10.172 pm debug >>>>> ConfigurationReport(configurationValue:[254, 0, 0, 0], parameterNumber:3, size:4) - raw[zw device: 39, command: 7006, payload: 03 04 FE 00 00 00 , isMulticast: false]

dev:2962020-08-13 12:48:09.203 pm debug ----- rspFlg=true No Commands or Events

dev:2962020-08-13 12:48:09.196 pm debug ----- ConfigurationReport - got parameter=2 - firemanTimeout, value=[255, 1]

dev:2962020-08-13 12:48:09.192 pm debug >>>>> ConfigurationReport(configurationValue:[255, 1], parameterNumber:2, size:2) - raw[zw device: 39, command: 7006, payload: 02 02 FF 01 , isMulticast: false]

dev:2962020-08-13 12:48:08.150 pm debug ----- rspFlg=true No Commands or Events

dev:2962020-08-13 12:48:08.146 pm debug ----- ConfigurationReport - got parameter=1 - operationMode, value=[6, 1]

dev:2962020-08-13 12:48:08.142 pm debug >>>>> ConfigurationReport(configurationValue:[6, 1], parameterNumber:1, size:2) - raw[zw device: 39, command: 7006, payload: 01 02 06 01 , isMulticast: false]

dev:2962020-08-13 12:48:08.017 pm debug <<<<< rspFlg=false dly:1000/1000 10 Commands, 9 Delays, 0 Events <<<<< Cmd to Device: ConfigurationGet(parameterNumber:1) --> 700501, delay 1000 <<<<< Cmd to Device: ConfigurationGet(parameterNumber:2) --> 700502, delay 1000 <<<<< Cmd to Device: ConfigurationGet(parameterNumber:3) --> 700503, delay 1000 <<<<< Cmd to Device: ConfigurationGet(parameterNumber:22) --> 700516, delay 1000 <<<<< Cmd to Device: ThermostatSetpointGet(setpointType:1) --> 430201, delay 1000 <<<<< Cmd to Device: ThermostatSetpointGet(setpointType:7) --> 430207, delay 1000 <<<<< Cmd to Device: VersionGet() --> 8611, delay 1000 <<<<< Cmd to Device: ManufacturerSpecificGet() --> 7204, delay 1000 <<<<< HubAction: 910005400102870301, delay 1000 <<<<< HubAction: 910005400101830101

dev:2962020-08-13 12:48:07.986 pm debug ----- refreshInternal() DTH:Ver 4.0.2 state.Versioninfo=Versions: Firmware v3.4 DTH: Ver 4.0.2 zWaveLibraryType: 6 zWaveProtocol: v2.78

keithriley · August 17, 2020, 12:50pm

@aarony logs look clean. I think we've got it, as long as everything is working as expected. Thanks for your help in testing and reporting.

Did you track down what you have connected to the airTempFreeze sensor?

Keith