Well, both WifiLED and WifiLED_n are acceptable, but people usually prefer to have WiFiLED_n set, because it's off when it's connected and people don't like extra distracting light. Still, the final choice is up to you.
Got it, yes, I prefer that too, like Tasmota! Good to know, I have some other devices which bother me, they have "flashlight" white LEDs. But this is at the (dark at night) entrance, so some guide light is good. Now it is quite bright, can I set it so it's just powered by the pullup?
Added after 6 [minutes]:
I immediately changed that setting for these units: https://www.elektroda.com/rtvforum/topic3958242.html They had annoyingly ultra bright light on all the time. Since that "WiFi" LED has "reversed" powering, it should be WiFiLED there. Maybe you can kindly fix that, too? Thanks!
Since that "WiFi" LED has "reversed" powering, it should be WiFiLED there.
Maybe you can kindly fix that, too?
Are you saying that I should swap the behaviour of two WiFi LED pin roles? Well, I am not sure. I already have a lot of users, and now swapping WifiLED_n with WifiLED would suprise everyone who does firmware update, don't you think?
This BK7231T has a strange MAC, ending in :00:00:00. It causes a few issues and I'm just wondering where that MAC came from, since its original MAC was not :00:00:00. I read a few things there but mostly refer to BL602. Is there a way to get the original MAC back? Should I reflash it with portions (?which) from the original dump in case other parameters are also missing? I did update it a few times OTA. Here is the original dump
Question: My device name ends with 00000, is it normal?
A: Device name is generated based on MAC, that would mean you have accidentally cleared your MAC, so see question below.
Question: I somehow lost my MAC address and I am unable to change it in Options! My MAC ends with 000000, how to fix?
A: You have most likely overwrote the TLV header of RF partition of BK7231. You might have done something wrong while flashing or/and done unnecessary 'Erase all' for the chip. The RF partition is normaly NOT overwritten when a device is flashed correctly, because it starts far after the end of OBK binary. For BK7231, we have a way to restore it - open Web App, go to Flash tab, and press 'Restore RF Config'. Note that removing original RF partition (which was already done, if you have 00000) may slightly reduce your device WiFi range and performance
Yes, thank you, I saw that note in the "Web App, Flash" "MAC ends with 00 00 00 and is unable to change bug", read about it in forums etc. also. It says it will replace it with a random MAC address. So I thought that maybe the RF data and MAC can be extracted from the dump I posted? I tried to look for the MAC with a hex editor but got nowhere, I think the first part of the current MAC is not correct also.
I got two of these and both had extremely low range out of the box, around 6m. Returned the other (uncracked) already, still waiting for the money back, xenon is a bad bad company. In any case, if you think the RF and MAC are not in the dump, will I then use your nice 00 00 00 repair tool. Thanks!
So I thought that maybe the RF data and MAC can be extracted from the dump I posted?
RF data can be indeed extracted from a backup file if you have it, but it would require some little manual work, we don't have a tool for that. It could be done even in Linux terminal I think. And indeed, using original RF calibration instead of a stub one is better for your WiFi range.
I would need to actually check myself what's the offset for that is.
Hi
as mentioned here
https://www.elektroda.com/rtvforum/topic4033215.html#21052330 after flashing to Build on Apr 3 2024 07:20:17 version 1.17.532 my precious autoexec etc files were gone!
It was a work in progress and I hadn't backed up those files yet.
"It's a recurring bug due to the OTA file size growing, we will update WebApp to have a warning or something"
"Autoexec.bat should work, just restore old script and it should be ok."
As mentioned, I cannot even get the simple btn_scriptonly going, what am I doing wrong?
Attached please find the files I tried to run plus a (cleaned) log.
I left one channel (pin24) with Btnand that works, the relay switches on and off.
But the other channel (pin10) with longpress etc and using "Btnscriponly" doesn't work.
It seems it cannot find "AllLights_off.bat"
Label // not found in AllLights_off.bat - will go to the start of file
but then
Info:CMD:CMD_StartScript: started AllLights_off.bat at label //
the log:
Info:GEN:24 Button_OnInitialPressDown
Info:GEN:24 key_short_press
Info:MQTT:Channel has changed! Publishing 1 to channel 1
Info:GEN:24 Button_OnInitialPressDown
Info:GEN:24 key_short_press
Info:MQTT:Channel has changed! Publishing 0 to channel 1
Info:GEN:10 Button_OnInitialPressDown
Info:GEN:10 Button_OnLongPressHoldStart
Info:GEN:10 Button_OnLongPressHold
Info:EVENT:EventHandlers_FireEvent: executing command startScript AllLights_off.bat // long pressing (2+ seconds) the button calls AllLights_off.bat
Info:CMD:Label // not found in AllLights_off.bat - will go to the start of file
Info:CMD:CMD_StartScript: started AllLights_off.bat at label //
Info:GEN:10 Button_OnLongPressHold
Info:EVENT:EventHandlers_FireEvent: executing command startScript AllLights_off.bat // long pressing (2+ seconds) the button calls AllLights_off.bat
Info:CMD:Label // not found in AllLights_off.bat - will go to the start of file
Info:CMD:CMD_StartScript: started AllLights_off.bat at label //
Info:GEN:10 Button_OnLongPressHold
Info:EVENT:EventHandlers_FireEvent: executing command startScript AllLights_off.bat // long pressing (2+ seconds) the button calls AllLights_off.bat
Info:CMD:Label // not found in AllLights_off.bat - will go to the start of file
Info:CMD:CMD_StartScript: started AllLights_off.bat at label //
Info:GEN:10 Button_OnLongPressHold
Info:EVENT:EventHandlers_FireEvent: executing command startScript AllLights_off.bat // long pressing (2+ seconds) the button calls AllLights_off.bat
Info:CMD:Label // not found in AllLights_off.bat - will go to the start of file
Info:CMD:CMD_StartScript: started AllLights_off.bat at label //
Info:GEN:10 Button_OnLongPressHold
Info:EVENT:EventHandlers_FireEvent: executing command startScript AllLights_off.bat // long pressing (2+ seconds) the button calls AllLights_off.bat
Info:CMD:Label // not found in AllLights_off.bat - will go to the start of file
Info:CMD:CMD_StartScript: started AllLights_off.bat at label //
Info:GEN:10 Button_OnLongPressHold
Info:EVENT:EventHandlers_FireEvent: executing command startScript AllLights_off.bat // long pressing (2+ seconds) the button calls AllLights_off.bat
Info:CMD:Label // not found in AllLights_off.bat - will go to the start of file
Info:CMD:CMD_StartScript: started AllLights_off.bat at label //
Info:GEN:10 Button_OnLongPressHold
Info:EVENT:EventHandlers_FireEvent: executing command startScript AllLights_off.bat // long pressing (2+ seconds) the button calls AllLights_off.bat
Info:CMD:Label // not found in AllLights_off.bat - will go to the start of file
Info:CMD:CMD_StartScript: started AllLights_off.bat at label //
Info:GEN:10 Button_OnLongPressHold
Info:EVENT:EventHandlers_FireEvent: executing command startScript AllLights_off.bat // long pressing (2+ seconds) the button calls AllLights_off.bat
Info:CMD:Label // not found in AllLights_off.bat - will go to the start of file
Info:CMD:CMD_StartScript: started AllLights_off.bat at label //
Info:GEN:10 Button_OnInitialPressDown
Info:GEN:10 key_short_press
Info:EVENT:EventHandlers_FireEvent: executing command startScript AllLights_on.bat // short pressing the button calls AllLights_on.bat
Info:CMD:Label // not found in AllLights_on.bat - will go to the start of file
Info:CMD:CMD_StartScript: started AllLights_on.bat at label //
Info:GEN:10 Button_OnInitialPressDown
Info:GEN:10 key_short_press
Info:EVENT:EventHandlers_FireEvent: executing command startScript AllLights_on.bat // short pressing the button calls AllLights_on.bat
Info:CMD:Label // not found in AllLights_on.bat - will go to the start of file
Info:CMD:CMD_StartScript: started AllLights_on.bat at label //
The discussion revolves around flashing the OTA (Over-The-Air) firmware on the Xenon SM-PW801-U2 dual in-wall outlet, specifically addressing issues related to low range and quality concerns with the device. Users share methods for flashing, including UART connections and the necessity of obtaining a 2MB flash dump for successful OTA updates. Various tools such as bk_writer and ltchiptool are discussed, with emphasis on using reliable methods to avoid bricking the device. The conversation also touches on extracting GPIO configurations and modifying button labels in the firmware. Additionally, users express frustrations with the manufacturer's support and the device's performance, while seeking solutions for programming multiple units without physical access. Summary generated by the language model.