im trying to add more options to home assistant. for now it only knows 1 press action but i want it to have: double press, maybe triple and defently long press anyone have any ideas?

Hi everybody. I have a problem: I need to configure the KS868-E16st board so that the relays on it turn on according to the get request. I tried to use the code from this appeal: https://www.kincony.com/forum/showthread.php?tid=1927 But without result.
When compiling the code, the following error pops up:

invalid conversion from 'int' to 'eth_phy_type_t' [-fpermissive]

Maybe the problem is with the wrong board in the Arduino IDE?

Versions of my apps:
Arduino 1.8.19
Ethernet 1.1.2

I hope on your help!
Thanks

Hello KinCony Team.  My name is José. I live in Brazil.  I am a Computer Engineering and Data Science student.  If possible, I would like to obtain a KC868-A16 for educational purposes.  I am immensely grateful for your attention and willingness to contribute to the development of projects.  Kind regards, José.

IFTTT is set up to give my output port 1 an ON state, and when I press a momentary switch to input 1, output 1 turns OFF for ten (10S) seconds before turning back on. Using a 433MHz remote controller or my momentary switch, this function operates well. However, I am unable to access these input buttons through my Tuya mobile application when using it. Additionally, pressing output button 1 changes the state to ON/OFF, but it doesn't do it automatically (switching from On - OFF to ON after 10 seconds). How am I going to accomplish this? Furthermore, how can I use my hand to input data into the Tuya mobile application?

Please download the files from this link ( https://mega.nz/folder/4IUFxRYR#6rTauOgSxSSNAO6JqylFig )

2)  Also, kindly advise me on how to operate the KC868-A16 PCB using PC and mobile KBox software. Please outline the actions we must take to resolve it.

Regards

Hardware setup: Kincony MiniServer running homeassistant connected to kincony A6 board (slave) via RS485.

Created a Modbus-switch in the Mini Server yaml configuration pointing to relay 1 onto the A6 board.

Problem: when I switch on or off the modbus switch at home assistant sometimes the relay goes on or off immediately, sometimes after some seconds (<10 more or less). The dashboard at home assistant update the situation after some seconds (<10 more or less), not immediately.
Sometimes the relay is on but the dashboard show it off, and sometimes viceversa.

The more strange situation happen if I change the master of the modbus. I tried to use another A6 board as master and in this case all it's running ok and there are no delay. It's all immediate.

I made a video for better explain this. I don't want to abuse of this forum, so could I post the video here ?

In the mean time I attach my yaml files.
  configuration.pdf (Size: 32.4 KB / Downloads: 854)
  kc868-a6-exp3.pdf (Size: 36.64 KB / Downloads: 1504)

Hello Kincony,

I have been watching for some time your channel and really love what you did with the distribution box.

I would like your opinion on what's the best approach regarding automation for the following setup:

1 kitchen circuit for 32 amps 
11 outlets (16 amp circuit)
16 lightbulbs (10 amp circuits)
12 light switches
4 motion sensors
4 temperature sensors

I was looking at this distribution box - https://shop.kincony.com/products/16ch-r...t-node-red but i'm not entirely sure if it covers all my needs
Im planning to use this with home assistant and use alexa for voice command, and in the future i might install 5 automatic window blinds

Best regards

IFTTT is set up to give my output port 1 an ON state, and when I press a momentary switch to input 1, output 1 turns OFF for ten (10S) seconds before turning back on. Using a 433MHz remote controller or my momentary switch, this function operates well. However, I am unable to access these input buttons through my Tuya mobile application when using it. Additionally, pressing output button 1 changes the state to ON/OFF, but it doesn't do it automatically (switching from On - OFF to ON after 10 seconds). How am I going to accomplish this? Furthermore, how can I use my hand to input data into the Tuya mobile application?
Please find attached a web link (Please download to get the files) to get a video + jpeg file for my issue. 
(https://mega.nz/folder/4IUFxRYR#6rTauOgSxSSNAO6JqylFig).

Also, kindly advise me on how to operate the KC868-A16 PCB using PC and mobile KBox software. Please outline the actions we must take to resolve it.

Regards

Hello,

KC868-E16P is a great product, I love it!

I am almost finished connecting all my sensors and devices using ESPHome. 

Only remains 2 EZO sensors (1 device is pH, the other ORP). This is from Atlas Scientific:   EZO™ pH Circuit | Atlas Scientific (atlas-scientific.com)

I found this code on  EZO sensor circuits — ESPHome
- platform: ezo
  id: ph_ezo
  address: 99
  unit_of_measurement: "pH"
  update_interval: 10s

The device is connected to SDA / SCL.

Problem:
- Results from i2c bus scan doesn't detect the EZO sensor (I know the SDA / SCL ports are OK since I am able to detect an additional PCF8574 board for instance).
- While the device isn't detected, it is somehow interfering with ESP32 since I am seeing this in the logs:
                [W] [component: 157]: Component pcf8574 set Warning flag: unspecified
                [W] [component: 170]: Component pcf8574 cleared Warning flag

Questions:
- How to make my EZO sensor work please ?
- For my second  EZO sensor, should I connect it to the IC2 extender ?

Thank you.

Hi
please help, i didnt connect the KC868-A8 bord with arduino app.
When read information from board i receive the picture attached
   

   
   
the hair drier we tested, have two switch for different heat level. we found when MAX power, the signal from CT sensor is well, but when set to middle level, the signal from CT sensor is bad, fixed DC signal. so let the BL0910 energy meter chip lost some data, let the data incorrect, so in this case, should chose the CT sensor that can anti-DC signal version, just this CT sensor will be larger.
   
the signal is well, it's a sine wave.
   
   
the signal is bad, not sine wave.