I've started measuring my 3-phase home energy 4/5 months ago with Aeotec HEM3 Gen5. I've 3 clamps for each phase... My main consumption device during the day is my Swimming Pool along with PH dosing and Chlorine production machines, around 900W of instant power consumption. I used to have something  this:
Phase1: 30W
Phase2: 900W
Phase3: 50W
Total Consumption: 980W

Last week I installed 4 Solar Panels and the production energy started to be injected on Phase 2. I know have the difference between the my consumption and production on Phase2 readings. For instance... If the panel is producing 700W the readings display:
Phase1: 30W
Phase2: 200W
Phase3: 50
Total Consumption: 280W

When I shutdown the swimming pool pump and all other machines I start to have negative readings:
Phase1: 30W
Phase2. -700W
Phase3: 50W
Total Consumption: -620W

My intention is to install a 1 clamp meter right on the Phase that receives the energy provided by the solar panels and set the device on HC3 as a Production. Now come my doubts...

Q1: This device will also register and display negative readings, am I right?

Q2: Will this Production energy be taken in account as energy consumed by my house in the Fibaro Energy Panel? I am asking this because since I installed the Solar Panels, my HEM3 Gen5 started to display only the Grid consumption and not my Total consumption (Grid+Solar).

Q3: Should the Consumption  on the Energy Panel be the Total Consumption (Grid+Solar)? And in this case should I create a sort of Virtual Device (through QA) that adds the abs(production readings) from by 1 clamp meter with the total consumption readings from my 3 clamps to get the Balance value calculated correctly?

Thanks for your help

is the Home Center 3 or other products affected by the log4j vulnerable?

Best Regards

why you developers broke exists behavior and replace nil to null function in json.decode ?

Please login or register to see this code.

Please login or register to see this code.

Please login or register to see this attachment.

today 3 times driving from home to home. nothing.

but some days ago it`s work. what happened?

here is alternative logs from homekit

Please login or register to see this attachment.

morning

Please login or register to see this attachment.

[skipped...]

back to home at the evening (expect lighting on - cuz too dark)

Please login or register to see this attachment.

yes, i can f**ck off on HC3 at all and use homekit events, but what the hell, Fibaro?

Where can there be a mistake?

This generates a message:

[29.11.2021] [18:16:51] [ERROR] [SCENE159]: /opt/fibaro/lua_engine/lua/engine/fibaro_sdk.lua:248: Assertion failed: Expected number

well thank you

Please login or register to see this attachment.

Just for those, who want to try and update to latest Beta 5.091.39, please don't do it..it is crashing.

After the update is downloaded, the system tries to reboot, and start services for like 30 minutes, and after that it goes to error mode.

You then need to go to recovery mode, and restart from the backup..

Is it possible to correct this in the new update.

I am waiting for a year now to get this corrected.

Thanks , 

Leon

Thank you for using our gateway! Be sure to update to the latest version to enjoy new features and improvements.


Main features:

1. A new, user-friendly wizard for adding Elero devices

Device configuration within the pairing process.
Pairing multiple devices in one process.
Redesigned default icons.

2. Configuration of favourite positions in device settings Advanced tab

Easy, single-button step-by-step wizard.
Possibility to name positions and use them in scenes and profiles.


What's new:

Access
Mobile device status indication.

Dashboard
Distinction of actions sent on click and hold of the slat rotation button.
Support for holding the level change button on device sidebar.
Favourite positions buttons available on device sidebar.

Devices
Possibility of enabling inversion in device Advanced tab for blinds/shutters/gates etc.
Improved and unified support of device control types.
New default icons for switches, dimmers, shutters, gates, and garage doors.
Added icons for missing device states (favourite positions, brightening, dimming, etc.).
Devices of the com.fibaro.baseShutter type available in the Blinds linked device.
Improved detecting if device is awake and checking its wake-up interval.**
Added missing support for FIBARO Roller Shutter 2 FGRM-222.**
Reinterview process optimisation.**

Elero*
Configuration of device name, assignment, and its type as a part of pairing process.
Possibility of pairing multiple devices of different types in one process.
Testing the device detected during the pairing process to allow its identification.
Inversion feature enabled by default for devices detected as awnings.
Support for controlling the slats position.
Support for alarms and notifications.
Possibility of configuring favourite positions.
Possibility of changing the device role.
Possibility of forcing the device polling.
Support for Elero Unio-868, Combio-868 HE, and Combio-868 LI.

Energy
New Ecology tab for ecu-enthusiasts and everyone who produces energy.
Displaying self-sufficiency level, equivalent trees planted, and CO2 reduction.
Animated graphs of achievements and their impact on the environment.
Possibility of setting the return rate in Panel Settings.
Calculation of already returned installation cost including set return rate.
Redesigned interface for configuring additional rates in Tariffs.

Network
Access Point remains enabled after finishing FTI if no network is connected.

Nice*
Improved and unified support of Nice Mono devices.
Global abort for all types of binding procedures.
Possibility of configuring favourite positions.
Possibility of changing the device role.
Possibility of forcing the device polling.

Quick Apps
Possibility of adding custom icon for all single-state devices (players, remotes, etc.).


Bug fixes:

Alarm
Alarm partitions (com.fibaro.alarmPartition) are not available as zones in alarm panel.

Dashboard
Holding the button on device sidebar does not work in mobile app.

Devices
Device properties and its interfaces are removed after the soft reconfiguration.
Soft reconfiguration of the device removes it from the linked device.
Maximum value reported by the sensor connected to analog input is limited to 4 digits.
In some cases, com.fibaro.baseShutter type device lose its configuration.
Incorrect setpoint temperature range for some thermostats.
Attempt to update firmware of some battery devices always fails.
Node provisioning list is not available.**
No power charts for power meters (com.fibaro.powerMeter).

Elero*
Incorrect default polling time interval.
Device is too early marked as dead but remains available.
Number of devices is not updated after removing the device.
In some cases, adding one device after another results in error.
In some cases, adding previously removed device is not possible.
Device polling is not stopped after performing action.
No Notifications tab.

Energy
No validation for entering negative values of measured energy.

Gateway Connection
Rebooting the master gateway always results in sending devices model to slaves.
Firmware update possibility disappears for devices added to slaves.

Nice*
In some cases, adding a new device is aborted before finishing the process.
Number of devices is not updated after removing the device.
No parameters after adding a device with parameters interface.
Device added on previous versions has its parameters disabled after performing update.
In some cases, clicking on remotes while binding is not always detected.
Redundant requests during device creating process.
No device calibration for BiDi Dimmer device.
Cannot bind new gate using its remote.
Incorrect default polling time value.

Notifications
System migration notification is restored and created after each reboot.

Other
Some HTTP requests do not require authentication.

Plugins
Recording feature in FIBARO Intercom plugin does not work.

Profiles
Some Elero devices are not available in profiles.

Scenes
No possibility to define multiple values in the date field.


Known issues:

Z-Wave engine 3.0
Some Z-Wave devices are not fully compatible with the new version of Z-Wave engine.
Gateway connection is not available in the new Z-Wave engine version.


* - does not apply to HC3L (Home Center 3 Lite)
** - applies only to Z-Wave Engine 3.0