Hi,

Are there any example yaml files for coding LoRa and the RS-485 connection for Home Assistant esphome?

Hi,
I'm about to buy my first KC868 module but I have some very basic questions. 

I had a tuya wifi relay board before and that created 13 switches which saturated my wifi network. If I flash esphome on this kc868 board will it create 16 switches on the network or just one device?

I need to have toggle switches able to control the relays and at the same time I want to be able control the switches from homeassistant. So if the toggle switch is on I still want to be able to turn the relay off. 
This means if the toggle switch is at off state and I turn the relay on remotely then changing the manual switch to on will do nothing because the relay is already on.

Thx!

I have started using the MB battery monitor, but I see Current & Power readings are much lower than my Victron SmartShunt.

Kincony Current: 2.7 A
Victron Current : 5 A.

16A version of Kincony MB

I am using the YAML referenced here: https://www.kincony.com/forum/showthread.php?tid=3975

Is there any tunings?   What is the expected accuracy of 16A MB ?

Attached Files

Image(s)
   

Hello,

Could I use a PSU 24VDC to supply power to kc868-a32 rev 1.4?

Thanks in advance

Regards

Nicolouts

Hi,

I am an electrician in Canada that dabbles in smart home equipment and programming.

I wanted to get better power consumption data into my Home Assistant and eventually settled on the N20.
The N20 has two voltage inputs so should be well suited to typical residential services in North America which are usually 120/240V split phase.
That is two hot lines, each 120 volts to neutral/ground but 240V between each other.

After getting the yaml provided on this forum installed I discovered a shortcoming when used in this fashion.

The N20 uses two BL0910 chips which each have 10 current transformer inputs and 1 voltage sensing input (1 BL0910 on the N10 and 3 on the N30 which would be good for 3-phase monitoring).
Each  BL0910  chip does calculations internally to provide watts and kWh but those calculations are done based on the single voltage input on each chip.

This is not a problem when one uses two current transformers, one for each hot line, but for a purely 240V load only a single current transformer is required.
Except the BL0910 chip calculates the watts based only on that single voltage input, 120V rather than 240V.

This yaml makes a few changes to tailor the firmware for typical USA/Canadian 120/240V residential services.

#1. Sensors have been renamed to aid readability.
bl0910_1_current_1 becomes CT1_1_Current
bl0910_1_power_1 becomes CT1_1_Power (or CT1_1_Power_HV when the power is based on a higher 240V circuit)
bl0910_2_power_1 becomes CT2_1_Power

The labelling on the outside of the unit lists CT1 to 11 and CT11-20 but I believe retaining the separation between BL0910 chip #1 and chip #2 is still important conceptually so went with CT1 1-10 and CT2 1-10.

#2 The renaming results in reordering of the entities in Home Assistant. Originally it would list currents 1-10, then watts 1-10, etc. Now all 3 sensors for each input is grouped and easily visible at a glance rather than scrolling 10 entries down.

#3 Reconfigured to use wifi rather than ethernet. Deleted unnecessary(?) text sensors for unused IP addresses.

#4 The OLED screen. Originally it only displayed the unit's IP address. 
Now it shows the IP address, Line 1 & 2 voltages, Line-to-line voltage, L1 watts and L2 watts.
For Line 1 & 2 watts I have CTs on my main panel feeder to get the whole house consumption. If you do not have CTs this could be changed to a specific load or commented out.

#5 This is one of the important ones. A sensor has been added that adds together voltage 1 and voltage 2 to get the Line-to-Line voltage. This is trivial to do with a helper in Home Assistant but having a dedicated sensor is nice and is also vital for the next change.

#6 I've added commented-out sections for each current sensor input that multiply the current by the Line-to-Line voltage for 240V loads using single current transformers.
Simply delete or comment out the original sensor entry for 120V loads and uncomment the 240V entry.
The new entities add "HV" to their name to indicate the watts are derived from 240V rather than 120V.

#7 At this time I have not looked into a way to fix the kWh sensors to accommodate 240V loads but I suspect it should be possible.
In the meantime I've added comments indicating the kWh sensors should be commented out if a single CT is used for a 240V load.
kWh tracking is also trivial in Home Assistant so I'm not in a hurry to figure this one out.

If anyone has feedback or modifications please share here.
Please give credit if my modified yaml is shared elsewhere. Thank you

Attached Files

Image(s)
   

  KinCony North America 120-240V split phase.txt (Size: 35.66 KB / Downloads: 230)

Hi, 

I have KC868-H16B relay.
What seems to happen is that Mqtt client stops listening to subscriptions after a while. 
I have ports 1-6 for lights, and port 16 for heating. 
Randomly, port 16 stops responding to mqtt state changes. 
Looking at the explorer, the set value is changed to 1 but state is not changed accordingly. This only affects port 16. ports 1-6 are still working. 
If I power cycle the relay, it's back to normal again. 
Version I'm running is H16B_V4.35. 
Any ideas? 


Thanks, 

Heikki

SetUp 

Board Model: T64M
Software Version: v3.18.0

DI1 = push button
DO1 = control lamp
DO2 = Pulse Start
DO3 = Pulse Stop
 
Output
Output DO2 Delay 0.5s
Output DO3 Delay 0.5s
 
IFTTT
1) If -> DI1 Rising Edge, and, DO1 OFF -> Then -> Toggle DO2 , DO1 ON
2) If _> DI1 Rising Edge, and, DO1 ON -> Then -> Toggle DO3, DO1 OFF

When I test the code via IFTTT by clicking "run," it works.
However, when I use my pushbutton DI1, output DO1 turns on and I get a pulse from DO2. 
This happens repeatedly, no matter how many times I press the button.
The output doesn't turn off when I press the button a second time.
It seems like the "If DO1 on" nor the "If DO1 off" is working.

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.
   

Need for mqtt code for cover shutter and water level

1. Introduction
Hello everyone,
I purchased the KC868-A16V3 controller and was genuinely impressed by its hardware capabilities. To explore its potential beyond smart home applications, I developed a fully functional OPC UA server as a proof-of-concept. This project transforms the A16V3 into a practical industrial OPC UA data gateway.
2. Project Overview & Features
This is a stable, working implementation that demonstrates the controller's ability to serve as an industrial communication node:

• OPC UA Server: Full server implementation based on open62541 and ESP-IDF.
  
• Hardware Support: Utilizes all core I/O of the A16V3:
  • 16 digital input/output channels (via integrated PCF8574).
    
  • 4 analog input (ADC) channels.
    
• Performance: Achieves consistent read times of less than 5ms per tag in testing.
  
• Real-World Validation: Successfully integrated and tested with an industrial SCADA system (Simple SCADA). Screenshots are attached below.
  
• Complete & Open: All source code is available, documented, and ready to be built upon.
  

• Primary Goal: To demonstrate that affordable, accessible hardware like the KC868-A16V3 can be effectively adapted for standard industrial protocols.
  
• Current Status: Stable proof-of-concept. All core functionalities are implemented, tested, and operational. The code provides a solid foundation for further development, pilot projects, or customization.
  
• Disclaimer: This is an open-source community project, not an official or commercial product from KinCony.
  

• GitHub Repository (Full Source Code): https://github.com/Aksurd/opcua-kincony-a16v3
  
• Direct Download: For users who may have difficulty accessing GitHub, I have attached the complete source code archive
  
  Code:

  forum-release.zip
  to this post. It contains all necessary files to explore and build the project.
  

• Potential improvements for reliability in industrial environments.
  
• Use cases for pilot projects or light automation tasks.
  
• Collaboration possibilities to enhance the ecosystem around KinCony hardware.
  

Attached Files

Thumbnail(s)
           

  forum-release.zip (Size: 772.63 KB / Downloads: 332)