01-30-2025, 03:03 AM
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.
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.