B16M reboot when clicking individual switch

[mcroa]

Hi, i just want to report if this is a firmware problem or hardware problem. My order B16M was delivered last Jan 23, 2025.

So here are my findings:

(1) When I click "ALL on" and 'ALL Off", it works fine. ALL LEDs on B16M are working, all display on KCS 1-16 OUTS are green.
   


(2) But when I am clicking any of the 16 switches (1-16 OUTS), it reboots.
   

In the photo, I clicked OUT1, the RED LED on B16M lit, but the KCS firmware dont have color green as expected.

(3) Then after 3 seconds, the RED LED turned off then the board reboots it self. 
   

-I tried re-installing the KCS firmware, I deleted first the past flash.
-I removed my Tuya link.
- Disabled the MQQT

The board is now stand alone but still keeps rebooting whenever I press any of the 16 OUT switches on KCS firmware.

(4) The time NTP also not synching automatically even i set +8, and sync browser time, still from time to time it is displaying abnormal date and time.


If this is a hardware problem and cannot be solved by KCS firmware bug update, I have 15 days or until 6Feb2025 to dispute refund to ALIEXPRESS Official Kincony store.

Thank you.

[admin]

1. what KCS firmware you are using?
2. don't worry about the time, now we are during China New Year holidays. if hardware have issue, even >15 days of Aliexpress, we can also replace new one.

[mcroa]

1. what KCS firmware you are using?
-----Im usinng v3.4.0
2. don't worry about the time, now we are during China New Year holidays. if hardware have issue, even >15 days of Aliexpress, we can also replace new one.
---Im glad to here this. Happy new year Admin

But I think this is not a hardware problem, because i did this:

(1) I repeat the flashing, no MQQT, no Tuya linking, just a bare.
I open its IP at 192.168.4.1 as default, all 16 outputs are ok ok when i press, works normal.

(2) Then I set static IP, set to Static wifi mode IP, +8 utc, so far its working normal no problem.

(3) Then I link tuya and MQTT HA Auto discovery, at first 5 mins it ok., testing all button ok. Then after some short time suddenly it reboots again.
Then back to problem as stated in this thread (ALL ON and ALL OFF button on KCS are ok, but pressing individual switches it reboots)

( I disabled all automations on my home assistant just to test if this mqtt is the culprit)

The worst part are, when i disabled the MQTT of board to KCS and unlink my Tuya on my smart life account, the problem still present even Im back on my item(2) setup. Is it possible that a software problem embedded itself on the B16M board? Taka note that Im back to where I am at item no.2 where it is perfectly fine. Im confused what is wrong.

Admin, Please check why this problem exist. i will post my MQTT addon log on this thread

//This is the log of MQTT add on when I enable the 'MQTT for HA' at KCS web
2025-01-29 11:25:33: New connection from 192.168.0.54:57967 on port 1883.
2025-01-29 11:25:33: Client mqtt_D83BDXXXXXXX already connected, closing old connection.
2025-01-29 11:25:33: New client connected from 192.168.0.54:57967 as mqtt_D83BDXXXXXXX (p2, c1, k120, u'mqtt').


// When i click 'OUT1' of KCS web, the board reset/reboots. The following log file shows
2025-01-29 11:26:33: New connection from 192.168.0.201:54134 on port 1883.
2025-01-29 11:26:33: Client mqtt_D83BDXXXXXXX already connected, closing old connection.
2025-01-29 11:26:33: New client connected from 192.168.0.201:54134 as mqtt_D83BDXXXXXXX (p2, c1, k120, u'mqtt').
2025-01-29 11:26:34: New connection from XXX.30.32.2:55960 on port 1883.
2025-01-29 11:26:34: Client <unknown> closed its connection.

//I restarted the MQTT add-on
s6-rc: info: service legacy-services: stopping
2025-01-29 11:28:12: mosquitto version 2.0.20 terminating
time="2025-01-29T11:28:12+08:00" level=error msg="http request error: Post \"http://127.0.0.1:80/superuser\": dial tcp 127.0.0.1:80: connect: connection refused"
time="2025-01-29T11:28:12+08:00" level=error msg="http request error: Post \"http://127.0.0.1:80/acl\": dial tcp 127.0.0.1:80: connect: connection refused"
2025-01-29 11:28:12: Saving in-memory database to /data//mosquitto.db.
time="2025-01-29T11:28:12+08:00" level=error msg="Post \"http://127.0.0.1:80/superuser\": dial tcp 127.0.0.1:80: connect: connection refused"
[03:28:12] INFO: Service restart after closing
[03:28:12] INFO: Service restart after closing
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/mosquitto.sh
[11:28:19] INFO: Setting up user mqtt
[11:28:20] INFO: SSL is not enabled
cont-init: info: /etc/cont-init.d/mosquitto.sh exited 0
cont-init: info: running /etc/cont-init.d/nginx.sh
cont-init: info: /etc/cont-init.d/nginx.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun mosquitto (no readiness notification)
services-up: info: copying legacy longrun nginx (no readiness notification)
[11:28:21] INFO: Starting NGINX for authentication handling...
s6-rc: info: service legacy-services successfully started
[11:28:21] INFO: Starting mosquitto MQTT broker...
2025-01-29 11:28:21: Warning: Mosquitto should not be run as root/administrator.
2025-01-29 11:28:21: mosquitto version 2.0.20 starting
2025-01-29 11:28:21: Config loaded from /etc/mosquitto/mosquitto.conf.
2025-01-29 11:28:21: Loading plugin: /usr/share/mosquitto/go-auth.so
2025-01-29 11:28:21: ├── Username/password checking enabled.
2025-01-29 11:28:21: ├── TLS-PSK checking enabled.
2025-01-29 11:28:21: └── Extended authentication not enabled.
2025-01-29 11:28:21: Opening ipv4 listen socket on port 1883.
2025-01-29 11:28:21: Opening ipv6 listen socket on port 1883.
2025-01-29 11:28:21: Opening websockets listen socket on port 1884.
2025-01-29 11:28:21: mosquitto version 2.0.20 running
2025-01-29 11:28:21: New connection from ::1:60258 on port 1883.
2025-01-29 11:28:21: Client <unknown> disconnected due to protocol error.
2025-01-29 11:28:22: New connection from 192.168.0.199:60035 on port 1883.
[11:28:22] INFO: Successfully send discovery information to Home Assistant.
2025-01-29 11:28:22: New client connected from 192.168.0.199:60035 as 5xk7VcKZkIgoFpDVckNDM5 (p2, c1, k60, u'mqtt').
[11:28:23] INFO: Successfully send service information to the Supervisor.
2025-01-29 11:28:25: New connection from 192.168.0.54:54137 on port 1883.
2025-01-29 11:28:25: New client connected from 192.168.0.54:54137 as mqtt_D83BDXXXXXXX (p2, c1, k120, u'mqtt').
2025-01-29 11:28:34: New connection from 172.30.32.2:49446 on port 1883.
2025-01-29 11:28:34: Client <unknown> closed its connection.


//I press the another button 'OUT2' and still the b16M reboots
2025-01-29 11:29:49: New connection from 192.168.0.201:63693 on port 1883.
2025-01-29 11:29:49: Client mqtt_D83BDXXXXXXX already connected, closing old connection.
2025-01-29 11:29:49: New client connected from 192.168.0.201:63693 as mqtt_D83BDXXXXXXX (p2, c1, k120, u'mqtt').

[mcroa]

Hello Admin,

I found which causes the bug.

My set-up is working totally fine until i replace my A16 board to this B16M
These are my set up:
(1) Home Assistant in RPI
(2) B16M board
(3) Wifi ESP32 switches ( the purpose of this is wireless switch to bind to B16M switches thru HA automation)

So basically, my wifi switches are connected to router. Then I have automation in HA that if this switch entities are triggered, it will also trigger entity of B16M (MQTT HA auto discovery set-up) so that it will be updated to Tuya. So that I also monitor the state of switches even if I am outside my house. Here is my HA automation code, which is perfectly fine with both A16 and newly B16M.

alias: Dining light on - bind
description: ""
triggers:
- trigger: state
entity_id:
- switch.b16m_output02
- switch.dining_light_dining_light_output_1
from:
- "on"
- "off"
to:
- "off"
- "on"
conditions: []
actions:
- action: switch.turn_{{ trigger.to_state.state }}
metadata: {}
data: {}
target:
entity_id:
- switch.b16m_output02
- switch.dining_light_dining_light_output_1
- delay:
hours: 0
minutes: 0
seconds: 1
mode: restart


(4) Here is to trigger the bug, Go to Smart life app>b16m> click the switces (those who are binded to ESP wireless switces) FAST i mean Fast. on off on off on off.
Then boom, the board will reboot.

(5) The weird things is , even you unlink your b16M board to smart life and disable the MQTT, And put the B16m board as stand alone solo, the bug is embedded inside the board. Go to KCS, click any 16 siwthces, the board will reboot. There are times that I accidentally switch on off fast a smartlife tuya switches accidentally.

take note that this phenomenon is not present of my A16 board, until i upgraded to b16M because i want to voice command my entities.

Hope that this bug will be fixed on the next update of KCS firmware.
Thank you.