logo elektroda
logo elektroda
X
logo elektroda

A success story: using a CB3S pogo pin jig with a Tuya Powerstrip, but with some questions

hartzell 375 1
ADVERTISEMENT
  • #1 21250825
    hartzell
    Level 7  
    *TL;DR*: I was able to use a jig to upload the OpenBK firmware to SM-SO301 style power strips, but the red LED seems to only track plug 1.

    ---

    A quick "success story" post.  I've been looking for updates to my ESP-based Xenon powerstrip and they all now seem to be using Tuya chips (3 for 3...).

    I wanted to avoid soldering, and particularly *desoldering*.  I'd hoped that I'd be able to use the TYWE3S jig that I've had success with on the CB3S, since the module dimensions are the same.   I was hopeful given @gcole's report  and was hoping to have better luck than @tlpektroda did.

    I spent a bunch of time being frustrated (there are some notes over in this topic) and finally settled into being systematic:

    - I convinced myself I was able to power the board by using probes to connect first an external supply and then the power pins from my UART, seeing LED 5 (near the buttons) light up red, then using the button to put the Tuya firmware into AP mode and seeing it in my WiFi list.
    - I found a pin on a chip that showed continuity to the gnd terminal on the module and discovered that it was *not* connecting to the pogo pin.
    - I stared at it a while, eventually noticing that the RF shield on the CB3s is smaller than the one on the TYWE3S and that kept the pins from lining up properly.

    I created a CB3S specific remix of the jig (ThingiversePrintables) that was a more accurate fit and thing's moved quickly.

    I was able to upload the most recent OpenBK code and stole the configuration from @gcole's post.

    Everything *almost* works.

    That leads me to an observation and a question:

    There seem to be a few differences between my two systems and @G-Code's. Here's his config:

    
      "pins": {
        "6": "Rel_n;2",
        "7": "Btn_Tgl_All;0",
        "8": "Rel_n;1",
        "10": "Rel_n;6",
        "14": "Rel;5",
        "21": "WifiLED;0",
        "23": "Rel_n;1",
        "24": "Rel_n;3",
        "26": "Rel_n;4"
      },
    


    1. He's defined two pins as "Rel_n;1", I think that the one on P23 is an error.
    2. He defined P10 as a "Rel_n", but it seems to be attached to a red LED.
    2. On my systems, Pin 21 needs to be "WifiLED_n;0" so that it lights up when the connection is established.

    That leaves me with one problem/question. Things work with this config:

    
      "pins": {
        "6": "Rel_n;2",
        "7": "Btn_Tgl_All;0",
        "8": "Rel_n;1",
        "10": "LED_n;0",
        "14": "Rel;5",
        "21": "WifiLED_n;0",
        "24": "Rel_n;3",
        "26": "Rel_n;4"
      },
    


    *but*, when I turn on Toggle 1 the red LED also turns on. If I leave P10 as a relay, I get a 6th button that controls the red LED. If I don't associate anything P10 then the red LED isn't used.

    I'm not sure how to get it to work as a power LED for the entire strip. Are my expectations off, or my config, or ?

    Thanks!
  • ADVERTISEMENT
  • #2 21251172
    p.kaczmarek2
    Moderator Smart Home
    Hello, I recognize this issue. This is by design, but you can get desired effect with a simple script. See related question:
    https://www.elektroda.com/rtvforum/topic4062580.html#21139966
    Adjust the number and indexes of used channels as needed.
    I think we may need to create a dedicated pin role for that soon so it's easier to configure without scripting, but for now, script should be enough...
    Helpful post? Buy me a coffee.
ADVERTISEMENT