How to Change Firmware on PH-W218 WiFi 8-in-1 Water Quality Tester with CB3S Chip?

TuyaMCU (the MCU itself) remembers data between reboots. You need to power if off. You can also enable TuyaMCU queue in the flags.

In display it shows data but no longer in log or web or MQTT
An OTA update didn't work either

Well, did you do full power off and on cycle?

If not, what is your autoexec.bat?

I took some things out so that only this one still stands
If I get a fakeTuyaPacket 55AA0307000808020004000000FE1D
Send data from the old log but it will not be updated

startDriver TuyaMCU
tuyaMcu_defWiFiState 4

tuyaMcu_sendQueryState
setChannelType 1 temperature_div10
setChannelLabel 1 "Temperatur"
linkTuyaMCUOutputToChannel 8 val 1

Maybe you can try tips from this post?
https://www.elektroda.com/rtvforum/topic3959907.html#20460951

I have now tried the following commands

uartSendHex 55AA000300010407
tuyaMcu_defWiFiState
tuyaMcu_sendQueryState


should not
product_information_valid=0 so aussehen  product_information_valid=1

here is an old log

Hello
Unfortunately nothing has changed
The device display shows all data
But in web and MQTT everything stays at zero
I can set hosts manually with fakeTuyaPacket but they are not updated

You have no TuyaMCU communication at all. You must have played around with settings. Check which flags do you have set. Maybe you've set a "use second UART" flag or something? Check your autoexec.bat. Check other settings. Power off and on the device (physically, not restart button)

startDriver TuyaMCU
tuyaMcu_sendQueryState
tuyaMcu_defWiFiState 4
setChannelType 4 temperature
setChannelLabel 4 "PH Aktuell"
linkTuyaMCUOutputToChannel 106 val 4

Which flags should be set can you export them and post them here

Hinzugefügt nach 8 [Stunden] 49 [Minuten]:

I have now completely reset again with the command
clearConfig
and flashed again, unfortunately without success

I don't know what to do if tuyaMcu_sendProductInformation doesn't return the product information

You must have changed some settings, or removed some settings. Maybe you need to set 115200 baud rate for TuyaMCU?

Or your connection to MCU came loose.

I did a reset and re-flashed which flags should be on
I have now tested again with the baud rate
Is there any way to narrow down the error?

Yes.
1. Set config for baud rate 115200
2. save config
3. open web app log
4. power off (electricity) and on
5. Are there TuyaMCU messages in the log?

6. If there are messages, we have progress, if not, do point 7

7. change baud to 9600
8. save config
9. open web app log
10. power off (electricity) and on
11. Are there TuyaMCU messages in the log?

12. if there is still no TuyaMCU messages, you either have "use UART 2 flag" set in flag (remove it) or connection to MCU is shorted or cut

I did the power,
I disconnected it for 15 seconds,
unfortunately without success
For example,
if I send fakeTuyaPacket 55AA03070008080200040000011636,
it shows a host but unfortunately this host is not updated

Nordlicht77 wrote:

it shows a host but unfortunately this host is not updated

What do you mean?


Are you sure you have it deselected?

once with and once without

|And no TuyaMCU communication at all? Are they still physically connected?

Can you query the status of the DIP in MCU
There has to be some way to isolate the error
I tested the following commands

fakeTuyaPacket fakes the packet from MCU, it won't help here.

You can query data with tuyaMcu_sendQueryState if there is communication, but I don't see any communication on your log.

The main problem is that you are not receiving any packets.

Do you get any TuyaMCU heartbeats?

Nordlicht77 wrote:

I did a reset and re-flashed which flags should be on

I think you don't have physical connection on RX/TX lines between WiFi module and the MCU.

Info:TuyaMCU:ProcessIncoming[v=0]: cmd 0 (Hearbeat) len 7
Info:CMD:[WebApp Cmd 'fakeTuyaPacket 55aa00000000ff' Result] OK
Info:MAIN:Time 11472, idle 204160/s, free 68152, MQTT 1(1), bWifi 1, secondsWithNoPing 1, socks 2/38

No, you can't do that.

You can't use fakeTuyaPacket . It fakes a packet from TuyaMCU to WiFi module. This is useless in your case. You need to get a true heartbeat from physical MCU.

Are you really sure that you have no shorts (or missing connection) on RX1/TX1? Can you show a photo?

I got further, it was really a small hairline crack because I could only see with a magnifying glass
I cut off the tip with a jumper wire and bridged this point with soldering
Now I still have the following problem
Can you remove the word Toogle from Buttom name?
There is a limit because of the button, see picture

 

My code looks like this so far




To set the values ​​for the min and max, I used the following page
https://www.rapidtables.com/convert/number/decimal-to-hex.html
and there I selected Decimal to Hexadecimal
Under Decimal I wrote the host in plain text
You will then get the result under Hex
An example
the first numbers of 55AA03070008 for example of 55AA0307000866020004000000FA77 remain the same in this case
The 66 is the number of TuyaMCU dpID in hex in plain text 102
The next numbers of 55AA0307000866020004000000FA77 i.e. 0200040000 remain
The 00FA in the number of TuyaMCU value in Hex in plain text 250
The next numbers from 55AA0307000866020004000000FA77 i.e. 77 is the checksum
This must be converted on the page
https://www.scadacore.com/tools/programming-calculators/online-checksum-calculator/
To do this, take the result of the hex without the last two numbers in this case 55AA0307000866020004000000FA
inserts it under Hex Input
Then press AnalyzeDataHex
Under AnalyzeDataHex there is the checksum, i.e. the last two numbers
I then inserted this host under config-> Execute custom command with fakeTuyaPacket 55AA0307000866020004000000FA77
Here is my fakeTuyaPacket with positive feedback
fakeTuyaPacket 55AA0307000866020004000000FA77    id 121
Info:TuyaMCU processIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU parseState: id 102 type 2-val len 4
Info:TuyaMCU parseState: int32 250
Info:GEN:CHANNEL_Set channel 2 has changed to 250 (flags 0)
Info:MQTT:Channel has changed! Publishing 250 to channel 2
Info:MQTT publishing val 250 to obk0DE017Cuuuu/2/get retain=0

fakeTuyaPacket 55AA0307000867020004000000E664
Info:TuyaMCU processIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU parseState: id 103 type 2-val len 4
Info:TuyaMCU parseState: int32 230
Info:GEN:CHANNEL_Set channel 3 has changed to 230 (flags 0)
Info:MQTT:Channel has changed! Publishing 230 to channel 3
Info:MQTT publishing val 230 to obk0DE017Cuuuu/3/get retain=0
Info:TuyaMCU processIncoming: discarding packet bad expected checksum, expected 119 and got checksum 228

fakeTuyaPacket 55AA030700086B02000400000320A5
Info:TuyaMCU processIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU parseState: id 107 type 2-val len 4
Info:TuyaMCU parseState: int32 800
Info:GEN:CHANNEL_Set channel 5 has changed to 800 (flags 0)
Info:MQTT:Channel has changed! Publishing 800 to channel 5
Info:MQTT publishing val 800 to obk0DE017Cuuuu/5/get retain=0

fakeTuyaPacket 55AA030700086C020004000002BC41
Info:TuyaMCU processIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU parseState: id 108 type 2-val len 4
Info:TuyaMCU parseState: int32 700
Info:GEN:CHANNEL_Set channel 6 has changed to 700 (flags 0)
Info:MQTT:Channel has changed! Publishing 700 to channel 6
Info:MQTT publishing val 700 to obk0DE017Cuuuu/6/get retain=0

fakeTuyaPacket 55AA0307000870020004000001F47C
Info:TuyaMCU processIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU parseState: id 112 type 2-val len 4
Info:TuyaMCU parseState: int32 500
Info:GEN:CHANNEL_Set channel 8 has changed to 500 (flags 0)
Info:MQTT:Channel has changed! Publishing 500 to channel 8
Info:MQTT publishing val 500 to aqariumwasserkontrolle/8/get retain=0

fakeTuyaPacket 55AA03070008710200040000000088
Info:TuyaMCU processIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU parseState: id 113 type 2-val len 4
Info:TuyaMCU parseState: int32 0
Info:GEN:No change in channel 9 (still set to 0) - ignoring

fakeTuyaPacket 55AA0307000884020004000001902C
Info:TuyaMCU rocessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU parseState: id 132 type 2-val len 4
Info:TuyaMCU arseState: int32 400
Info:GEN:CHANNEL_Set channel 11 has changed to 400 (flags 0)
Info:MQTT:Channel has changed! Publishing 400 to channel 11
Info:TuyaMCU:Received: 55 AA 03 00 00 01 01 04
Info:TuyaMCU processIncoming[v=3]: cmd 0 (Hearbeat) len 8
Info:MQTT publishing val 400 to aqariumwasserkontrolle/11/get retain=0

fakeTuyaPacket 55AA0307000885020004000000C864
Info:TuyaMCU rocessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU parseState: id 133 type 2-val len 4
Info:TuyaMCU parseState: int32 200
Info:GEN:CHANNEL_Set channel 12 has changed to 200 (flags 0)
Info:MQTT:Channel has changed! Publishing 200 to channel 12
Info:MQTT publishing val 200 to aqariumwasserkontrolle/12/get retain=0

I am happy to hear that you've solved the RX/TX trace problem. As I said, I suspect that is the issue.

Nordlicht77 wrote:

Can you remove the word Toogle from Buttom name?
There is a limit because of the button, see picture

I can try to organise it better.

Nordlicht77 wrote:

Code: text Expand Select all Copy to clipboard

setChannelType 3 temperature_div10
setChannelLabel 3 "Low temperature alarm value"
linkTuyaMCUOutputToChannel 103 val 3
addRepeatingEvent 15 -1 publishFloat temperatur_min $CH3/10 0 2 
//set value to Channel 103 TuyaMcu
fakeTuyaPacket 55AA0307000867020004000000E664
//set virtual button temp min
setChannelLabel 21 "Temp min"
setChannelType 21  Toggle

fakeTuyaPacket simulated TuyaMCU sending data to the WiFi module. So it's not affecting Tuya MCU. Please stop using this. This won't set anything for TuyaMCU.

Nordlicht77 wrote:

To set the values ​​for the min and max, I used the following page
https://www.rapidtables.com/convert/number/decimal-to-hex.html
and there I selected Decimal to Hexadecimal
Under Decimal I wrote the host in plain text
You will then get the result under Hex
An example
the first numbers of 55AA03070008 for example of 55AA0307000866020004000000FA77 remain the same in this case
The 66 is the number of TuyaMCU dpID in hex in plain text 102
The next numbers of 55AA0307000866020004000000FA77 i.e. 0200040000 remain
The 00FA in the number of TuyaMCU value in Hex in plain text 250
The next numbers from 55AA0307000866020004000000FA77 i.e. 77 is the checksum
This must be converted on the page
https://www.scadacore.com/tools/programming-calculators/online-checksum-calculator/
To do this, take the result of the hex without the last two numbers in this case 55AA0307000866020004000000FA
inserts it under Hex Input
Then press AnalyzeDataHex
Under AnalyzeDataHex there is the checksum, i.e. the last two numbers
I then inserted this host under config-> Execute custom command with fakeTuyaPacket 55AA0307000866020004000000FA77
Here is my fakeTuyaPacket with positive feedback
fakeTuyaPacket 55AA0307000866020004000000FA77    id 121
Info:TuyaMCU processIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU parseState: id 102 type 2-val len 4
Info:TuyaMCU parseState: int32 250
Info:GEN:CHANNEL_Set channel 2 has changed to 250 (flags 0)
Info:MQTT:Channel has changed! Publishing 250 to channel 2
Info:MQTT publishing val 250 to obk0DE017Cuuuu/2/get retain=0

Again - this is only changing the WiFi module values. It's not affecting the MCU. Please stop using this.

If you want to set the real value of the MCU, then you can consider:

https://github.com/openshwprojects/OpenBK7231T_App/blob/main/docs/commands.md
tuyaMcu_sendState will automatically send the packet from WiFi module to TuyaMCU to send the given dpID of type to given value. This will automatically calculate checksum.

have changed it
Now I only have the problem that not everything is set at the first start
have it with me
Tried addRepeatingEvent doesn't work either
and at temperature I have another formatting problem
see image

Are you really sure that you want to do:

This will send forever, every 15 seconds, a command to send dpID 103 to 2300.

Do you have enabled TuyaMCU queue in the flags?

If you want to set values once after boot, do:

etc

I would have to go
delay_s 15 go so that the values ​​are all loaded otherwise two or three were always missing
Now the format problem is still like in the picture Temp Max and Temp min must look like temperature

Maybe just change temperature_div10 to temperature_div100?

Now the point is correct with temperature div 100 but now there are three digits and not two
with fakeTuyaPacket it was correct

tuyaMcu_sendState doesn't run reliably for me;
it always doesn't set some values ​​after a restart
but not always the same
I even went with Deley S 25
If there is a temperature format error, I'll go back to the two on fakeTuyaPacket
because otherwise the if loops won't work

Hinzugefügt nach 7 [Stunden] 28 [Minuten]:

Hi
For me the output of TDS not correct
See photo



I don't know what it's like @Upright6771

Hinzugefügt nach 2 [Stunden] 11 [Minuten]:

Are there the following MQTT values
IPAddress
Gateway
Subnet mask
Mac
hostname
version
BootCount
Core
Updates available
Online state
Web interface disable via Mqtt

What do they think with this image? It is possible with CSS

I tried again with tuyaMcu send State, unfortunately not everything was sent sporadically, see photo after various restarts
Now have tuyaMcu_setBaudRate 9600
Added clearIO now the Gui looks different
Also temperature min and max after changing 2300 to 230 the host is correct
Now it's just the TDS values ​​that don't match the display
The status via the Bottom On / OFF would be nice if it could be deactivated using a flag