Yesterday, 07:31 PM
Greeting from Finland!
I just finished installation of my N60 yesterday and I got it sending data to my mqtt broker. Installation, upgrading the firmware and auto discovery worked flawlessly.
Overall great device and I have been looking for couple of years for a solution to monitor my entire electricity usage on fuse level. This is first reasonable product to do this.
Some basic information. I am using KCS V3 Firmware version v3.18.0. Connected with ethernet in my IOT VLAN. Monitoring three phase system with 3x16 fuses.
Power measurement appears to be reasonably accurate. I am using DL-CT03CL1.0 2000:1 current transformers. No Coefficients factors used for current power or energy.
I discovered some bugs in the MQTT integration.
N60 not sending energy (kwh) information in MQTT message:
Example Monitor1 Channel 8:
Home Assistant data
Data from Kincony webUI
MQTT data from MQTT Explorer
N60 is periodically sending kwh energy data but is not correct.
Incorrect state_class
Some of the measurement types have incorrect state class statement. Measurement is basically working but these entities cannot be used as Devices in
Home Assistant Energy dashboard. For power meter Energy dashboard assume device type: power and state class: measurement.
Currently N60 sends incorrectly:
unit_of_measurement: W
device_class: power
friendly_name: 3.1 Valo Keittiö Power
(state_class missing)
This is working example:
state_class: measurement
unit_of_measurement: W
device_class: power
friendly_name: EVSE 2 Total Power
There is a workaround to create helper entities from raw data from power sensor but this quite tedious to do 96 times for 48 channels (power and energy measurement).
Power Factor
Third observation is about power factor calculation. For some reason only one of six monitors are giving reasonable value. This is not usually super important in normal domestic
house as we are not charged for reactive power. For me this is interesting measurement as I run my house mostly battery powered and heat pumps generate quite a lot reactive power
and this strains inverters. It would be nice to know exact reactive power values. reference voltages match measured phases.
I am measuring L1 with monitor 1 and 2, L2 with monitor 3 and 4 and L3 with monitor 5 and 6.
Hopefully we can get these small bugs sorted out soon enough. Another possibility would be to use ESPHome but I really like the idea of this easy MQTT auto-discovery. So easy when
it works.
BR, Veikko Suihkonen
PS. My screen installation is kind of wonky. I see very little use for the screen anyway but I wonder what went wrong? Also, wifi is disabled on my N60. Software could be changed to show
"[Wifi] disabled" or something else on screen if it really is disabled. This could prevent some confusion in future.
I just finished installation of my N60 yesterday and I got it sending data to my mqtt broker. Installation, upgrading the firmware and auto discovery worked flawlessly.
Overall great device and I have been looking for couple of years for a solution to monitor my entire electricity usage on fuse level. This is first reasonable product to do this.
Some basic information. I am using KCS V3 Firmware version v3.18.0. Connected with ethernet in my IOT VLAN. Monitoring three phase system with 3x16 fuses.
Power measurement appears to be reasonably accurate. I am using DL-CT03CL1.0 2000:1 current transformers. No Coefficients factors used for current power or energy.
I discovered some bugs in the MQTT integration.
N60 not sending energy (kwh) information in MQTT message:
Example Monitor1 Channel 8:
Home Assistant data
Data from Kincony webUI
MQTT data from MQTT Explorer
N60 is periodically sending kwh energy data but is not correct.
Incorrect state_class
Some of the measurement types have incorrect state class statement. Measurement is basically working but these entities cannot be used as Devices in
Home Assistant Energy dashboard. For power meter Energy dashboard assume device type: power and state class: measurement.
Currently N60 sends incorrectly:
unit_of_measurement: W
device_class: power
friendly_name: 3.1 Valo Keittiö Power
(state_class missing)
This is working example:
state_class: measurement
unit_of_measurement: W
device_class: power
friendly_name: EVSE 2 Total Power
There is a workaround to create helper entities from raw data from power sensor but this quite tedious to do 96 times for 48 channels (power and energy measurement).
Power Factor
Third observation is about power factor calculation. For some reason only one of six monitors are giving reasonable value. This is not usually super important in normal domestic
house as we are not charged for reactive power. For me this is interesting measurement as I run my house mostly battery powered and heat pumps generate quite a lot reactive power
and this strains inverters. It would be nice to know exact reactive power values. reference voltages match measured phases.
I am measuring L1 with monitor 1 and 2, L2 with monitor 3 and 4 and L3 with monitor 5 and 6.
Hopefully we can get these small bugs sorted out soon enough. Another possibility would be to use ESPHome but I really like the idea of this easy MQTT auto-discovery. So easy when
it works.
BR, Veikko Suihkonen
PS. My screen installation is kind of wonky. I see very little use for the screen anyway but I wonder what went wrong? Also, wifi is disabled on my N60. Software could be changed to show
"[Wifi] disabled" or something else on screen if it really is disabled. This could prevent some confusion in future.