Why do build in Generic z-wave driver have no MeterReport support?

[MrFarmer]

Hi,

Many, many zwave switch devices include power and energy reporting. For me an important reason to buy a specific device. However, with newer devices there is not a (functioning) specific driver. In many cases this would not be needed especially with the introduction of the build in Generic Z-Wave DT drivers.

However, I cannot understand why these and any other generic driver I try does not have any other than some very basic function. It is not a lot of work to add MeterReport support for example.

Now I am off building my own driver for a Shelly Plug S, again.

Cheers Rene

[marktheknife]

@MrFarmer

Many, many zwave switch devices include power and energy reporting. For me an important reason to buy a specific device. However, with newer devices there is not a (functioning) specific driver. In many cases this would not be needed especially with the introduction of the build in Generic Z-Wave DT drivers.

Can you be more specific about which devices you’re referring to?

There’s been lots of discussion in the forum for years about z-wave power reporting, and not just limited to custom/user-created drivers.

In fact it’s such a big topic that the staff have created special posts just to inform users about it. See, for example:

Dos and Don'ts of Z-Wave Power Reporting (repost)

Have you noticed automation slowdowns or even Z-Wave devices that aren’t firing at all? It is likely that one (or more) devices in your system are demanding too much Z-Wave bandwidth. One of the biggest bandwidth hogs is unnecessary power reporting. Let’s take a look at Z-Wave bandwidth constraints and how you can reduce or eliminate issues caused by power reporting. The Z-Wave radio in your Hubitat Elevation hub is designed with more than enough bandwidth to handle your day-to-day automations …

@MrFarmer

Now I am off building my own driver for a Shelly Plug S, again.

Isn’t this a WiFi device?

[MrFarmer]

@marktheknife

@MrFarmer

Many, many zwave switch devices include power and energy reporting. For me an important reason to buy a specific device. However, with newer devices there is not a (functioning) specific driver. In many cases this would not be needed especially with the introduction of the build in Generic Z-Wave DT drivers.

Can you be more specific about which devices you’re referring to?

In this case anything with power and energy metering. There is loads, mainly switches, build in or plugs.

@marktheknife

There’s been lots of discussion in the forum for years about z-wave power reporting, and not just limited to custom/user-created drivers.

In fact it’s such a big topic that the staff have created special posts just to inform users about it. See, for example:
Dos and Don'ts of Z-Wave Power Reporting (repost)

I am aware of this and no it is not what I am referring to. The generic drivers simply lack the function to handle the meter reports. As the Generic DT drivers give you full control over the parameters that control reporting frequency this should not be a problem. The devices will send the reports anyway unless explicitly disabled, the generic driver is simply not processing them. So without proper support you may be overloading the mesh without even being aware of all the traffic.

@marktheknife

@MrFarmer

Now I am off building my own driver for a Shelly Plug S, again.

Isn’t this a WiFi device?

Nope.

[bobbyD]

@MrFarmer

The devices will send the reports anyway unless explicitly disabled

You have a good point, and one that came up in a thread, yesterday

@MrFarmer

generic driver I try does not have any other than some very basic function.

The problem is that parameters are not standard. Their numbers change based on individual manufacturer. A user must figure out the power reporting parameter number, before they can set a new value. Leaving an empty field to allow a user to input the appropriate parameter is a recipe for disaster. That's why power reporting drivers are offered for specific manufacturers.

There is a way for newer DT Z-Wave drivers, like you suggested, and is currently under consideration by our engineers

[marktheknife]

@MrFarmer

Nope.

Apologies then, I was going by this description on the Shelly website:

Documentation about Shelly Plug S

[MrFarmer]

No problem. The Z-wave versions are quite new and at the good Shelly price as usual.

[MrFarmer]

@bobbyD

The problem is that parameters are not standard. Their numbers change based on individual manufacturer. A user must figure out the power reporting parameter number, before they can set a new value. Leaving an empty field to allow a user to input the appropriate parameter is a recipe for disaster. That's why power reporting drivers are offered for specific manufacturers.

There is a way for newer Z-Wave devices and is currently under consideration by our engineers

Great to hear you are looking at it :-). I know the report handling parameters is all over the place, but nearly all have a (min/max) report frequency parameter in seconds and always report Power and Energy. For energy monitoring devices like Aeotec HEM it is much more complex indeed. Having said this anyone configuring a (zwave) device without RTFM should be wrist slapped if they call in for support

[jtp10181]

@MrFarmer

I am aware of this and no it is not what I am referring to. The generic drivers simply lack the function to handle the meter reports. As the Generic DT drivers give you full control over the parameters that control reporting frequency this should not be a problem.

I brought this up when the DT drivers first came out. I suggested there needed to be a special metering switch one, which could mainly be used for power metering plugs/outlets. It was agreed it was needed, but never produced

I do have a similar driver set (mine are called Universal and have more features of course). I would highly suggest you take a peek at the switch version for a starting point. If you just add the metering capabilities and event handlers to it, it should work for ANY modern switch/meter device and it brings in all the settings just like the DT drivers.

I have been wanting to do this but just have not had time for it. Let me know if you decide to tackle it. You could even steal a whole bunch of code from my ZEN Plugs (ZEN04) driver for all the metering code, could probably copy and paste it all into the switch driver and be ready to go.

[DRIVER] Universal Z-Wave Drivers (Switch/Dimmer)

Package of Universal Z-Wave Drivers with the goal of probing the device for all features and options possible and presenting that to you for configuration. If you are using this driver PLEASE like this post This should work on ALL 800 series devices, and many 700 series. Current Package Version: v0.4.0 - 2024-07-16 Confirmed Working Devices: Should work on ALL 800 series devices, and many 700 series. Let me know about any devices that work and I can…

[MrFarmer]

Thanks Jeff, for now I go for reworking one of my other Plug drivers to one for the Shell Wave Plug S EU. I did have a look at your Universal drivers and looks great. I may do a pull request at one point with the MeterReport handling. For the Aeotec HEM8 I made some flexible code that I think could be a starting point (Hubitat/Aeotec/Aeotec Home Energy Meter 8 (3 clamp).groovy at main · reneboer/Hubitat · GitHub) If you want to grab it feel free to do so.

Cheers Rene