v3.22.0 improvement:
1: add "import" and "export" function for backup.
2: fixed bug copied IR command can't send out issue.
   

Attached Files

  KCS_A6V3_V3.22.0.zip (Size: 1.08 MB / Downloads: 61)
  KCS_A2V3_V3.22.0.zip (Size: 1.11 MB / Downloads: 49)
  KCS_A8V3_V3.22.0.zip (Size: 1.13 MB / Downloads: 55)
  KCS_A16V3_V3.22.0.zip (Size: 1.15 MB / Downloads: 72)
  KCS_A32PRO_V3.22.0.zip (Size: 1.11 MB / Downloads: 49)
  KCS_AG8_V3.22.0.zip (Size: 1.09 MB / Downloads: 50)
  KCS_AIO_HYBRID_V3.22.0.zip (Size: 1.32 MB / Downloads: 52)
  KCS_ALR_V3.22.0.zip (Size: 1.08 MB / Downloads: 85)
  KCS_B4_V3.22.0.zip (Size: 1.14 MB / Downloads: 53)
  KCS_B4M_V3.22.0.zip (Size: 1.14 MB / Downloads: 49)
  KCS_B8_V3.22.0.zip (Size: 1.14 MB / Downloads: 48)
  KCS_B8M_V3.22.0.zip (Size: 1.14 MB / Downloads: 42)
  KCS_B16_V3.22.0.zip (Size: 1.14 MB / Downloads: 51)
  KCS_B16M_V3.22.0.zip (Size: 1.14 MB / Downloads: 49)
  KCS_B24_V3.22.0.zip (Size: 1.14 MB / Downloads: 39)
  KCS_B24M_V3.22.0.zip (Size: 1.14 MB / Downloads: 54)
  KCS_B32M_V3.22.0.zip (Size: 1.14 MB / Downloads: 62)
  KCS_DM16_V3.22.0.zip (Size: 1.11 MB / Downloads: 49)
  KCS_F4_V3.22.0.zip (Size: 1.13 MB / Downloads: 58)
  KCS_F8_V3.22.0.zip (Size: 1.13 MB / Downloads: 50)
  KCS_F16_V3.22.0.zip (Size: 1.14 MB / Downloads: 62)
  KCS_F24_V3.22.0.zip (Size: 1.14 MB / Downloads: 54)
  KCS_F32_V3.22.0.zip (Size: 1.14 MB / Downloads: 65)
  KCS_G1_V3.22.0.zip (Size: 1.1 MB / Downloads: 47)
  KCS_KC_TA_V3.22.0.zip (Size: 1.09 MB / Downloads: 53)
  KCS_N10_V3.22.0.zip (Size: 1 MB / Downloads: 52)
  KCS_N20_V3.22.0.zip (Size: 1 MB / Downloads: 48)
  KCS_N30_V3.22.0.zip (Size: 1 MB / Downloads: 54)
  KCS_N60_V3.22.0.zip (Size: 1.02 MB / Downloads: 49)
  KCS_T16M_V3.22.0.zip (Size: 1.09 MB / Downloads: 55)
  KCS_T32M_V3.22.0.zip (Size: 1.11 MB / Downloads: 50)
  KCS_T64M_V3.22.0.zip (Size: 1.11 MB / Downloads: 46)
  KCS_T128M_V3.22.0.zip (Size: 1.11 MB / Downloads: 47)
  KCS_TR_V3.22.0.zip (Size: 1.06 MB / Downloads: 47)
  KCS_Z1_V3.22.0.zip (Size: 1.24 MB / Downloads: 45)

Could You consider making ESP32-S3 LED dimmer module but not with 0-10V outputs (like DM16), but MOSFET with PWM Analog Outputs?

0-10V is great, but it makes everything more complicated when I just want to dimm multiple individual LEDs from single DC source - additional multiple dimmable drivers etc.

We have nice product from Polish manufacturer - boneIO ESP DImmer LED gen 2 with 8x PWM outputs. It costs 110$ and is great, I just wanted to have all from Kincony and cannot find anything like this

https://store.boneio.eu/product/boneio-d...8404204e3d

Please consider making product like this. I think it will be very popular on the Polish market (this boneIO is almost always sold out).

Thanks!

I'm trying to hook up an SHT30 sensor to the I2c connector and from what I'm reading the default address is 0x44 (or 0x45) but I'm not getting an readings on the monitor page when set that way (after I add it in the sensor page). Is there any way to scan the I2c bus within KCS V3 so determine the address for certain ?

Also I assume the sensor address on the sensor page its looking for the last 2 numbers of the address as 0x44 does it save correctly, its wiped out after save, but I can type 44 and save without issues ?

Thanks in advance for any assistance,
Rich

home assistant OS command line, input command:
ls /dev/i2c-*
then will show i2c dev as this photo.
   

In the root of the hassos-boot partition, add a new folder called CONFIG.
In the CONFIG folder, add another new folder called modules.
Inside the modules folder add a text file called rpi-i2c.conf with the following content:
i2c-dev

In the root of the hassos-boot partition, edit the file called config.txt at last add two lines to it:
dtparam=i2c_arm=on
dtoverlay=i2c1-pi5,pins_2_3
   

restart home assistant.

how to check whether have enabled i2c bus for home assistant, see here: https://www.kincony.com/forum/showthread.php?tid=9075

1: install "SSD1306 I2C Display for Home Assistant" component:

HACS (Recommended)
  1. Open HACS in your Home Assistant instance
  2. Click on "Integrations"
  3. Click the three dots in the top right corner
  4. Select "Custom repositories"
  5. Add this repository URL: https://github.com/hzkincony/hass-ssd1306
  6. Select category: "Integration"
  7. Click "Add"
  8. Find "SSD1306 I2C Display" in HACS and click "Download"
  9. Restart Home Assistant

Manual Installation
  1. Clone or download this repository
  2. Copy the custom_components/ssd1306_i2c directory into your Home Assistant custom_components folder
  3. Restart Home Assistant

2: Test: home assistant "Settings" -- "Developer tools" -- "Actions" search "print text"
   
select "ssd1306_i2c.print_text" action, set the X, Y, Text, Font size , then click "Perform action" to show in OLED display.
   
   

3: note: make sure your CM5 have enabled i2c bus.
how to enable CM5 i2c bus, see here: https://www.kincony.com/forum/showthread.php?tid=9074

KinCony Pi5 is a Raspberry Pi CM5 server for smart home automation and industrial automation control. It can use for home assistant local server. It's a Linux computer, you can install software by yourself, such as Node red. The product default CM5 version is CM5004000. It without Bluetooth and wifi, RAM:4G Lite version.

Model No. KinCony Pi5
Description: KinCony Automation Local Server – Pi5
Power supply: 12-24V DC
Processor: Raspberry Pi Compute Module 5
Size: 146mm*83mm*56mm
interfaces: Ethernet(RJ45)-LAN 1000Mbps IPv4/IPv6,USB-C
Installation method: DIN RAIL
2 × USB 3 sockets
microSD card socket for CM5 Lite modules
M.2 M key PCIe socket
1 × full-size HDMI 2.0 connectors
DIP SWITCH for jumpers
SSD1306 i2c OLED displayer
CM5 GPIO extender

Order bundles:
Bundle A: Pi5 without CM5 + heatsink + fan
Bundle B: Pi5 with CM5(CM5004000):RAM:4G-Lite + heatsink + fan




here is CM5 free GPIOs for user.

Hello,

There are 2 issues with the documentation of the 4 dip switches to set the slave ID on the bus.
Let's call, from left to right, the 4 dip switches respecively A0 A1 A2 A3.

1/ 
The documentation mentions that when A3 is in OFF state, this means the outputs are controlled by the input terminals (and when in ON state, it is controlled by MODBUS).
It is actually the reverse: When A3 is in OFF state, the device is controlled by MODBUS.

2/
The documentation specifies that when identifying the slave id, the value of the slave id is:  (A0 * 1  + A1 * 2 + A2 * 4) + 10.
so: A0=ON A1=OFF A2= OFF should give  slave ID  (1 * 1 + 0 * 2 + 0 * 4 ) + 10 = 11 (according to the table in the documentation)

It is actually the reverse: from trials/errors, the formula to apply seems to be (A0 * 4 + A1 * 2 + A2 * 1) + 10
so: A0=ON A1=OFF A2= OFF is, in reality slave ID  (1 * 4 + 0 * 2 + 0 * 1 ) + 10 = 14 (from experience).

Hello,

I have 2 E16V3 installed as 2 different slaves on the same modbus.

When I send a command to each in isolation, I  receive a response within a few milli-seconds from the E16V3.

But when I send a command to the second E16V3 immediately after successful response from the first one, then I never receive the response from the second device.

It seems that the second E16V3 is puzzled by the activity on the bus that is not intended to himself.

I have to retry the command to the second E16V3, or wait (20 miliseconds for example) before sending the command to the second E16V3

I can help troubleshooting further if needed.

BRs,

Laurent