Energy Monitoring with GE Zigbee Dimmer (45852GE)

[jl.quema]

I have the following Dimmer Plug (https://amz.run/4BUZ) paired with my HE.
I'm using it with the "GE Zigbee Dimmer".
No problem to switch on/off, change the level, however, I can't find out how to read the energy consumption.

I have enabled the "Enable automatic power reporting" option with a 1 Watt threshold but I don't see any energy report coming. If I read correctly, by enabling this automatic reporting, I should see the power levels in the "events" tab.

Does anyone have any experience with this dimmer and how to use the energy feature?

Thanks

[mike.maxwell]

select the power reporting preference, then save preferences.
I just included a sample unit and tested it, it is reporting as expected.
remember, it's only the switched (non grounded outlet) that's monitored.

[jl.quema]

Hi Mike,

Thanks for replying.
This is what I did already: selecting "1 Watt" in the "Enable automatic power reporting" dropdown and save the preferences.
Then on the switched outlet, I have a 40W light bulb that I turn on and off (manually, not with the GE switch).
I would then expect to see the energy consumption change between 40W and 0W.
I check in the events of the devices as well as in the logs (debug enabled) but no trace of energy reporting...

Edit/additional note: following the sending of a refresh, the power value in the "Current States" section remains at 0:

Current States

• level : 90
• power : 0
• switch : on

[Navat604]

I have the GE zigbee dimmer and the power reporting is working fine. I don't have the plug so not sure about the driver needed for it to work.

[jl.quema]

Interesting...
It seems we are using the same driver/type: "GE Zigbee Dimmer"

I don't see any significant difference in the preferences.
I have the reporting interval at 5s and the power threshold at 5 watts

But on the top right (Current States) the power remains at zero and I don't see any reporting in the events when switching the bulb on/off (once again, with a separate switch)

Just to confirm: are you using the 45852GE model?

[Ranchitat]

Here's what my 45852GE looks like with a 9W bulb using the "GE Zigbee Dimmer" driver.
Power is showing on the Events tab.
Nothing connected to the pass-through outlet.

On

Off

Data

[Navat604]

I have the switch. Not the plug-in Zigbee dimmer even though they should be very similar.

Edit : maybe switch the driver to "device" then clear all states. Save preference.
Switch back to GE Zigbee dimmer. Configure. Save preference and see if that will help.

[jl.quema]

Thanks both.

I'm seeing the same details as @Ranchitat :

• endpointId: 01
• application: 12
• manufacturer: Jasco Products
• model: 45852

I don't have anything connected to the pass-trough either (in case it matters)

Following the advice of @Navat604 , I changed the device type, deleted all the states, and then put back "GE Zigbee Dimmer" but unfortunately, it didn't solve my issue: I still don't have any power showing in the event or in the current states.

In the log (when changing back the device type, I see however, a line reporting configuration for Metering succeded.

[dev:298] (...) 2021-01-05 03:22:51.062 pm [info](...device/edit/298)Study East is on [digital]
[dev:298] (...) 2021-01-05 03:22:47.906 pm [info](...device/edit/298)reporting configuration for Metering (cluster 0x0702) suceeded
[dev:298] (...) 2021-01-05 03:22:47.690 pm [info](...device/edit/298)reporting configuration for On/Off (cluster 0x0006) suceeded
[dev:298] (...) 2021-01-05 03:22:47.286 pm [info](...device/edit/298)reporting configuration for Level Control (cluster 0x0008) suceeded
[dev:298] (...) 2021-01-05 03:22:46.865 pm [warn](...device/edit/298)description logging is: true
[dev:298] (...) 2021-01-05 03:22:46.861 pm [warn](...device/edit/298)debug logging is: false
[dev:298] (...) 2021-01-05 03:22:46.857 pm [info](...device/edit/298)updated...
[dev:298] (...) 2021-01-05 03:22:16.064 pm [info](...device/edit/298)state.bulbLevel was removed...
[dev:298] (...) 2021-01-05 03:22:16.058 pm [info](...device/edit/298)state.bin was removed...

[jl.quema]

From the logs in my previous message, I guess the power is reported using cluster 0x0702.
I have re-enabled the debug log and sent a refresh.

I can see the following:

descMap:[raw:CDC40107020E00042A000000, dni:CDC4, endpoint:01, cluster:0702, size:0E, attrId:0400, encoding:2A, command:01, value:000000, clusterInt:1794, attrInt:1024]

I'm not sure of what the different parameters mean but the value being 000000 would let me think that the plug itself doesn't report any value (more exactly always reports 0)

I have 4 of them and they all have the same behavior so I doubt it's a hardware issue (otherwise, I'm very unlucky)...

[Ranchitat]

Hubitat Elevation C5 Platform 2.2.3.148

[jl.quema]

I'm on C5 2.2.4.158.

So we basically use the same dimmers, with the same drivers and same platform (2.2.x.y) but you have the power meter and I don't... argh!

[Ranchitat]

@jl.quema

same platform

Mines a different firmware/platform but Mike probably used the same version you're using when he tested the functionality on his sample unit.

@mike.maxwell

I just included a sample unit and tested it, it is reporting as expected.

Here's a pic of the back of mine, maybe it's a different version?

Model: ZB3101

[jl.quema]

Regarding the platform, I was in 2.2.3.148 and had the issue already (which is why I said "same")
I recently updated to 2.2.4.158 but it didn't change anything.

As you can see, I also have the ZB3101

Picture

[jl.quema]

Does it help to look at the debug log when sending the configure command?
Is it the correct approach to focus on clusterId 0702?

Configure Log

[dev:297] 2021-01-06 08:53:53.440 am debug			descMap:[raw:E7470107020E00042A000000, 	dni:E747, endpoint:01, cluster:0702, size:0E, attrId:0400, encoding:2A, command:01, value:000000, clusterInt:1794, attrInt:1024]
[dev:297] 2021-01-06 08:53:53.274 am debug			descMap:[raw:E7470100080A0000207F, 		dni:E747, endpoint:01, cluster:0008, size:0A, attrId:0000, encoding:20, command:01, value:7F, 	  clusterInt:8, 	 attrInt:0]
[dev:297] 2021-01-06 08:53:53.150 am debug			descMap:[raw:E7470100060A00001000, 		dni:E747, endpoint:01, cluster:0006, size:0A, attrId:0000, encoding:10, command:01, value:00, 	  clusterInt:6, 	 attrInt:0]
[dev:297] 2021-01-06 08:53:53.144 am trace	skipped descMap:[raw:catchall: 0104 0702 01 01 0040 00 E747 00 00 0000 07 01 00, 	profileId:0104, clusterId:0702, clusterInt:1794, 	sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:E747, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:07, direction:01, data:[00]]
[dev:297] 2021-01-06 08:53:53.123 am debug			descMap:[raw:catchall: 0104 0702 01 01 0040 00 E747 00 00 0000 07 01 00, 	profileId:0104, clusterId:0702, clusterInt:1794, 	sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:E747, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:07, direction:01, data:[00]]
[dev:297] 2021-01-06 08:53:53.074 am trace	skipped descMap:[raw:catchall: 0000 8021 00 00 0040 00 E747 00 00 0000 00 00 0D00, 	profileId:0000, clusterId:8021, clusterInt:32801, 	sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:E747, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[0D, 00]]
[dev:297] 2021-01-06 08:53:53.069 am debug			descMap:[raw:catchall: 0000 8021 00 00 0040 00 E747 00 00 0000 00 00 0D00, 	profileId:0000, clusterId:8021, clusterInt:32801, 	sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:E747, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[0D, 00]]
[dev:297] 2021-01-06 08:53:52.864 am trace	skipped descMap:[raw:catchall: 0104 0006 01 01 0040 00 E747 00 00 0000 07 01 00, 	profileId:0104, clusterId:0006, clusterInt:6, 		sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:E747, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:07, direction:01, data:[00]]
[dev:297] 2021-01-06 08:53:52.833 am debug			descMap:[raw:catchall: 0104 0006 01 01 0040 00 E747 00 00 0000 07 01 00, 	profileId:0104, clusterId:0006, clusterInt:6, 		sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:E747, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:07, direction:01, data:[00]]
[dev:297] 2021-01-06 08:53:52.615 am trace	skipped descMap:[raw:catchall: 0000 8021 00 00 0040 00 E747 00 00 0000 00 00 0B00, 	profileId:0000, clusterId:8021, clusterInt:32801, 	sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:E747, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[0B, 00]]
[dev:297] 2021-01-06 08:53:52.610 am debug			descMap:[raw:catchall: 0000 8021 00 00 0040 00 E747 00 00 0000 00 00 0B00, 	profileId:0000, clusterId:8021, clusterInt:32801, 	sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:E747, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[0B, 00]]
[dev:297] 2021-01-06 08:53:52.421 am trace	skipped descMap:[raw:catchall: 0104 0008 01 01 0040 00 E747 00 00 0000 07 01 00, 	profileId:0104, clusterId:0008, clusterInt:8, 		sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:E747, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:07, direction:01, data:[00]]
[dev:297] 2021-01-06 08:53:52.417 am debug			descMap:[raw:catchall: 0104 0008 01 01 0040 00 E747 00 00 0000 07 01 00, 	profileId:0104, clusterId:0008, clusterInt:8, 		sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:E747, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:07, direction:01, data:[00]]
[dev:297] 2021-01-06 08:53:52.241 am trace	skipped descMap:[raw:catchall: 0000 8021 00 00 0040 00 E747 00 00 0000 00 00 0900, 	profileId:0000, clusterId:8021, clusterInt:32801, 	sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:E747, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[09, 00]]
[dev:297] 2021-01-06 08:53:52.237 am debug			descMap:[raw:catchall: 0000 8021 00 00 0040 00 E747 00 00 0000 00 00 0900, 	profileId:0000, clusterId:8021, clusterInt:32801, 	sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:E747, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[09, 00]]
[dev:297] 2021-01-06 08:53:52.040 am warn	configure...

[jl.quema]

I'm reading the following: https://www.nxp.com/docs/en/user-guide/JN-UG-3115.pdf
Chapter 42 describes cluster 0702 ("Simple Metering Cluster").

Obviously, way more complex than I expected but I found out that attrId=0400 I see in the log is for E_CLD_SM_ATTR_ID_INSTANTANEOUS_DEMAND

I have now to understand the other parameters in:

descMap:[raw:E7470107020E00042A000000, dni:E747, endpoint:01, cluster:0702, size:0E, attrId:0400, encoding:2A, command:01, value:000000, clusterInt:1794, attrInt:1024]

Obviously, the value:000000, while a 40W incandescent bulb is ON, is incorrect.

@Ranchitat, @mike.maxwell, would you mind sharing your logs so I can compare what you have?
@Navat604, as you have the switch and not the plug-in dimmer, I guess your logs are different but it might be helpful too if using the same cluster.

Please forgive the non-sense (if any), as I'm far to be an expert in this area.

[Navat604]

raw:48410107020E00042A000000
dni:4841, endpoint:01, cluster:0702,
size:0E, attrId:0400, encoding:2A,
command:01, value:000000,
clusterInt:1794, attrInt:1024]

Have you looked at this post?

[RELEASE] GE/Jasco Power Monitoring Zigbee Smart Switch (45853, 45856)

So I figured I might as well drop this here, even though Mike has said 2.1.6 will contain support for these devices built-in. Since those drivers source aren't open source and I could not find any other Simple Metering (0702) drivers out there, this could be helpful for others. Caveat: This driver is a bit fresh, I've been using it for a few days, so it's presumably far from perfect. This driver supports I both plugin and in-wall versions thanks for @aruffell. Features: On/Off Switch cont…

[jl.quema]

@Navat604
I think you just found the root cause of my issue: it seems the "GE Zigbee dimmer" driver doesn't implement the Simple Metering (Cluster 0702)

As soon as I switched to the GE/Jasco Smart Switch driver from the other post, I was able to read the power.

Current States

• power : 36.9
• switch : on

Now, the problem is that this new driver only supports on/off but no dimmer function.

@mike.maxwell, do you confirm the above? that "power metering" is not supported by the "GE zigbee dimmer"driver?

I guess I could combine this driver (the on/off + power metering) with another one (dimming feature) but not sue if it is the wise thing to do...

Edit/Additional info:
I reverted to the GE Zigbee dimmer driver and now have a new behavior.
The power is not zero anymore but fluctuate between two values: 6 and 37 every 5s (which is my reporting interval).
My interpretation is that the GE/Jasco driver somehow enabled the power reporting feature and the GE Zigbee Dimmer driver can read it but not configure it properly.

[mike.maxwell]

Power reporting is supported with the built in ge zigbee switch and dimmer drivers.

[jl.quema]

Thanks for the feedback, although I'm confused:

• when using only the "GE Zigbee dimmer", I have no power reporting at all.
• when using in combination:
  • first the GE/Jasco driver, it "enables" the power reporting and it is stable (value doesn't change constantly)
  • second the "GE Zigbee dimmer", the power reporting remains enabled but the value changes all the time (switching between 2 values, in my example 6W and 37W). Changes in the threshold and reporting interval seem to be ignored as well

When using your sample, could it be that it was previously setup with another driver that would have enabled the power reporting feature?

[mike.maxwell]

please post a screen shot of the data section of the driver details for the device thats got the spastic power reporting, thanks.