logo elektroda
logo elektroda
X
logo elektroda

[ESP8285] SE831L intelligent garage door controller - interior, analysis

p.kaczmarek2 3237 13
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
  • [ESP8285] SE831L intelligent garage door controller - interior, analysis
    I will present here a short analysis of the interior and the firmware change of the WiFi SE831L/GD-DC5 garage door controller advertised as Sonoff eWelink. As a standard, I will free it from the cloud, give the procedure for changing its firmware and configurations of its GPIO. This time the discussed driver will be based on ESP, so there will be a little change from what I usually show. I showed the driver based on BK7231 some time ago in the topic WiFi garage gate controller, Smart Garage Opener Tuya - Home Assistant , there I also provided an example YAML configuration for HA, I will not repeat it here.

    Purchase of the ECN SN kit
    The set was bought on a Polish auction site for about PLN 73:
    [ESP8285] SE831L intelligent garage door controller - interior, analysis
    Let's take a look at its description so you know what kind of product it is:
    [ESP8285] SE831L intelligent garage door controller - interior, analysis
    Assembly instructions:
    [ESP8285] SE831L intelligent garage door controller - interior, analysis
    [ESP8285] SE831L intelligent garage door controller - interior, analysis
    [ESP8285] SE831L intelligent garage door controller - interior, analysis
    [ESP8285] SE831L intelligent garage door controller - interior, analysis


    Received set
    Let's see what we get in practice:
    [ESP8285] SE831L intelligent garage door controller - interior, analysis [ESP8285] SE831L intelligent garage door controller - interior, analysis
    Everything is there, there is an opening sensor, there is a cable to connect the button, there is a USB cable for power supply, and the manual and the device itself are also present.
    [ESP8285] SE831L intelligent garage door controller - interior, analysis [ESP8285] SE831L intelligent garage door controller - interior, analysis [ESP8285] SE831L intelligent garage door controller - interior, analysis [ESP8285] SE831L intelligent garage door controller - interior, analysis [ESP8285] SE831L intelligent garage door controller - interior, analysis [ESP8285] SE831L intelligent garage door controller - interior, analysis
    How does such a controller even work?
    I already described this in the previous topic about the gate, there was a controller on CB3S (BK7231N):
    WiFi garage gate controller, Smart Garage Opener Tuya - Home Assistant

    The inside of the controller
    I skip the tests with the manufacturer's application, we immediately look inside. Just pry the cover up.
    [ESP8285] SE831L intelligent garage door controller - interior, analysis
    [ESP8285] SE831L intelligent garage door controller - interior, analysis [ESP8285] SE831L intelligent garage door controller - interior, analysis
    The ESP8285 is directly on the PCB here. There is also AMS1117-3.3V, because ESP requires 3.3V, and the input is 5V from USB. There is also a small SOIC8 chip inside, STC 15W104 H41U58 2241.XA. It is a microcontroller, core 8051.
    [ESP8285] SE831L intelligent garage door controller - interior, analysis
    Pinouts:
    [ESP8285] SE831L intelligent garage door controller - interior, analysis
    There is nothing interesting on the bottom of the PCB:
    [ESP8285] SE831L intelligent garage door controller - interior, analysis
    [ESP8285] SE831L intelligent garage door controller - interior, analysis
    [ESP8285] SE831L intelligent garage door controller - interior, analysis
    Based on the photos, I made a list of connections - it will also be useful for setting the Tasmota's GPIO:
    [ESP8285] SE831L intelligent garage door controller - interior, analysis
    Only that... if there is an additional MCU here, how can we set the GPIO? About that in a moment.

    Firmware change
    You can easily upload Tasmota here. RX and TX is available. The UART port is not occupied by the MCU, it is not a TuyaMCU device. This microcontroller is on a regular GPIO.
    GPIO0 is on the button, just press it before connecting the power.
    [ESP8285] SE831L intelligent garage door controller - interior, analysis
    [ESP8285] SE831L intelligent garage door controller - interior, analysis
    esptool.py works, as I have already described several times:
    https://www.elektroda.pl/rtvforum/topic3866386.html
    The only thing left is what about the MCU...
    My suggestion is to desolder it. First, we apply flux, then additional lead binder (we make bridges on its pins), and then we quickly heat both sides with a soldering iron. The layout can be removed after a while with tweezers:
    [ESP8285] SE831L intelligent garage door controller - interior, analysis [ESP8285] SE831L intelligent garage door controller - interior, analysis
    And that's it for now. Then it is enough to make jumpers and program the Tasmot IO, but more on that another time.

    Summary
    Changing the firmware turned out to be very simple. At first I was worried about GPIO0, but it turned out that this signal is brought out to the button, so there was no problem with putting the ESP into programming mode. I also had concerns about this mysterious MCU, but it turned out that you can desolder it and just freely use the ESP8285 IO and script it as we like in Tasmot / Home Assistant.
    I will try to show the configuration of the sensor itself, connecting it to the gate and a practical presentation soon, in a separate topic.
    Does any of the readers have such "intelligent" (whatever it means - this is the language of advertisers) garage doors controlled by WiFi? There are no problems with the WiFi range Before gate? Maybe I'm just too skeptical. I invite you to the discussion.

    Cool? Ranking DIY
    Helpful post? Buy me a coffee.
    About Author
    p.kaczmarek2
    Moderator Smart Home
    Offline 
    p.kaczmarek2 wrote 11949 posts with rating 9991, helped 572 times. Been with us since 2014 year.
  • ADVERTISEMENT
  • #2 20638735
    tmf
    VIP Meritorious for electroda.pl
    So, I'm curious about two things. The first - sense. According to the descriptions, it is connected to the gate drive. Generally, probably all drives come with a receiver and remote controls. So what does "smart" mean? Because controlling via the Internet in the case of a garage door seems to me to be more of a disadvantage than an advantage.
    The second question - security. In the event of a device break-in, the burglar has access to more than just turning a light bulb on/off. Considering how it works and the price, somehow I don't think safety is a priority here... But maybe I'm wrong?
  • #3 20638838
    p.kaczmarek2
    Moderator Smart Home
    I don't know if I'm the right person to answer the first question, because I'm interested in these gadgets from a technological point of view, and at home I mainly have "dumb switches" (read: "those that are not intelligent") and the SMART peak at in my workshop is to pair the LED strips above the window and under the cabinets with switch boxes (WiFi really makes it easier here, I use my own SendGet in OBK and Tasmota Device Groups emulation for LED lamps) and adding the option to choose the style of light (warm white / cold white) in home, but:

    tmf wrote:

    So, I'm curious about two things. The first - sense. According to the descriptions, it is connected to the gate drive. Generally, probably all drives come with a receiver and remote controls. So what does "smart" mean?

    Here I would see four potential advantages:
    - when we have one application for everything, there is no need to remember about many remotes, even in the case of several family members. Everything is in one place, lighting, cameras, door open sensors, and that titular garage. I have already seen the problem of many remotes at friends and family, then suddenly there is one remote control for LEDs above the "fireplace" (electric with animation), a second remote control for the fireplace, a third remote control for air conditioning, etc... Of course, this also has disadvantages, because what if there is no internet ...
    - if someone does not care about privacy, then it can also be connected to the voice assistant and open the gate, e.g. via Alexa
    - one ecosystem can have the potential to do some kind of automation like opening the gate turns on the lights or a PIR sensor opening the gate, although many of these examples are not that practical
    - I don't know how important it is, but it also gives us a log/log of who opened the gate when, etc., how useful it is depends on the situation and the device itself, there are also ordinary door opening sensors that can also give us such information

    However, what it looks like in practice and how often it is used by real users is probably only known by the manufacturer of these gadgets that tracks and collects data, they undoubtedly collect some analytics and probably very rich, knowing life with everything you can, you would have to check what Android Permissions their app gets.

    tmf wrote:

    The second question - security. In the event of a device break-in, the burglar has access to more than just turning a light bulb on/off. Considering how it works and the price, somehow I don't think safety is a priority here... But maybe I'm wrong?

    Absolutely everything that is connected to the Internet is always exposed to access by third parties and should be treated as such. Even those "private" posts or conversations on Facebook, or "private" files on Dropbox or Google Drive may at any time, even as a result of human error, become public for some time.
    However, focusing on the device itself from the topic, it would be worth considering first whether we are talking about the version before the firmware change or after the firmware change?

    If after changing the firmware, it's probably best to just link this article:
    https://tasmota.github.io/docs/Securing-your-IoT-from-hacking/
    The above article describes potential attacks and how you can try to protect yourself against them.

    If before the change, it's hard to comment on anything else, because the manufacturer's original software is closely related to the cloud and we can never be sure if there is any vulnerability on their servers, at least one unsecured API point, e.g. allowing anyone without logging in to control all devices by their ID or something...

    All in all, I can add this, regarding this security, that I have repeatedly downloaded batches from such devices on ESP8266 / ESP8285 and on BK7231 and I saw that both SSID and WiFi network password can be recovered from them.

    By the way, the tuya-convert itself for BK7231 works based on... the usual C buffer overflow in the Tuya software and it allows you to upload your own batch to the BK7231 without opening the case (if someone previously obtained function offsets for the firmware build of this device), and this already says something about the Tuya safety standard. If they didn't even secure the buffers in their code, it's scary to think what lurks in the server and cloud software.
    Helpful post? Buy me a coffee.
  • #4 20639001
    tmf
    VIP Meritorious for electroda.pl
    Thanks for the info. I actually think the same about it. I am not talking about the general benefits of home automation, but about this particular device. As you wrote, originally it is strongly related to the cloud, so probably whatever it is possible, the producer logs in and does what he wants with it. I think it's worth making the users aware of it. Ideas for including Alexa and similar solutions are IMHO completely off the top. Of course, someone will say - I will be able to give voice commands, but ... we have zero privacy, everything we say goes to the company, and the company does what it wants with it. The question is, do we agree to constant surveillance at the price of unnecessary facilitations? Even if we do, we must be aware that if we do not like the company, our account will be banned and we will not even leave this garage - this is not a hypothetical scenario, because it is already happening. Ew. another version - today it's pretty much free (or rather because we allow ourselves to be eavesdropped and peeked), and when they smell blood, it suddenly turns out that the device requires a subscription to continue working...
    IMHO, if you force pack automation everywhere, then only under the condition:
    - we change the batch to something we trust somehow (open source),
    - absolutely no cloud,
    - also works when the net fails.
    Since self-replacement of firmware is beyond the capabilities of most users, it is all the more important to make the public aware of the risks associated with such devices, the restriction of freedom and privacy, as well as the introduction of solutions through the back door that normally no one would agree to, e.g. subscription models, in of which we have a physical device, but we do not really own it, because the manufacturer can limit its functionality at any time or simply turn it off.
  • ADVERTISEMENT
  • #5 20639273
    ArturAVS
    Moderator
    tmf wrote:
    originally it is strongly connected with the cloud, so probably whatever it is possible, the producer logs in and does what he wants with it. I think it's worth making the users aware of it.

    After all, the situation is almost identical with other devices, e.g. CCTV IP cameras. Unfortunately, people wanting to make their lives easier forget about their own privacy.
  • #6 20639672
    krzbor
    Level 27  
    What was that MCU 8051 there for? ESP will easily handle the reed switch and relay.
  • #7 20639748
    p.kaczmarek2
    Moderator Smart Home
    @tmf I am against all kinds of subscriptions, even those for VOD services, although at the same time I see (even from family members) that some people wouldn't manage without them. A much bigger problem is with subscription software, with software that requires the Internet to work, although it shouldn't need it, with pushing subscriptions wherever possible (where have I seen material about a subscription printer?), and with manufacturers, for example, secretly replacing lifetime subscription licenses:




    @krzbor I'm already used to this type of quirks. Below is a photo of an ordinary MiBoxer WL_SW1 smart relay based on the WiFi CB2S module and an external MCU controlling the button and relay, where the MCU communicates with the WiFi module via the TuyaMCU protocol.
    [ESP8285] SE831L intelligent garage door controller - interior, analysis [ESP8285] SE831L intelligent garage door controller - interior, analysis [ESP8285] SE831L intelligent garage door controller - interior, analysis [ESP8285] SE831L intelligent garage door controller - interior, analysis
    Why is there an external MCU connected to the WiFi module via UART (TuyaMCU operates on UART)? Unfortunately, I do not know.
    Helpful post? Buy me a coffee.
  • #8 20639759
    William Bonawentura
    Level 34  
    Does the manufacturer warn in the manual about the legal risk of installation? The motorized gate is not a toy and must comply with the requirements of the Machinery Directive. As long as it was controlled locally with a remote control, the operator had supervision over its movement and it did not require additional protection with curtains or pressure sensors. After installing the "over the Internet" control, the status will change.
  • #9 20643936
    noel200
    Level 27  
    I attached a small magnet to the gate, and next to the gate I screwed a yunshan plate with a reed switch at the entrance. I have in the app whether the gate is closed. Unfortunately, I often forget "did I close the gate or not?" Sometimes even the remote button is pressed accidentally in a purse or pocket and the gate opens. I fire up the app and see. But that's just reading. I didn't hook up the controls. Still. No one has time to help me, and I'm in a wheelchair and I can't reach the drive under the ceiling. But if I could, I would. Then when I see that the gate is open and no one is home, I could close it remotely. The security problem then unfortunately becomes serious. Though it's nothing to steal from me.
  • ADVERTISEMENT
  • #10 20644291
    metalMANiu
    Level 21  
    I have 2 garage doors with an electric drive and control with a 433MHz remote control. Half a year I couldn't find time to connect some "Smart" switch to it.
    Once I found the time and sat down, I thought calmly, then I concluded that in terms of safety, this is a poor idea.
    I am currently using Tuya to control small lighting at home (rather for fun than real functionality) and it happens very often that the relay on/off indicator in the application has the opposite state than in reality.
    If I had to install something similar, it would be only with real-time camera preview (although even these can disconnect for no reason ...)
  • #11 20646858
    borba
    Level 15  
    >>20638623
    I have the exact (or very similar) model.
    And it's been working for a year now.
    Because the backyard garage is built of concrete walls about 15 cm thick, unfortunately, it was necessary to add a repeater to the existing WiFi router/modem.
    Previously, there were problems with maintaining the connection, now (for about 10 months) nothing like this is happening.
    The eWeLink app allows you to open/close/check the status of the gate from any location.
    More irritating is the lack of operation of the eWeLink application in my car (with the old Android 4.0.4), because the Chinese probably modernized the soft and at the moment the application prevents logging into the account.
    There are no such problems with a smartphone, but you have to use it instead of tapping the big button on the car console screen.
  • ADVERTISEMENT
  • #12 20647193
    metalMANiu
    Level 21  
    @borba and isn't this Ewelink based on Tuya?
  • #13 20647195
    borba
    Level 15  
    I don't know anything about it.
    From what I've read (I'm just an amateur, that's why I haven't uploaded my own software to the WiFi controllers that I have with 9 at home yet), eWelink does not need a central (hub) connecting everything into one.
    The principle of operation of these devices is individual connection to the WiFi network, not through a control panel.
    So the whole eWelink works for me only synchronized with the home WiFi network.
    Regards
  • #14 21508733
    Perelka
    Level 15  
    Hi I have been a user of a number of Sonoff units around the house for several years. Mainly the Mini R2 but also three of the same as in the subject for the gates in the garages and the entrance gate. I have Sonoff cameras in the garages so I have a view of the garage when opening. I very often open for couriers to leave packages. In addition, there is monitoring of the cameras outside. Since updating the software in these Sonoffs for the gates to the latest 3.6.0, at the entrance gate I have a problem with opening using the remote control. The Sonoff receives a signal from the contracton during opening and unfortunately emits a signal at the output so that the gate stops after opening for several cenimetres. This was not the case before.Only I use sonoff because I have Android Auto. My wife uses the remote control and this is troublesome. Because after opening when it stops you have to trigger it again and stop it so it doesn't close all the way and reach the sensor. After this, the opening goes correctly because the sonoff no longer has a change of state on the contracton and does not issue an output signal unnecessarily. Garage doors do not have this problem....

Topic summary

The discussion revolves around the SE831L/GD-DC5 garage door controller, marketed as Sonoff eWelink, focusing on its firmware modification and the implications of using such a device. Users express concerns regarding the practicality and security of smart garage door controllers, particularly the risks associated with cloud dependency and potential privacy invasions. The conversation highlights the advantages of integrating multiple smart devices into a single application, but also raises alarms about the lack of user control and the possibility of surveillance. Technical inquiries about the device's components, such as the MCU and its functionality, are also addressed, alongside personal experiences with connectivity issues and the need for additional hardware like WiFi repeaters. The eWeLink app's limitations and its operation without a central hub are discussed, emphasizing the need for awareness regarding the legal and safety implications of remote-controlled garage systems.
Summary generated by the language model.
ADVERTISEMENT