logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

Query: Tuya Led Controller DC5-12v Compatibility with Cloudcutter Flash BK7321 and OBK Drivers

MnM1 6414 136
ADVERTISEMENT
Reply | New topic
  • #121 21100785
    p.kaczmarek2
    Moderator Smart Home  
    Did it start with HA update or with OBK update? If so, which version breaks?
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #122 21100801
    MnM1
    Level 10  
    I have one light on 1.17.596 and the others on 1.17.577 and they all behave the same.

    As for the HA version - no idea what was the last version that worked. All I can say for sure is that on version 2024.5.5 it works as described above.

    Edit: After the lights are toggled ON and they turn off, if I press the While Light Button (which enables the white light as per the script earlier) all lights are toggled ON. If I don't press the White Light the lights are not ON at all).

    Added after 1 [hours] 59 [minutes]:

    Just a follow up - I think before it was working as I had a smart switch and I was controlling the lights from the smart switch - so cutting power to the light and then turning on power via the smart switch.

    Now I have the lights always with power on and on the wifi and just need to toggle them. So when toggled they dont turn on any light.

    Added after 1 [hours] 11 [minutes]:

    Got the lights working again like this:

    Turn OFF Option 12
    Save
    Toggle on/off
    Turn ON Option 12
    Save
    Toggle on/off

    This somehow fixed the issues for all the lights.
    Wondering now if this is an mqtt issue rather than lights/ OBK or HA. Need to some research (run mqtt on a separate server, not as HA addon)
  • #123 21101688
    MnM1
    Level 10  
    @DeDaMrAz - all lights running 1.17.598 - BK7231N
  • ADVERTISEMENT
  • #124 21101953
    DeDaMrAz
    Level 19  
    @MnM1

    I'll have to check and report back, but to make it clear and for me to reproduce - If I toggle them from HA they will not work, is my understanding correct??
  • #125 21102752
    MnM1
    Level 10  
    Yes that is how they behaved for me - toggle from HA no lights turned on at all.
  • #126 21257131
    DeDaMrAz
    Level 19  
    Wow I 100% forgot about this, I apologize @MnM1 I will do this maybe this or the following weekend.

    We have a similar "problem" with another user and I was trying to refresh my memory and went back to this post.

    Sorry once again.

    Did you manage to find a solution to you problem in particular in our absence?
  • #127 21270442
    MnM1
    Level 10  
    I didn't find a solution for this.
    If you could have a look that will be great.

    Added after 2 [hours] 31 [minutes]:

    @p.kaczmarek2 - maybe a firmware bug? No fields displayed under configure startup.

    Screenshot of settings with information on initial pin values.
  • #128 21271206
    DeDaMrAz
    Level 19  
    I just checked on my end, updated my FW to latest and I can not replicate your problem. Is there anything else I can try, maybe different flags setup or different LFS? I'll attach mine for reference, but it work for me from HA. The only thing (I recall we never addressed it) is for some reason CW channels are transferred to HA but they don't work.

    EDIT: Flags active are: 1, 2, 10, 12, 20 and 43
    Attachments:
  • ADVERTISEMENT
  • #129 21272241
    DeDaMrAz
    Level 19  
    @MnM1

    I'll keep the lamp attached if you are willing to share your autoexec and some more details for me to try and replicate the problem and hopefully we can solve it for you somehow.

    Let me know.
  • #130 21272313
    p.kaczmarek2
    Moderator Smart Home  
    MnM1 wrote:

    @p.kaczmarek2 - maybe a firmware bug? No fields displayed under configure startup.

    Screenshot of settings with information on initial pin values.


    This topis seems very long, but isn't it a TuyaMCU device? Startup values on the screenshot are only for Relay channels in non-TuyaMCU setting.
    Helpful post? Buy me a coffee.
  • #131 21274775
    MnM1
    Level 10  
    >>21272313 Yes correct but they are missing. Would like to change the setting I have done a while ago but I cant anymore.

    Added after 1 [minutes]:

    >>21272241

    Sorry for the late reply.
    I have been away for the past 5 months and slowly getting back it it.
    I am testing again to see exactly what the symptoms are - will get back to you soon.
    Many thanks.
  • #132 21274776
    DeDaMrAz
    Level 19  
    MnM1 wrote:
    Yes correct but they are missing. Would like to change the setting I have done a while ago but I cant anymore.


    Let us know what you need and we will assist.

    Lamp is working as intended on my end so we will make yours work as well ;)
  • ADVERTISEMENT
  • #133 21274792
    p.kaczmarek2
    Moderator Smart Home  
    MnM1 wrote:
    >>21272313 Yes correct but they are missing. Would like to change the setting I have done a while ago but I cant anymore.

    What is your current pin config? Are you saying that you had non-TuyaMCU relays on your TUyaMCU device?


    You can always use: SetStartValue
    https://github.com/openshwprojects/OpenBK7231T_App/blob/main/docs/commands.md
    Helpful post? Buy me a coffee.
  • #134 21275249
    MnM1
    Level 10  
    >>21274792

    OK the first issue I was trying to sort with configure startup is for the light to be in the OFF position when the device reboots or the power is cycled on it.
    A few times I found the lights on during the day after there was a power cut to the house.
    I did try SetStartValue 0 0 or -1 but it doesn't work. I also have Flag 12 enable and the same result.
    It seems to remember the light color - if I pick blue and I give it a reboot it will turn on on blue.

    Second is not what I posted originally anymore. - either the OBK firmware since my post sorted it or HA updates did it.
    The light does turn on from HA.

    The enabled flags for me are:
    12, 27, 37, 43
    I have enabled 1, 2, 10 and 20 too, but it still turns on after a reboot.

    Thanks.
  • #135 21275570
    DeDaMrAz
    Level 19  
    @MnM1

    Ok, I found the source of the issue, we will have to work on it a bit, please be patient.

    EDIT: Quick and dirty way around it for now is to send the OFF command after the reboot, replace the header of your autoexec with this:

    Code: text Expand Select all Copy to clipboard
    startDriver TuyaMCU
startDriver httpButtons 
tuyaMcu_defWiFiState 4
tuyaMcu_setBaudRate 115200
tuyaMcu_sendQueryState
tuyaMCU_setupLED 24 1
delay_s 1
tuyaMcu_sendState 20 1 0


    Light will turn on for a second on reboot and go back to off state, upon MQTT connection it will update the state in HA (set flag 10 if not set for that)
  • #136 21276508
    MnM1
    Level 10  
    >>21275570

    Thanks - I will use the temporary fix until the issue can be sorted in the firmware so the light doenst come on at all.
  • #137 21307716
    MnM1
    Level 10  
    Hi @DeDaMrAz - any news on the firmware fix for these?
Reply | New topic
Report a violation of the law

Topic summary

The discussion revolves around the compatibility of a Tuya LED controller (DC5-12V) with Cloudcutter for flashing firmware on devices using BK7231 and OBK drivers. Users explore the feasibility of flashing the device, identifying the correct firmware version (N or T), and the potential for GPIO settings. The LED driver in question is identified as SM16703, with users attempting to control individually addressable LEDs. Various commands and configurations are tested, including the use of TuyaMCU for controlling LED states and colors. Issues with color mismatches and device behavior after power cycles are also addressed, with suggestions for workarounds and firmware updates to improve functionality. The community collaborates on troubleshooting and developing solutions for better integration with Home Assistant.
Summary generated by the language model.
Popular Topics
ADVERTISEMENT