Both of my units are the 3 phase 4 wire version made for EU.
One has firmware 1.5 and the other one has firmware 1.8.
I have discovered when looking through debug logs that it seems that Indigo does not parse energy reports for my unit with the newer firmware 1.8?!
I do see energy reports showing in the debug log but Indigo does not populate it to the GUI and nor does it parse it.
It works fine for power reports and for firmware 1.5 it works fine for both power and energy reports.
This error has most likely been there for ever and has not shown up after my switch from the S2 stick to the S5 stick but I will dig into some old debug logs when using the S2 stick.
Here are 2 examples of power load total reports for DSB28 Home Energy Meter G2 with firmware 1.5 and as you can see they are properly parsed by Indigo:
- Code: Select all
Z-Wave Debug RCVD requestMeterLevel: 01 14 00 04 00 1E 0E 32 02 21 74 00 13 76 76 00 00 FD AC 00 3C E4
Z-Wave Debug . . requestMeterLevel: node 030, endpoint None, meterType 01, raw value 7400...
Z-Wave Debug . . requestMeterLevel: 1275.510 W (float: 1275.510000)
Z-Wave received "Energy Meter - House - TOTAL" power load to 1275.510 W
- Code: Select all
Z-Wave Debug RCVD requestMeterLevel: 01 14 00 04 00 1E 0E 32 02 21 74 00 13 5F 86 00 00 FD AA 00 3C 3B
Z-Wave Debug . . requestMeterLevel: node 030, endpoint None, meterType 01, raw value 7400...
Z-Wave Debug . . requestMeterLevel: 1269.638 W (float: 1269.638000)
Z-Wave received "Energy Meter - House - TOTAL" power load to 1269.638 W
And here are 2 examples of power load total reports for DSB28 Home Energy Meter G2 with firmware 1.8 and as you can see they are also properly parsed by Indigo:
- Code: Select all
Z-Wave Debug RCVD requestMeterLevel: 01 14 00 04 00 51 0E 32 02 21 74 00 00 58 E8 00 00 00 00 00 00 65
Z-Wave Debug . . requestMeterLevel: node 081, endpoint None, meterType 01, raw value 7400...
Z-Wave Debug . . requestMeterLevel: 22.760 W (float: 22.760000)
Z-Wave received "Energy Meter - Garage - TOTAL" power load to 22.760 W
- Code: Select all
Z-Wave Debug RCVD requestMeterLevel: 01 14 00 04 00 51 0E 32 02 21 74 00 00 59 22 00 00 00 00 00 00 AE
Z-Wave Debug . . requestMeterLevel: node 081, endpoint None, meterType 01, raw value 7400...
Z-Wave Debug . . requestMeterLevel: 22.818 W (float: 22.818000)
Z-Wave received "Energy Meter - Garage - TOTAL" power load to 22.818 W
However, moving over to the ENERGY reports now. Here are 2 examples of energy total reports for DSB28 Home Energy Meter G2 with firmware 1.5 and they are properly parsed by Indigo:
- Code: Select all
Z-Wave Debug RCVD requestMeterLevel: 01 14 00 04 00 1E 0E 32 02 21 64 00 03 50 13 00 3C 00 03 4F FD 47
Z-Wave Debug . . requestMeterLevel: node 030, endpoint None, meterType 01, raw value 6400...
Z-Wave Debug . . requestMeterLevel: 217.107 kWh (float: 217.107000)
Z-Wave received "Energy Meter - House - TOTAL" energy total to 217.107 kWh
- Code: Select all
Z-Wave Debug RCVD requestMeterLevel: 01 14 00 04 00 1E 0E 32 02 21 64 00 03 4F FD 00 3C 00 03 4F EC A7
Z-Wave Debug . . requestMeterLevel: node 030, endpoint None, meterType 01, raw value 6400...
Z-Wave Debug . . requestMeterLevel: 217.085 kWh (float: 217.085000)
Z-Wave received "Energy Meter - House - TOTAL" energy total to 217.085 kWh
BUT look now at the ENERGY reports for my DSB28 with the NEWER firmware version 1.8:
- Code: Select all
Z-Wave Debug RCVD requestMeterLevel: 01 14 00 04 00 51 0E 32 02 21 64 00 00 00 11 00 3C 00 00 00 11 F9
Z-Wave Debug . . requestMeterLevel: node 081, endpoint None, meterType 01, raw value 6400...
Z-Wave Debug . . requestMeterLevel: 0.017 kWh (float: 0.017000)
- Code: Select all
Z-Wave Debug RCVD requestMeterLevel: 01 14 00 04 00 51 0E 32 02 21 64 00 00 00 11 00 3C 00 00 00 11 F9
Z-Wave Debug . . requestMeterLevel: node 081, endpoint None, meterType 01, raw value 6400...
Z-Wave Debug . . requestMeterLevel: 0.017 kWh (float: 0.017000)
As you can see above the energy reports for firmware 1.8 are indeed received by Indigo but they are not parsed and reported back to the GUI for some reason?
Same problem is for the 3 individual clamps as well (endpoints 1 to 3) and only for the energy reports. Power load reports works fine for both total reports and individual clamp reports for both firmware 1.5 and 1.8.
I have emailed Aeon Labs (Aeotech support page: https://aeotec.freshdesk.com/support/home ) and asked for release notes and difference between firmware 1.5 and 1.8 but maybe you can already now see from the debug logs what is going wrong with the energy reports for firmware 1.8?