Hello! I bought the TOB9-63M WIFI Smart Switch Energy Meter Relay. I made the backup and flashed OpenBK7231N_QIO_1.17.391.bin. Everything worked fine until I added SetStartValue 1 1; to the startup command line. The device hangs after restart and the LEDs light up a little. If I re-flash the...

I can check that SetStartValue command, but can you show your full script? Futhermore, why are you using this command? It should be possible to do the same from GUI... Maybe you are using it in some kind of way that was not predicted by us at the development stage. Alternatively, you can just put a setChannel call in your script and set channel to 1, it will work in a very similiar way... or maybe even better, if that's TuyaMCU device

Which flashing tool are you using to write firmware? Our flasher has option to clear command line, I think.

Ok, so what does the debug log output on TX2 say?

The final startup command was something like:Code: text Expand Select all Copy to clipboardbacklog SetStartValue 1 1; startDriver NTP; ntp_setServer 217.147.223.78; ntp_timeZoneOfs 2; startDriver BL0942; SetupEnergyStats 1 60 5;But the problem is that even if I now rewrite OpenBK firmware with clean OBK settings - device hangs. Relay works only if I flash original firmware which I dumped before flashing OpenBK.

I use BK7231Flasher. Command line is clear but the device doesn't boot with OpenBK.

Thanks for the tip. I soldered the wire to TX2 and checked the console output. It turned out that the device was booting. For some reason the pin assignment was simply reset after changing startup command and restart the device. For now, I have another problem. I set these pins settings: Code: text Expand Select all Copy to clipboard pins: { 9: LED;1, 15: WifiLED;1, 17: Btn_Tgl_All;1, 24: BridgeFWD;1, 26: BridgeREV;1 }, If I press Toggle 1 button in the web-interface - I hear click and relay changes the state. But if I press the button on the device - nothing happens. Flag 41(Ignore all button events) isn't active. What can be wrong?

Is there some information in log when you press the button on the device?

Code: text Expand Select all Copy to clipboardInfo: GEN:17 Button_OnInitialPressDown Info: GEN:17 key_short_press

I checked src of firmware. Btn_Tgl_All works with relays only. But we have type Bridge.Code: text Expand Select all Copy to clipboardvoid CHANNEL_DoSpecialToggleAll() { int anyEnabled, i; anyEnabled = 0; for (i = 0; i 0) { anyEnabled = true; } } for (i = 0; i

That's very good finding, I've applied your fix. Please update and retry.

TOB9-63M Smart Switch Freezes After Adding SetStartValue Command with OpenBK

Exkilla 855 11

Reply | New topic

#1 20895551 07 Jan 2024 10:19

Exkilla Exkilla

Level 2

Post #1
20895551 07 Jan 2024 10:19

Hello! I bought the "TOB9-63M" WIFI Smart Switch Energy Meter Relay. I made the backup and flashed "OpenBK7231N_QIO_1.17.391.bin". Everything worked fine until I added "SetStartValue 1 1;" to the startup command line. The device hangs after restart and the LEDs light up a little. If I re-flash the OpenBK firmware - nothing changes. It still hangs. If I restore the original firmware (Tuya) from the backup - the relay works fine. Please tell me what the problem is and how to solve it?
ADVERTISEMENT
Helpful post

#2 20896320 07 Jan 2024 16:23

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Helpful post? (+1)

Helpful post
Post #2
20896320 07 Jan 2024 16:23

I can check that SetStartValue command, but can you show your full script?

Futhermore, why are you using this command? It should be possible to do the same from GUI...

Maybe you are using it in some kind of way that was not predicted by us at the development stage.

Alternatively, you can just put a setChannel call in your script and set channel to 1, it will work in a very similiar way... or maybe even better, if that's TuyaMCU device

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#3 20896946 07 Jan 2024 20:17

Exkilla Exkilla

Level 2
Topic author Helpful post? (0)

Post #3
20896946 07 Jan 2024 20:17

The final startup command was something like:

Code: text Expand Select all Copy to clipboard
backlog SetStartValue 1 1; startDriver NTP; ntp_setServer 217.147.223.78; ntp_timeZoneOfs 2; startDriver BL0942; SetupEnergyStats 1 60 5;

But the problem is that even if I now rewrite OpenBK firmware with clean OBK settings - device hangs. Relay works only if I flash original firmware which I dumped before flashing OpenBK.
Helpful post

#4 20896962 07 Jan 2024 20:23

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Helpful post? (+1)

Helpful post
Post #4
20896962 07 Jan 2024 20:23

Which flashing tool are you using to write firmware?

Our flasher has option to clear command line, I think.

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
ADVERTISEMENT
#5 20896988 07 Jan 2024 20:34

Exkilla Exkilla

Level 2

Topic author Helpful post? (0)

Post #5
20896988 07 Jan 2024 20:34

I use "BK7231Flasher". Command line is clear but the device doesn't boot with OpenBK.
ADVERTISEMENT
Helpful post

#6 20897089 07 Jan 2024 21:09

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Helpful post? (+1)

Helpful post
Post #6
20897089 07 Jan 2024 21:09

Ok, so what does the debug log output on TX2 say?

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#7 20897368 07 Jan 2024 22:49

Exkilla Exkilla

Level 2
Topic author Helpful post? (0)

Post #7
20897368 07 Jan 2024 22:49

Thanks for the tip. I soldered the wire to TX2 and checked the console output. It turned out that the device was booting. For some reason the pin assignment was simply reset after changing startup command and restart the device.

For now, I have another problem. I set these pins settings:

Code: text Expand Select all Copy to clipboard
"pins": { "9": "LED;1", "15": "WifiLED;1", "17": "Btn_Tgl_All;1", "24": "BridgeFWD;1", "26": "BridgeREV;1" },

If I press "Toggle 1" button in the web-interface - I hear click and relay changes the state. But if I press the button on the device - nothing happens. Flag 41(Ignore all button events) isn't active. What can be wrong?
#8 20897584 08 Jan 2024 07:49

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Helpful post? (0)

Post #8
20897584 08 Jan 2024 07:49

Is there some information in log when you press the button on the device?

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
ADVERTISEMENT
#9 20904666 08 Jan 2024 19:18

Exkilla Exkilla

Level 2
Topic author Helpful post? (0)

Post #9
20904666 08 Jan 2024 19:18

Code: text Expand Select all Copy to clipboard
Info: GEN:17 Button_OnInitialPressDown Info: GEN:17 key_short_press

#10 20906463 13 Jan 2024 03:27

Exkilla Exkilla

Level 2

Post #10

20906463 13 Jan 2024 03:27

I checked "src" of firmware. "Btn_Tgl_All" works with relays only. But we have type "Bridge".

void CHANNEL_DoSpecialToggleAll() {
	int anyEnabled, i;
	anyEnabled = 0;
	for (i = 0; i < CHANNEL_MAX; i++) {
		if (CHANNEL_IsPowerRelayChannel(i) == false)
			continue;
		if (g_channelValues[i] > 0) {
			anyEnabled = true;
		}
	}
	for (i = 0; i < CHANNEL_MAX; i++) {
		if (CHANNEL_IsPowerRelayChannel(i)) {
			CHANNEL_Set(i, !anyEnabled, 0);
		}
	}
}

bool CHANNEL_IsPowerRelayChannel(int ch) {
	int i;
	for (i = 0; i < PLATFORM_GPIO_MAX; i++) {
		if (g_cfg.pins.channels[i] == ch) {
			int role = g_cfg.pins.roles[i];
			// NOTE: do not include Battery relay
			if (role == IOR_Relay || role == IOR_Relay_n) {
				return true;
			}
		}
	}
	return false;
}

Maybe need to replace line in the function "CHANNEL_IsPowerRelayChannel" from:

if (role == IOR_Relay || role == IOR_Relay_n) {

to:

if (role == IOR_Relay || role == IOR_Relay_n || role == IOR_BridgeForward || role == IOR_BridgeReverse) {

Is it correct?

P.S. We can't just change the type to "Relay" because device is getting very hot (mentioned in another topic about this device). Bistable relay is used.

#11 20906548 13 Jan 2024 08:43

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Helpful post? (0)

Post #11
20906548 13 Jan 2024 08:43

That's very good finding, I've applied your fix. Please update and retry.

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#12 20906660 13 Jan 2024 10:21

Exkilla Exkilla

Level 2

Topic author Helpful post? (0)

Post #12
20906660 13 Jan 2024 10:21

It works fine now! Thanks! =)
Create an account, log in and become active in a forum and ads will not appear. You will receive points by participating in discussions.
Join this discussion.

Install the application

Reply | New topic

Report a violation of the law

Topic summary

The discussion revolves around issues faced with the TOB9-63M WiFi Smart Switch after adding the "SetStartValue 1 1;" command to the startup script while using the OpenBK firmware. The device freezes upon restart, and re-flashing the firmware does not resolve the issue, while the original Tuya firmware works fine. Users suggest checking the full script and using alternative commands. The author later discovers that the pin assignments reset after changing the startup command. Despite setting the pins correctly, the physical button on the device does not respond, leading to further investigation into the firmware's handling of button events. A proposed fix involves modifying the firmware code to recognize the device's bridge role, which ultimately resolves the issue.
Summary generated by the language model.