HC3 main energy meter limited to energyMeter device type

[lazer 41]

On previous firmwares until 5.070, it was possible to select any device as main energy meter in general parameters panel, as long as they had the energy interface (thus an energy property) :

 

Please login or register to see this image.

/monthly_2021_08/1591187248_Mainenergymeter5_070_42.png.f056edf9d237302430941e054045ea67.png" />

 

Since new 5.080 stable firmware, it's not possible anymore, the choice is limited to only energyMeter device type :

 

 

 

Could you fix that in next firmware ?

 

For now, I have revert back to 5.070, as my whole house energy consumption device is not of type energyMeter, but powerSensor (with aditionnal energy property)

[tinman 1,070]

indeed, seems to be hard coded to energy meter, so i think we need to create child (or separate QA) to act as such.

Edited August 5, 2021 by tinman

[m.roszak 763]

What device is it?

If this is a Z-Wave one just hit soft-reconfiguration

 

powerSensor device type is no longer used by Z-Wave and it is obsoleted

 

This change in configuration is expected.

[lazer 41]

Both Z-Wave devices and QuickApps are concerned.

 

OK I can try to soft-reconfigure Z-Wave devices, but what about QA ?

[m.roszak 763]

Use com.fibaro.energyMeter for energy production/consumption.
For instant powe meters (Watts) Z-Wave now uses com.fibaro.powerMeter device type but if you like you can still use com.fibaro.powerSensor (if you like).

com.fibaro.powerMeter does not have instant power graphs in it (working on it) - so that is the only reason to use old com.fibaro.powerSensor.

Just to clarify, "energy" interface was intended for actors with build-in energy measurements in the first place - we put a lot of work to clear a bit devices hierarchy (new meter types) and a lot of additional work on Z-Wave engine to fully support meters from this version (water, gas, heat, cool, electric ...)

The case with com.fibaro.powerSensor with energy interface is a legacy from HC2.