Installing Openbk or ESPHome on TOB9-63M Circuit Breakers: Issues with Cloudcutter and Lightleak

I got a bunch of these TOB9-63M (https://www.aliexpress.com/i/3256805380190385.html?gatewayAdapt=4itemAdapt) circuit breakers with energy monitoring.
The device is welded shut, so opening it to install openbk using gpio is not a very viable option (don't want duct-taped switches in main breaker panel).
Wanted to load openbk or esphome variant on this (since all my other devices are on it and connected to HA). Tried cloudcutter (and lightleak) and setup breaker in AP mode. Can't find a profile for this, and by firmware version (1.0.5), tried all the options, but none work. The first step completes OK, but the device stays on and when I restart and start AP mode, it continues to have AP SmartLife-xxxx and not the A* that is expected by cloudcutter.
Lightleak doesn't even connect to the device (keeps connecting/disconnecting from the SmartLife-xxxx AP).
Hate to open it (too many devices and would have to break it open making it unusable).
Any ideas?

I am afraid that you may need to open at least one of TOB9's and take 2MB firmware dump by wires.

Hello partners. A few days ago I received the tomz tob9-63. I decided to open the device, it is relatively easy and there are no marks left, you have to extract the golden pins with a flat screwdriver and separate the two faces, inside there is a CBU. Attached photos. I'll try to extract a backup. If you need any more photos, tell me.

Is that BL0942 there?

p.kaczmarek2 wrote:

Is that BL0942 there?

Yes. Is it?

Added after 10 [minutes]:

It will be enough to install openbeken and configure the pin with BL0942. Or will we have to follow the steps in the link?

https://www.elektroda.com/rtvforum/topic3995777-30.html#20852685

Added after 12 [minutes]:

It will be enough to install openbeken and configure the pin with BL0942. Or will we have to follow the steps in the link?

https://www.elektroda.com/rtvforum/topic3995777-30.html#20852685

The topic you linked is about TuyaMCU device. I am not sure if your device is TuyaMCU-based yet. It may be worth checking whether that BL0942 is connected directly to BK7231 (in UART or SPI mode, it's also worth checking, we support both), or maybe is it connect via TuyaMCU? Is there a secondary MCU on the board?

Can you check with multimeter whether RX/TX of BL042 connects directly to RX1/TX1 of WiFi module?

Still, do 2MB flash backup and try flashing OBK.

I DON'T watch anymore MCU. I am currently attaching the backup copy and the JSON.

Device configuration, as extracted from Tuya:
- Button (channel 1) on P17
- LED (channel 1) on P9
- Bridge Relay On (channel 1) on P24
- Bridge Relay Off (channel 1) on P26
- WiFi LED on P15
Device seems to be using CBU module, which is using BK7231N.
And the Tuya section starts, as usual, at 2023424

JSON

Good job, so all you need is startDriver BL0942 and calibrate.
If that is not working, then you need to retry with startDriver BL0942SPI.

Hello, good evening.
I have flashed the CBU module using UART successfully.

To configure the pins:

P9 = LED 1
P15 = WIFILED
P17 = BTN_TGL_ALL
P24 = BridgeFWD;1
P26 = BridgeREV;1


The BL0942 works perfectly running startDriver BL0942. I haven't had time to calibrate it yet.

Please include JSON template from the web App if you can

Would that be correct? Thanks for your help.

Thank you, device was added to our list:
https://github.com/OpenBekenIOT/webapp/commit/5e6cd9f5f9e4254d279ed27943c299b585337817
It should be available now at:
https://openbekeniot.github.io/webapp/devicesList.html

Hello, good evening.

Today, I calibrated tomz.

I have noticed that the real power is changed with the reactive power, therefore the power factor is wrong.
Furthermore, when consumption is removed, the counter never reaches zero.

How can I change the data from reactive power to power?

And how can I make the consumption zero?

At the moment, I have seen that flags 38 contemplate the option of setting the power to zero when the relays are open.
I have not been able to correct or change the MQTT topic from real power to reactive power.

Okay, so the command to clear stats is: EnergyCntReset
as per our docs: https://github.com/openshwprojects/OpenBK7231T_App/blob/main/docs/commands.md
So you think that values of real power and reactive power are swapped?
Which driver are you using, BL0942 or BL0942SPI?

I am not the author of BL0942SPI, there might be a bug in the code that I need to fix...

I am using BL0942. In other plugs, they work fine. But in this new device, I don't know why it appears rotated. I connect a 400W power resistor. 400VAR appears on the screen. Since it is a pure resistance, it should not be reactive energy.

And you have other BL0942 devices and they work fine? This is very strange.


Well, maybe I could create a flag for you, something like "swap" option, but it seems very odd.

Are all your devices on the same OBK version? Maybe something was broken in the update?

Since I have a second unit of the same model, I'll flash it to see if the same thing happens. I'll comment on it this afternoon.


Added after 10 [hours] 17 [minutes]:

hello, good afternoon. I have tried with the other device I have with BL0942. Same brand and model. Ocurrs the same. The power appears in reactive power, and not in active power as it should be.

I have new news about the active power measurement error in the TOMZ 63. When flag 25 is activated, it begins to measure but as if it were pouring energy, negative data appears. Likewise, the reactive energy is very high.

I have the TOMZN TOB9-VAP. After having it flashed with OBK, I have been struggling with the device getting very hot, also experiencing it to report a couple of Watts even if it has no load powered. Turns out that my config for pins #24 and #26 was incorrect. It should not be configured for Rel and Rel_N respectively. The following pin config worked for me:
"24": "BridgeFWD;1",
"26": "BridgeREV;1"
Also check your channel grouping. Mine was "1".

This solved both the heating problem as well as the no-load current reporting problem.
For the latter, I had Flag #25 & #38 also set.

Anyway, the above worked for me. Worth checking your PIN config out.
I also think the device template might need to be double-checked, as it also shows the Pin #24 and #26 as relay: https://github.com/OpenBekenIOT/webapp/commit/5e6cd9f5f9e4254d279ed27943c299b585337817

For a similar setup, see also: https://www.elektroda.com/rtvforum/topic3934580.html

Hope this helps.

Thank you for reporting the problem, @johanvdm . I don't have those devices personally so it's hard for me to check what config will work the best, but you're not the first one to point this issue, so I decided to change all pins of similiar devices to bridge roles:
https://github.com/OpenBekenIOT/webapp/commit/6e0ac72c19065d843c4af22c0324918dcaf8dcb3
I hope this will help. If something is still incorrect, let me know.

Good morning. It is true that the device got hot. I have changed the remote configuration, I will check that the temperature has dropped.
I was totally unaware of this type of bridge relay.
It is exactly the same device that you show in the link. https://www.elektroda.com/rtvforum/topic3934580.html
Seeing that it worked, I thought it was the correct function.

I am glad to hear that the problem is resolved, let me know i anything else is needed or if you find any other incorrect template on our devices database

I have set this up and allocated the pins as follows:



However, the power is still incorrect for a purely resistive load:

I will add this template to database, what is your device model? Is it 100% the same as in the first post - TOB9-63M?

>>20853888
I wonder if the relay in the 2nd picture can handle 63 amps. From size, I would have guessed 16 amps!

>>20869347 @johanvdm, do you remember what firmware version your TOMZN TOB9-VAP was running?

Mine is running 1.0.15 and I was not able to flash it with cloudcutter.

Do you happen to have your firmware dump too? If it is the same version, maybe cloudcutter devs can add support for it.

Thanks in advance.