logo elektroda
logo elektroda
X
logo elektroda

[bk7231n / cbu / mcu] Milfra MFA05F Motion Sensor Light Switch, teardown and dpId

gokeeper 2751 38
ADVERTISEMENT
  • #31 21224168
    roywalker777
    Level 3  
    >>21221857 Does anyone have a device with original firmware? We need to see what is being sent back and forth over the UART...
  • ADVERTISEMENT
  • #32 21243160
    DexEdson
    Level 4  
    >>21221857 My PIR sensor didn't work either until I played with the datapoints 101 and 102. Sometimes it just stops working again though and I have to reset
  • ADVERTISEMENT
  • #33 21243180
    divadiow
    Level 34  
    >>21156301

    can someone do this and post the file from their MFA05F please
  • ADVERTISEMENT
  • #34 21243224
    p.kaczmarek2
    Moderator Smart Home
    Maybe you need to script a dp 101 or 102 send (with required value - which one?) in autoexec.bat?
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #35 21296271
    amymariegerlach
    Level 5  
    Can someone help me please. I bought a couple of these switches to replace some cheap hubspace motion switches that were malfunctioning in my home. I successfully flashed openbeken onto the first one but I unchecked the auto config button in the easy UART flasher because I kept receiving errors, thinking I would be able to configure the device like I normally do with Tasmota devices, through the device access point. I have logged into the access point and configured my SSID info. I'm not really computer smart and don't know how or where to paste the data that is found in the beginning of this thread (dpIds, device status from tuya website, and autoexec.bat). I'm in the online app for my device and can view all of the different tabs but again don't know what to paste or where to put it to define this switch. I've found the template in screen shot 2 below but it looks like no pins or flags are transferring over and the device is still not configured even though I have "green" in the last photo.

    in case it matters...I did update to the newest firmware via OTA


    OpenBK7231N user interface with buttons for configuration, restart, and launching the web application. OpenBeken device configuration page with various settings. Screenshot of the Tuya device configuration interface.
  • #37 21300900
    amymariegerlach
    Level 5  
    Thanks for the link.

    OK, I got the autoexec.bat file pasted into the correct location and my switch has been partially configured (see 1st pict)

    User interface for configuring OpenBK7231N device.

    I say partially because the template still has all of the generic info and nothing showed up in the pins section (pict 2)

    Device configuration template with empty fields and Tuya chip identifier.

    Am I needing to insert the other two files from the first post, the dplds, and the device status from tuya website? If yes, where do they go?
  • #38 21305821
    p.kaczmarek2
    Moderator Smart Home
    You only need autoexec.bat. This is TuyaMCU device, so no pins are used except the UART1 port, which is used for MCU communication.
    Helpful post? Buy me a coffee.
  • #39 21313159
    psyko_chewbacca
    Level 6  
    Am I the only one that has reliability issues regarding PIR motion detection with these units?

    Whatever sensitivity setting I choose (Low, Med, High), the switch will sometimes (more often than not) take a very long time to toggle ON the relay.
    Switch is in a windowless room and light sensor is supposedly deactivated.

    Overall not a whole lot impressed, it kinda defies the purpose if I need to press the button to turn ON the light 75% of the time.

Topic summary

The discussion revolves around the Milfra MFA05F Motion Sensor Light Switch, which utilizes a CBU board and Tuya MCU. Users share their experiences with configuring the device, troubleshooting issues related to the motion sensor and relay functionality, and flashing the device with alternative firmware. Key solutions include configuring the MQTT server, setting local time for the PIR sensor to function correctly, and using specific commands in the autoexec.bat file to manage device states. Users also discuss challenges in flashing the device via serial connections and the need for proper data point configurations to enable the PIR sensor. The conversation highlights the importance of understanding the device's firmware and communication protocols for effective operation.
Summary generated by the language model.
ADVERTISEMENT