Just received some LSPA9's but they come along now with WL2S (Lightning LN882HK) wifi/ble modules.
See also Support for WL2S module (Lightning LN882HK chip)
See also Support for WL2S module (Lightning LN882HK chip)
Czy wolisz polską wersję strony elektroda?
Nie, dziękuję Przekieruj mnie tam
They were working via LocalTuya integration, and one day one of them stopped to work (no wifi connection, no reaction on button). I supposed it to be dead, but I found your thread about OpenBeken, so decided to give it a try. Soldered wires, updated firmware and voila, it is alive again
Today's topic - I noticed that after restarting HA (or reloading the MQTT integration), the "buttons" connected to the dashboard via OpenBeken sockets do not work. You can click as much as you want, it does not turn on the relay. After entering MQTT integration and displaying the properties, switching on the relay looks like this:
{
"sel_pin_pin":"24",
"rl1_lv":"1",
"bt1_pin":"10",
"net_trig":"4",
"jv":"1.0.5",
"netled1_lv":"0",
"netled_reuse":"0",
"bt1_type":"0",
"ffc_select":"0",
"nety_led":"1",
"vi_pin":"6",
"resistor":"1",
"over_cur":"30000",
"bt1_lv":"0",
"reset_t":"5",
"netled1_pin":"8",
"chip_type":"0",
"lose_vol":"90",
"over_vol":"265",
"module":"CB2S",
"ele_pin":"7",
"ch_cddpid1":"9",
"ch1_stat":"2",
"rl1_type":"0",
"ch_num":"1",
"ele_fun_en":"1",
"rl1_pin":"26",
"netn_led":"0",
"vol_def":"0",
"ch_dpid1":"1",
"sel_pin_lv":"1",
"crc":"101",
"}SyNAgw_di{abi":"0",
"id":"null",
"swv":"1.1.15",
"bv":"40.00",
"pv":"2.2",
"lpv":"3.4",
"pk":"keyjup78v54myhan",
"firmk":"keyjup78v54myhan",
"cadv":"1.0.5",
"cdv":"1.0.0",
"dev_swv":"1.1.15",
"s_id":"null",
"dtp":"0",
"sync":"0",
"attr_num":"1",
"mst_tp_0":"9",
"mst_ver_0":"1.1.15",
"mst_md5_0":"null",
"mst_tp_1":"0",
"mst_ver_1":"null",
"mst_md5_1":"null",
"mst_tp_2":"0",
"mst_ver_2":"null",
"mst_md5_2":"null",
"mst_tp_3":"0",
"mst_ver_3":"null",
"mst_md5_3":"null } )MAgw_wsm{nc_tp",
"ssid":"null",
"passwd":"null",
"md":"0",
"random":"0",
"wfb64":"1",
"stat":"0",
"token":"null",
"region":"null",
"reg_key":"null",
"dns_prio":"0 }{uuid",
"psk_key":"Rw2qljrrRdPptlRhoqAwKsiN9cLTPsspSfuaI",
"auth_key":"ysA8AJ4BOFfyYn6quSGuGBhYIWRdiw3s",
"ap_ssid":"SmartLife",
"ap_passwd":"null",
"country_code":"null",
"bt_mac":"null",
"bt_hid":"null",
"prod_test":"false",
"fac_pin":"ddms3xyc8sfctabe }3VAwf_start_mdll"
}
maczekg wrote:They were working via LocalTuya integration, and one day one of them stopped to work (no wifi connection, no reaction on button). I supposed it to be dead, but I found your thread about OpenBeken, so decided to give it a try. Soldered wires, updated firmware and voila, it is alive again
minusync wrote:maczekg wrote:They were working via LocalTuya integration, and one day one of them stopped to work (no wifi connection, no reaction on button). I supposed it to be dead, but I found your thread about OpenBeken, so decided to give it a try. Soldered wires, updated firmware and voila, it is alive again
Exactly the same thing happened to me a couple of days ago with BL0937 version. This was really strange because when I did try to read it with BK7231Flasher I got CRC mismatch error and also was unable to read OBK configuration. But flashing with OB was without any problems and after some setup troubles, it is now fully functional again.
minusync wrote:
I have also some questions to p.kaczmarek2 if he happens to read this.
Is it still needed to "to save your BL0942 init and calibration constant setting commands in LittleFS or startup command " as described in the first post?
minusync wrote:
Can I save the button state after a power outage? I have not found any settings for that. Maybe I missed something.
p.kaczmarek2 wrote:I have never heard yet about CRC error in BK7231 GUI flasher. It happens in HID_download_py because of the wrong algorithm implementation, but not in my flasher. Did it happen every time you read?
p.kaczmarek2 wrote:You can use our docs to check the latest state of c ommands:
minusync wrote:
Since it is obviously now possible to perform calibration in the webapp, c commands are not directly necessary for this. The point of the question was rather whether the calibration made in the web app is preserved after the device restart?
Quote:
Measure the real voltage with an external, reliable power meter and enter this voltage via this command to calibrate. The calibration is automatically saved in the flash memory.
p.kaczmarek2 wrote:Yes, I answered you in the previous post. Please open this screenshot from the documentation:
sensor:
- platform: mqtt
name: "BL0937 Energy_yesterday"
state_topic: "obk68191C68/energycounter_yesterday/get"
unit_of_measurement: "Wh"
- platform: mqtt
name: "BL0937 Energy_today"
state_topic: "obk68191C68/energycounter_today/get"
unit_of_measurement: "Wh"backlog startDriver BL0937; StartDriver NTP; PowerSave 1; ntp_setServer 192.168.1.1; ntp_timeZoneOfs +1; SetupEnergyStats 1 60 5;
TL;DR: Switching BL0942 to 9 600 baud restored “100 % of readings” and cut error to <2 % on CUCO-Z06-N plugs [Elektroda, Wimmi, post #20957896] “The driver began showing voltage instantly” [Elektroda, uchristo, post #20936194] Why it matters: one baud-rate tweak turns unusable CB2S/BL0942 sockets into reliable 2 200 W power monitors.
• Max load LSPA9/EP2 clones: 2 200 W @ 230 V [Elektroda, Dark Man, post #20349891] • Default BL0942 UART speed: 4 800 baud; many new boards ship at 9 600 baud [Elektroda, Wimmi, post #20957896] • BL0937/BL0942 calibration kept in flash after VoltageSet/CurrentSet/PowerSet cmds [OBK docs]. • MQTT broadcast interval adjustable: 5 – 3 600 s via mqtt_broadcastInterval [OBK cmds]. • Safe-mode: three failed boots → AP mode & no startup commands [Elektroda, p.kaczmarek2, post #20308150]
startDriver BL0942 9600 (newer boards use 9 600 baud) [Elektroda, Wimmi, post #20957896]PowerSave for BL0937 devices; enable or disable for BL0942 depending on stability [Elektroda, p.kaczmarek2, post #20715289]
• Re-flash latest OBK (> 1.17.458) which fixes wrong CF/CF1 mapping [OBK changelog].VoltageSet, CurrentSet, or PowerSet command is written to flash instantly; no autoexec entry required [Elektroda, p.kaczmarek2, post #20563182]mqtt_broadcastInterval <sec> (typical 30 – 300 s). For change-only posts: VCPPublishThreshold <ΔV> <ΔC> <ΔP> <ΔE> (e.g. 10 0.2 2 0.1) [OBK cmds; Elektroda, carlig833, #21111858].SetupEnergyStats 1 60 5 then restart. HA discovery creates energycounter_yesterday/today/clear_date sensors [Elektroda, sliver85, post #20889701]PowerSave 1 to cut Wi-Fi peaks; both fixes removed −3 500 W glitches in BL0937 sockets [Elektroda, p.kaczmarek2, post #20350667]WifiLED_n, then add script:
alias r_on led_dimmer 0; led_enable 0addEvent Channel1 1 r_onaddEvent Channel1 0 led_enable 1
Now LED blinks during pairing and lights steady when relay is ON [Elektroda, p.kaczmarek2, post #20729217]