That’s just config reports.. Can you run the log a bit longer?
sure... I'll collect more and update.
1 Like
dev:8062020-05-14 08:33:19.715 pm warndebug logging is: true
dev:8062020-05-14 08:33:19.713 pm infoupdated...
dev:8062020-05-14 08:33:14.498 pm infoFountain was turned on
dev:8062020-05-14 08:33:14.475 pm debugSwitchBinaryReport(value:255)
dev:8062020-05-14 08:33:14.469 pm debugparse:zw device: 23, command: 2503, payload: FF , isMulticast: false
dev:8062020-05-14 08:33:14.305 pm infoFountain energy is: 1.971
dev:8062020-05-14 08:33:14.299 pm infoFountain energy is: 1.971
dev:8062020-05-14 08:33:14.279 pm debugMeterReport(meterType: 1, precision: 3, scale: 0, size: 4, meterValue: [0, 0, 7, 179], rateType: 1, deltaTime: 2, previousMeterValue: [0, 0, 7, 179])
dev:8062020-05-14 08:33:14.268 pm debugparse:zw device: 23, command: 3202, payload: 21 64 00 00 07 B3 00 02 00 00 07 B3 , isMulticast: false
dev:8062020-05-14 08:33:14.244 pm debugMeterReport(meterType: 1, precision: 3, scale: 0, size: 4, meterValue: [0, 0, 7, 179], rateType: 1, deltaTime: 2, previousMeterValue: [0, 0, 7, 179])
dev:8062020-05-14 08:33:14.232 pm debugparse:zw device: 23, command: 3202, payload: 21 64 00 00 07 B3 00 02 00 00 07 B3 , isMulticast: false
dev:8062020-05-14 08:33:14.134 pm infoFountain energy is: 1.971
dev:8062020-05-14 08:33:14.107 pm debugMeterReport(meterType: 1, precision: 3, scale: 0, size: 4, meterValue: [0, 0, 7, 179], rateType: 1, deltaTime: 2, previousMeterValue: [0, 0, 7, 179])
dev:8062020-05-14 08:33:14.096 pm debugparse:zw device: 23, command: 3202, payload: 21 64 00 00 07 B3 00 02 00 00 07 B3 , isMulticast: false
dev:8062020-05-14 08:33:13.895 pm infoFountain voltage is: 119.173W
dev:8062020-05-14 08:33:13.874 pm debugSensorMultilevelReport(precision:3, scale:0, sensorType:15, sensorValue:[0, 1, 209, 133], size:4, scaledSensorValue:119.173)
dev:8062020-05-14 08:33:13.866 pm debugparse:zw device: 23, command: 3105, payload: 0F 64 00 01 D1 85 , isMulticast: false
dev:8062020-05-14 08:33:11.879 pm infoFountain was turned on
dev:8062020-05-14 08:33:11.856 pm debugSwitchBinaryReport(value:255)
dev:8062020-05-14 08:33:11.850 pm debugparse:zw device: 23, command: 2503, payload: FF , isMulticast: false
dev:8062020-05-14 08:33:11.680 pm infoFountain energy is: 1.971
dev:8062020-05-14 08:33:11.657 pm debugMeterReport(meterType: 1, precision: 3, scale: 0, size: 4, meterValue: [0, 0, 7, 179], rateType: 1, deltaTime: 2, previousMeterValue: [0, 0, 7, 179])
dev:8062020-05-14 08:33:11.646 pm debugparse:zw device: 23, command: 3202, payload: 21 64 00 00 07 B3 00 02 00 00 07 B3 , isMulticast: false
dev:8062020-05-14 08:33:11.465 pm infoFountain voltage is: 119.183W
dev:8062020-05-14 08:33:11.443 pm debugSensorMultilevelReport(precision:3, scale:0, sensorType:15, sensorValue:[0, 1, 209, 143], size:4, scaledSensorValue:119.183)
dev:8062020-05-14 08:33:11.435 pm debugparse:zw device: 23, command: 3105, payload: 0F 64 00 01 D1 8F , isMulticast: false
dev:8062020-05-14 08:33:10.087 pm infoFountain was turned on
dev:8062020-05-14 08:33:10.064 pm debugSwitchBinaryReport(value:255)
dev:8062020-05-14 08:33:10.058 pm debugparse:zw device: 23, command: 2503, payload: FF , isMulticast: false
dev:8062020-05-14 08:33:09.884 pm infoFountain energy is: 1.971
dev:8062020-05-14 08:33:09.861 pm debugMeterReport(meterType: 1, precision: 3, scale: 0, size: 4, meterValue: [0, 0, 7, 179], rateType: 1, deltaTime: 8, previousMeterValue: [0, 0, 7, 179])
dev:8062020-05-14 08:33:09.851 pm debugparse:zw device: 23, command: 3202, payload: 21 64 00 00 07 B3 00 08 00 00 07 B3 , isMulticast: false
dev:8062020-05-14 08:33:09.615 pm infoFountain voltage is: 119.203W
dev:8062020-05-14 08:33:09.590 pm debugSensorMultilevelReport(precision:3, scale:0, sensorType:15, sensorValue:[0, 1, 209, 163], size:4, scaledSensorValue:119.203)
dev:8062020-05-14 08:33:09.581 pm debugparse:zw device: 23, command: 3105, payload: 0F 64 00 01 D1 A3 , isMulticast: false
1 Like
Are you getting power details on yours?
1 Like
Sorry, I missed these errors in the logs also.
dev:8062020-05-14 08:31:23.942 pm infoFountain was turned on
dev:8062020-05-14 08:31:23.920 pm debugSwitchBinaryReport(value:255)
dev:8062020-05-14 08:31:23.913 pm debugparse:zw device: 23, command: 2503, payload: FF , isMulticast: false
dev:8062020-05-14 08:31:21.011 pm errorjava.lang.NumberFormatException: null on line 158 (parse)
dev:8062020-05-14 08:31:20.971 pm debugMeterReport(meterType: 1, precision: 3, scale: 0, size: 4, meterValue: [], rateType: 1, deltaTime: 0, previousMeterValue: [])
dev:8062020-05-14 08:31:20.963 pm debugparse:zw device: 23, command: 3202, payload: 21 64 00 00 07 AF , isMulticast: false
dev:8062020-05-14 08:31:19.444 pm infoFountain voltage is: 119.277W
dev:8062020-05-14 08:31:19.423 pm debugSensorMultilevelReport(precision:3, scale:0, sensorType:15, sensorValue:[0, 1, 209, 237], size:4, scaledSensorValue:119.277)
dev:8062020-05-14 08:31:19.414 pm debugparse:zw device: 23, command: 3105, payload: 0F 64 00 01 D1 ED , isMulticast: false
dev:8062020-05-14 08:31:14.773 pm infoFountain was turned on
dev:8062020-05-14 08:31:14.749 pm debugSwitchBinaryReport(value:255)
dev:8062020-05-14 08:31:14.741 pm debugparse:zw device: 23, command: 2503, payload: FF 64 00 00 07 AF 00 00 00 00 07 AF , isMulticast: false
dev:8062020-05-14 08:31:13.740 pm infoFountain energy is: 1.967
dev:8062020-05-14 08:31:13.719 pm debugMeterReport(meterType: 1, precision: 3, scale: 0, size: 4, meterValue: [0, 0, 7, 175], rateType: 1, deltaTime: 0, previousMeterValue: [0, 0, 7, 175])
dev:8062020-05-14 08:31:13.709 pm debugparse:zw device: 23, command: 3202, payload: 21 64 00 00 07 AF 00 00 00 00 07 AF , isMulticast: false
dev:8062020-05-14 08:31:07.083 pm errorjava.lang.NumberFormatException: null on line 158 (parse)
dev:8062020-05-14 08:31:07.077 pm errorjava.lang.NumberFormatException: null on line 158 (parse)
dev:8062020-05-14 08:31:07.016 pm debugMeterReport(meterType: 1, precision: 3, scale: 0, size: 4, meterValue: [], rateType: 1, deltaTime: 0, previousMeterValue: [])
dev:8062020-05-14 08:31:07.008 pm debugparse:zw device: 23, command: 3202, payload: 21 64 00 00 07 AF , isMulticast: false
dev:8062020-05-14 08:31:06.977 pm debugMeterReport(meterType: 1, precision: 3, scale: 0, size: 4, meterValue: [], rateType: 1, deltaTime: 0, previousMeterValue: [])
dev:8062020-05-14 08:31:06.961 pm debugparse:zw device: 23, command: 3202, payload: 21 64 00 00 07 AF , isMulticast: false
dev:8062020-05-14 08:31:06.356 pm infoFountain voltage is: 119.337W
dev:8062020-05-14 08:31:06.334 pm debugSensorMultilevelReport(precision:3, scale:0, sensorType:15, sensorValue:[0, 1, 210, 41], size:4, scaledSenso
2 Likes
Yes.
1 Like
OK.. just pushed an update to fix that typo of W on voltage ..
But your device hasn't sent watt report yet..
Hit configure again .. it might have missed one of the setup messages.. and stop hitting refresh .. the device auto reports..
2 Likes
Hmmm, don't know, I see Voltage reports, but no wattage. I'm really not too concerned really, I just need on/off at this point. I moved this from ST where it was on my dryer, but I now have an Iris Smart Plug on the dryer, I switched it with the fountain when I moved it from ST.
I just figured if I had this, maybe others did too, I care about wattage for the Laundry monitoring app.
1 Like
I might have a workaround for it not reporting wattage... Give me a bit..
1 Like
Take your time, and thanks again
1 Like
Looking back on your logs.. I think it's missing packets part of the setup.. Because I see duplicated packets there..
But I am working on a manual refresh poll of wattage..
The normal methods in refresh I had to choose between W and V and since it auto reported W, I chose to do V since that is never auto reported.. But I should be able to poll it through meter in kW and convert it to W..
1 Like
I have a couple of these switches. Just tried setting one up and I can control the switch and see some power data but the Switch state never changes from OFF to ON when cycling the switch. I actually tried a few different generic drivers and none of them seem to work.
I am going to try the second switch I have to see if it's possibly an issue with the one unit, but any other ideas on what to try if that isn't the case?
1 Like
Did you hit Configure after changing drivers?
1 Like
I did, but after testing the second unit I think the problem is I'm just too far from the hub for reliable polling. I tested the new switch in the same room as the hub, and it reported the state change instantly. I then moved it to the porch where it would be living (maybe 30-35 feet and a few walls away) and it stopped reporting the state again.
Both switches do respond to on / off commands, sometimes a little delayed. I think I'll pick up some newer ZWave Plus units or add a couple of repeaters to the mix.
1 Like
Aha. I have a really good z-wave mesh with multiple z-wave+ repeaters and only a handful of older line-powered z-wave devices (like the DSC06106). Both of mine are about 30+ feet (and one floor and one wall) away from the HE, and the status change is instant.
1 Like
This is fantastic! You have given these devices new life. I have a bunch of these on room air conditioners and space heaters. One thing I like about them is they keep track of cumulative energy. One thing I can't figure out is how to reset the energy field. On HE stock driver there is a reset button to do this. Is there a way to do that on your driver? Thanks for all you do,
1 Like
Yep.. I’ll add that
3 Likes
I've been using your driver for a couple of days and very pleased at how well it works. The data all seems to be correct but occasionally this error pops up. Not sure if anyone else are getting these.
1 Like
Ok.. I’ll check it out
1 Like
I also saw that error today right after I switched to your driver. Seemed to happen shortly after I did a Configure and right as the plug started doing its regular reports.
Also it seems to be reporting back energy very often. I just left the defaults, but it is reporting several times a minute. Should I be changing some setting?
