logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

[BK7231N ] Teardown of TH08 LCD Calendar/clock/temperature/humidity, 3xAAA battery, backlight

morgan_flint 29784 225
ADVERTISEMENT
Reply Cool? Ranking DIY | New topic
Notify about new articles
  • #181 21074066
    p.kaczmarek2
    Moderator Smart Home  
    I think you still have problem because this old IP is remembered in settings. Please use ntp_setServer to assign a new, correct NTP server IP.
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #182 21074156
    spin55
    Level 17  
    Try this: ntp_setServer 217.147.223.78

    Added after 45 [minutes]:

    @kkarmah,

    Careful with this:

    Info:MAIN:Using SSID [Vodafone-******]
    Info:MAIN:Using Pass [8e5f******]
    Info:MQTT:mqtt_userName g******
    mqtt_pass Ha******
  • #183 21074347
    morgan_flint
    Level 14  
    @kkarmah
    The NTP server you're using (192.168.1.198) is a LAN address so, unless you have a local NTP server, it's not going to work.

    I'm using 150.214.5.121, but probably the one @spin55 is using (217.147.223.78) is also OK Try PINGing those addresses to see if you have a response. Before, I was using the NTP servers of the Spanish Navy Observatory (I visited it and could see the atomic clocks there, BTW), but their URLs (hora.roa.es and minuto.roa.es) don't seem to be working now:
    Code: text Expand Select all Copy to clipboard
    C:\Users\qrctg>ping hora.roa.es

Haciendo ping a hora.roa.es [150.214.94.5] con 32 bytes de datos:
Tiempo de espera agotado para esta solicitud.
Tiempo de espera agotado para esta solicitud.

Estadísticas de ping para 150.214.94.5:
    Paquetes: enviados = 2, recibidos = 0, perdidos = 2
    (100% perdidos),
Control-C
^C
C:\Users\qrctg>ping minuto.roa.es

Haciendo ping a minuto.roa.es [150.214.94.10] con 32 bytes de datos:
Tiempo de espera agotado para esta solicitud.
Tiempo de espera agotado para esta solicitud.

Estadísticas de ping para 150.214.94.10:
    Paquetes: enviados = 2, recibidos = 0, perdidos = 2
    (100% perdidos),
Control-C
^C

    So I changed to another one (this is why I suggest to PING to the address before using it).

    Also, have in mind the NTP time zone offset (ntp_timeZoneOfs) for your zone. For Spain the settings should be "ntp_timeZoneOfs 1" in winter and "ntp_timeZoneOfs 2" in summer but for Portugal, I think they should be 0 and 1, respectively (AFAIK, OBK doesn't deal with summer-winter time automatically at this moment, but seems like there's some work in progress for that on this thread, so maybe in the future it will).
  • #184 21087098
    kkarmah
    Level 6  
    Thank you all. It's already working, for me it works like this:
    Code: text Expand Select all Copy to clipboard
    startDriver TuyaMCU
startDriver tmSensor
startDriver NTP

ntp_setServer 193.136.152.71
ntp_timeZoneOfs 1

setChannelType 1 temperature_div10
linkTuyaMCUOutputToChannel 1 val 1

setChannelType 2 Humidity
linkTuyaMCUOutputToChannel 2 val 2

setChannelType 3 ReadOnlyLowMidHigh
linkTuyaMCUOutputToChannel 3 val 3
setChannelLabel 3 BatteryLevel 
  • #185 21297666
    xeparrelik
    Level 1  
    Hello,
    I've bought this device and I wanted to flash OpenBK into it, could anyone please tell me the instructions on how to flash it?
    I'm new to this and by reading the thread I'm with doubts on where to connect the wires (seems that there's few approaches).
    Thanks.
  • #186 21310308
    szabkaelektroda
    Level 2  
    >>21074347 Hi! I also faced NTP issues. My IOT devices lives in a separated vlan and the default gateway is the ntp server and even with this setup the sensor sometimes stuck with 2070 date. At first I added the errno value of the printed error message and found out that even with wifi connected the send can return with noroutetohost errno, and the receive could stuck in eagain.
    I already actively test a patch that does a quick resend on receive failures on the first minute(like in send) and Main_IsConnectedToWiFi changed to boolean and returns tru only if the module also received ip from dhcp or has static ip configured. So far it is working good but i want to do more endurence testing. This battery operated devices has a lot of boots.
  • #187 21310983
    p.kaczmarek2
    Moderator Smart Home  
    xeparrelik wrote:

    I've bought this device and I wanted to flash OpenBK into it, could anyone please tell me the instructions on how to flash it?

    Related guide: TuyaMCU flashing, setup and configuration guide - configure dpIDs for Home Assistant

    TLDR: TuyaMCU device uses UART 1 programming port also for communication with the MCU. So you may need to cut those traces or desolder the MCU or put MCU in reset state or desolder WiFi module. Your device also seems to be the battery-powered one. So there is another issue - TuyaMCU controls the power of WiFi module. So you need to power WiFi module 3.3V pin directly. Most likely.

    >>21310308 Main_IsConnectedToWiFi should only check for WiFi connection, not NTP... you seem to have found correctly the issue, but the fix should be rather to add the NTP check somewhere, I'm not sure where yet.
    Helpful post? Buy me a coffee.
  • #188 21311969
    szabkaelektroda
    Level 2  
    p.kaczmarek2 wrote:
    Main_IsConnectedToWiFi should only check for WiFi connection, not NTP... you seem to have found correctly the issue, but the fix should be rather to add the NTP check somewhere, I'm not sure where yet.

    I think there is a little misunderstanding, the Main_IsConnectedToWiFi is extended to check IP existence which is in my glossary is strictly connectivity related and not NTP related.
    Code: text Expand Select all Copy to clipboard
    return g_bHasWiFiConnected>0 && (g_cfg.staticIP.localIPAddr[0] != 0 || g_currentIPString[0] != 0);

    If somebody needs the wifi status alone just use the another Main_HasWiFiConnected function.
  • ADVERTISEMENT
  • #189 21339948
    PC-maniak
    Level 8  
    Hi, I'm asking for advice on this module thanks to TyuaMCU, I have a problem getting the values ​​for the publish command
    The values ​​are normally displayed on the website and are sent as mqtt, but when I need to send them using publish, I get zero.

    Screenshot showing temperature and humidity data and the status of OpenBK7231N drivers.

    autoexe :
    Code: text Expand Select all Copy to clipboard
    startDriver TuyaMCU
// TEMP $CH1
setChannelType 1 temperature_div10
linkTuyaMCUOutputToChannel 1 val 1 // maybe I just understand it wrong.. but now the value from TyuaMCU 1 should be connected to ch1??
// HUM $CH2
setChannelType 2 Humidity
linkTuyaMCUOutputToChannel 2 val 2

startDriver tmSensor
startDriver NTP
ntp_timeZoneOfs 1
ntp_setServer 192.168.1.132 // local NTP server for speed and loop prevention in case of internet outage
// now wait for NTP
waitFor NTPState 1
// now wait for MQTT
waitFor MQTTState 1
delay_s 1
publish DATA {"ROOM":"KITCHEN","TEMPERATURE":$CH1,"HUMIDITY":$CH2} // both are zero .. I also tried $1



    Thank you in advance for the information and knowledge. =) Tom
  • #190 21340135
    p.kaczmarek2
    Moderator Smart Home  
    Your Publish syntax is correct.
    Code snippet in Visual Studio testing JSON and MQTT syntax.

    You are getting 0 most likely because you are sending data BEFORE TuyaMCU sends it to OBK.

    I'd try something like that:
    Code: text Expand Select all Copy to clipboard
    
REST OF YOUR OLD SCRIPT HERE.... 
// now wait for MQTT
waitFor MQTTState 1
// now wait for channel 1 to become non zero
// if channel 1 is still 0, loop, wait 0.1s and check again
again:
delay_s 0.1
if $CH1==0 then goto again
publish DATA {"ROOM":"KITCHEN","TEMPERATURE":$CH1,"HUMIDITY":$CH2}


    The following suggestion was tested by self tests:
    - publish command JSON syntax test:
    https://github.com/openshwprojects/OpenBK7231...mmit/6940b06cfa9df8c1862e4aee5543bf4abc471e4d
    - waiting for channel 1 to become non-zero self test:
    https://github.com/openshwprojects/OpenBK7231...mmit/a0ab7c17e4632601f40e016e3afc2e93e799ce20
    Helpful post? Buy me a coffee.
  • #191 21341044
    PC-maniak
    Level 8  
    >>21340135

    WOOOW ! Thank you, that was it.
  • ADVERTISEMENT
  • #193 21357157
    smoeller95s
    Level 3  
    Hello Im new in OpenBK and with your Help it was Easy to Flash the TH08. But one Problem i found. I Have the 12H AM/PM Version of the TH08. Default is temperature in F.
    Anyone know how to send the command to switch the display to C Temperature?
    The Mqtt data is fine in C but the display show F Temperature.
  • #194 21357234
    divadiow
    Level 34  
    GAAD wrote:
    Is there a chance to reprogram it and free myself from Tuya?


    yes. same process as with TH08 and any other Beken device with TuyaMCU. Your firmware is patched so no Cloudcutter - you'll have to UART flash.

    To start you off here is the dpID mapping for the firmware you posted

    Code: JSON
    Log in, to see the code
  • #195 21357267
    p.kaczmarek2
    Moderator Smart Home  
    https://www.elektroda.com/rtvforum/topic4038151.html
    Search for TH06 there:
    https://github.com/openshwprojects/OpenBK7231T_App/blob/main/docs/autoexecExamples.md

    @GAAD as long as the dpIDs didn't change, it should be very easy, like with similiar modules. tmSensor driver should work. Just remember the basics that have been spoken on forum many time, like that you need to disconnect TuyaMCU for the time of the flashing because it's using the same UART port, etc, etc.

    @smoeller95s you need to know the dpID of temperature format enumeration. You can figure it in many ways:
    - you can capture traffic on original Tuya firmware with https://www.elektroda.com/rtvforum/topic3970199.html
    - you can get dpIDs from tuya developer API https://www.elektroda.com/rtvforum/topic4021129.html
    - you can just search the forum, maybe someone already has found out this dp?
    Maybe it could be also possible to just set temperature to C in Tuya App before flashing and the MCU just might remember that.
    EDIT:
    divadiow wrote:

    Code: JSON
    Log in, to see the code

    Thank you for sharing, that's what he asked for. So the temperature unit selection dpID on this device is 9, it's an enumeration with two possible options - C or F.
    Helpful post? Buy me a coffee.
  • #196 21357478
    GAAD
    Level 17  
    p.kaczmarek2 wrote:
    @GAAD as long as the dpIDs didn't change, it should be very easy, like with similiar modules. tmSensor driver should work. Just remember the basics that have been spoken on forum many time, like that you need to disconnect TuyaMCU for the time of the flashing because it's using the same UART port, etc, etc.


    Maybe in this module UART is probably free? I uploaded OBK without interrupting paths without any problem at 921600 baudrate, Rx and Tx and Vcc directly on CB3S. Now OBK works for me, on display outdated time, temperature and humidity but OBK does not see it. I found autoexec files but did not find dpio configuration.

    edit:
    It worked, but only for HA to show these readings My autoexec (NTP server in the local network)
    Digital display showing temperature and humidity.
    Code: text Expand Select all Copy to clipboard
    
startDriver NTP
ntp_setServer 192.168.1.253
waitFor NTPState 1
startDriver TuyaMCU
startDriver tmSensor
ntp_timeZoneOfs 1
setChannelType 1 temperature_div10
linkTuyaMCUOutputToChannel 1 val 1
setChannelType 2 Humidity
linkTuyaMCUOutputToChannel 2 val 2
linkTuyaMCUOutputToChannel 3 val 3
setChannelType 3 ReadOnlyLowMidHigh
setChannelLabel 3 "Battery Level"
mqtt_broadcastItemsPerSec 20 
waitFor MQTTState 1
// now wait for channel 1 to become non zero
// if channel 1 is still 0, loop, wait 0.1s and check again
again:
delay_s 0.1
if $CH1==0 then goto again
publish DATA {"ROOM":"SYPIALNIA 1","TEMPERATURE":$CH1,"HUMIDITY":$CH2}


    He reported it, but can it be improved?

    Interface displaying battery level, humidity, and temperature.
    next autoexec temperature not divided by 10
    Code: text Expand Select all Copy to clipboard
    
startDriver NTP
ntp_setServer 192.168.1.253
waitFor NTPState 1
startDriver TuyaMCU
startDriver tmSensor
ntp_timeZoneOfs 1

setChannelType 1 temperature
linkTuyaMCUOutputToChannel 1 val 1

setChannelType 2 Humidity
linkTuyaMCUOutputToChannel 2 val 2

setChannelLabel 3 "Battery Level State"
linkTuyaMCUOutputToChannel 3 val 3
setChannelType 3 ReadOnlyLowMidHigh

setChannelLabel 4 "Battery Level"
linkTuyaMCUOutputToChannel 4 val 4
setChannelType 4 ReadOnlyLowMidHigh



mqtt_broadcastItemsPerSec 20 
waitFor MQTTState 1
// now wait for channel 1 to become non zero
// if channel 1 is still 0, loop, wait 0.1s and check again
again:
delay_s 0.1
if $CH1==0 then goto again
publish DATA {"ROOM":"SYPIALNIA 1","TEMPERATURE":$CH1,"HUMIDITY":$CH2}


    Dodano po 9 [godziny] 14 [minuty]:

    It's almost perfect.
    How do I get rid of zeros after the decimal point in humidity?
    Why doesn't it send channels 3 and 4 with battery status even though I added them to autoconfig?
    When trying it sometimes sent, now there's nothing in HA even though it's displayed on the page.
    Home Assistant user interface displaying temperature, humidity, and battery level data for various rooms.
    Code: text Expand Select all Copy to clipboard
    
startDriver NTP
ntp_setServer 192.168.1.253
waitFor NTPState 1
startDriver TuyaMCU
startDriver tmSensor
ntp_timeZoneOfs 1

//setChannelType 1 temperature_div10
setChannelType 1 temperature
linkTuyaMCUOutputToChannel 1 val 1

setChannelType 2 Humidity
linkTuyaMCUOutputToChannel 2 val 2

setChannelLabel 3 "Battery Level State"
linkTuyaMCUOutputToChannel 3 val 3
setChannelType 3 ReadOnlyLowMidHigh

setChannelLabel 4 "Battery Level"
linkTuyaMCUOutputToChannel 4 val 4
setChannelType 4 ReadOnlyLowMidHigh

mqtt_broadcastItemsPerSec 20 
waitFor MQTTState 1
// now wait for channel 1 to become non zero
// if channel 1 is still 0, loop, wait 0.1s and check again
again:
delay_s 0.1
if $CH1==0 then goto again
publish DATA {"ROOM":"SYPIALNIA 1","TEMPERATURE":$CH1,"HUMIDITY":$CH2, "BATTERY Level State":$CH3,"BATTERY Level":$CH4}
  • #197 21358303
    smoeller95s
    Level 3  
    p.kaczmarek2 wrote:
    Thank you for sharing, that's what he asked for. So the temperature unit selection dpID on this device is 9, it's an enumeration with two possible options - C or F.


    Thank you for this information. How to do this in config? I think i need to add an line to autoexec.bat ?
    something like SetChannel 9 0 ?
  • ADVERTISEMENT
  • #198 21358429
    p.kaczmarek2
    Moderator Smart Home  
    Thank you for sharing @GAAD

    @smoeller95s setChannel will only set DP if you map it first.
    Check this:
    https://github.com/openshwprojects/OpenBK7231T_App/blob/main/docs/commands.md
    If you want to set dpID directly, you can use tuyaMcu_sendState. This does not require any channels. Just make sure to use it at the correct time, I don't know, maybe add some delay, like delay_s 2? I'm not sure at the moment. You can also try executing it at runtime, when device is online and see if it works.
    Helpful post? Buy me a coffee.
  • #199 21359447
    GAAD
    Level 17  
    The Polish version will be automatically translated?

    Unfortunately, not quite everything works as it should.
    I wrote that I do not have to divide the temperature by 10, i.e.
    "setChannelType 1 temperature"
    Theoretically it worked but after changing the battery in the HA instead of 20 degrees it is 2.0 degrees.
    Autoexec:
    Code: text Expand Select all Copy to clipboard
    
startDriver NTP
ntp_setServer 192.168.1.253
waitFor NTPState 1
ntp_timeZoneOfs 1
startDriver TuyaMCU
startDriver tmSensor

setChannelType 1 temperature_div10
//setChannelType 1 temperature
linkTuyaMCUOutputToChannel 1 val 1

setChannelType 2 Humidity
linkTuyaMCUOutputToChannel 2 val 2

setChannelLabel 3 "Battery State"
linkTuyaMCUOutputToChannel 3 val 3
setChannelType 3 ReadOnlyLowMidHigh

setChannelLabel 4 "Battery"
linkTuyaMCUOutputToChannel 4 val 4
setChannelType 4 BatteryLevelPercent

mqtt_broadcastItemsPerSec 20 
waitFor MQTTState 1
// now wait for channel 1 to become non zero
// if channel 1 is still 0, loop, wait 0.1s and check again
again:y
delay_s 0.1
if $CH1==0 then goto again
publish DATA {"Temperature":$CH1,"Humidity":$CH2,"Battery State":$CH3,"Battery Level":$CH4}
    .
    On the OBK web page the temperature is correct but in HA divided by 10
    Configuration screen of TiW_Disp 1 device showing temperature, humidity, and battery status information. .
    Home Assistant dashboard displaying device data. .

    Despite sending two battery statuses, this data is missing from the HA.

    If I change the channel configuration to:
    "setChannelType 1 temperature"
    it looks like this:
    Web page with information about the TiW_Disp 1 device, showing data on temperature, humidity, battery status, and other technical details. .
    but in HA:
    Screenshot of the Home Assistant interface displaying information about the TiW_Disp_1 device. .

    Sometimes, on the other hand, 230 degrees also appears in HA. I have completely lost my mind now.
    Part of the log file:
    Code: text Expand Select all Copy to clipboard
    
Info:MAIN:Main_OnWiFiStatusChange - WIFI_STA_CONNECTED - 4
Info:MAIN:Time 11, idle 88107/s, free 66000, MQTT 0(0), bWifi 1, secondsWithNoPing -1, socks 4/38 
Info:MAIN:HA discovery is scheduled, but MQTT connection is not present yet
Info:NTP:Seconds since Jan 1 1900 = 3943894588
Info:NTP:Unix time  : 1734905788
Info:NTP:Local Time : 2024-12-22 22:16:28
Info:MAIN:Time 12, idle 186198/s, free 74848, MQTT 0(0), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:MAIN:HA discovery is scheduled, but MQTT connection is not present yet
Info:NTP:NTP offset set
Info:MAIN:Started TuyaMCU.
Info:MAIN:Started tmSensor.
Info:GEN:Channel 1 type changed to temperature
Info:GEN:Channel 2 type changed to Humidity
Info:GEN:Channel 3 type changed to ReadOnlyLowMidHigh
Info:GEN:Channel 4 type changed to BatteryLevelPercent
Info:MQTT:mqtt_userName mqtt
mqtt_pass mqtt
mqtt_clientID obk689EE87D
mqtt_host 192.168.1.253:1883
Info:MQTT:mqtt_connection_cb: Successfully connected
Info:MQTT:mqtt_subscribed to obk689EE87D/+/set
Info:MQTT:mqtt_subscribed to bekens_n/+/set
Info:MQTT:mqtt_subscribed to cmnd/obk689EE87D/+
Info:MQTT:mqtt_subscribed to cmnd/bekens_n/+
Info:MQTT:mqtt_subscribed to obk689EE87D/+/get
Info:MAIN:Time 13, idle 181915/s, free 72368, MQTT 0(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:MAIN:Will do request HA discovery now.
Info:HTTP:HASS counts: 0 rels, 0 pwms, 0 inps, 0 excluded
Info:MQTT:Queued topic=homeassistant/sensor/TiW_Disp_1_temperature_1/config, 1 items in queue
Info:MQTT:Queued topic=homeassistant/sensor/TiW_Disp_1_humidity_2/config, 2 items in queue
Info:MQTT:Queued topic=homeassistant/sensor/TiW_Disp_1_sensor_3/config, 3 items in queue
Info:MQTT:Queued topic=homeassistant/sensor/TiW_Disp_1_temp/config, 4 items in queue
Info:MQTT:Queued topic=homeassistant/sensor/TiW_Disp_1_rssi/config, 5 items in queue
Info:MQTT:Queued topic=homeassistant/sensor/TiW_Disp_1_uptime/config, 6 items in queue
Info:MQTT:Queued topic=homeassistant/sensor/TiW_Disp_1_build/config, 7 items in queue
Info:MQTT:Queued topic=homeassistant/sensor/TiW_Disp_1_ssid/config, 8 items in queue
Info:MQTT:Queued topic=homeassistant/sensor/TiW_Disp_1_ip/config, 9 items in queue
Info:TuyaMCU:Received: 55 AA 00 01 00 24 7B 22 70 22 3A 22 67 37 63 6A 6D 65 66 75 6F 75 63 6D 63 62 32 73 22 2C 22 76 22 3A 22 31 2E 31 2E 36 22 7D DC 
Info:TuyaMCU:ProcessIncoming[v=0]: cmd 1 (QueryProductInformation) len 43
Info:TuyaMCU:ParseQueryProductInformation: received {"p":"g7cjmefuoucmcb2s","v":"1.1.6"}
Info:MQTT:Publishing val TiW_Disp_1 to obk689EE87D/host retain=0
Info:MQTT:Publishing val OpenBK7231N 1.17.780 Nov 29 2024 09:48:51 to obk689EE87D/build retain=0
Info:MQTT:Publishing val d8:d6:68:9e:e8:7d to obk689EE87D/mac retain=0
Info:MQTT:Publishing val (313 bytes) to homeassistant/sensor/TiW_Disp_1_temperature_1/config retain=1
Info:MQTT:Publishing val (302 bytes) to homeassistant/sensor/TiW_Disp_1_humidity_2/config retain=1
Info:MQTT:Publishing val (385 bytes) to homeassistant/sensor/TiW_Disp_1_sensor_3/config retain=1
Info:MQTT:Publishing val 34.00 to obk689EE87D/temp retain=0
Info:MQTT:Publishing val SALON to obk689EE87D/ssid retain=0
Info:MQTT:Publishing val 1734909389 to obk689EE87D/datetime retain=0
Info:MQTT:Publishing val 2 to obk689EE87D/sockets retain=0
Info:MQTT:Publishing val -80 to obk689EE87D/rssi retain=0
Info:MQTT:Publishing val 13 to obk689EE87D/uptime retain=0
Info:MQTT:Publishing val 58176 to obk689EE87D/freeheap retain=0
Info:MQTT:Publishing val 192.168.1.72 to obk689EE87D/ip retain=0
Info:MQTT:Channel has changed! Publishing 0.000000 to channel 1 
Info:MQTT:Publishing val 0.000000 to obk689EE87D/1/get retain=0
Info:MQTT:Channel has changed! Publishing 0.000000 to channel 2 
Info:MQTT:Publishing val 0.000000 to obk689EE87D/2/get retain=0
Info:MQTT:Channel has changed! Publishing 0.000000 to channel 3 
Info:MQTT:Publishing val 0.000000 to obk689EE87D/3/get retain=0
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic obk689EE87D/1/get
Info:MQTT:Channel has changed! Publishing 0.000000 to channel 4 
Info:MQTT:Publishing val 0.000000 to obk689EE87D/4/get retain=0
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic obk689EE87D/2/get
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic obk689EE87D/3/get
Info:MAIN:Time 14, idle 152993/s, free 57808, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic obk689EE87D/4/get
Error:CMD:cmd again:y NOT found (args )
Info:TuyaMCU:Received: 55 AA 00 02 00 00 01 
Info:TuyaMCU:ProcessIncoming[v=0]: cmd 2 (MCUconf) len 7
Info:TuyaMCU:ProcessIncoming: TUYA_CMD_MCU_CONF, TODO!
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Info:MQTT:Publishing val (334 bytes) to homeassistant/sensor/TiW_Disp_1_temp/config retain=1
Info:MQTT:Publishing val (331 bytes) to homeassistant/sensor/TiW_Disp_1_rssi/config retain=1
Info:MQTT:Publishing val (333 bytes) to homeassistant/sensor/TiW_Disp_1_uptime/config retain=1
Info:MAIN:Time 15, idle 136009/s, free 57352, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Info:MQTT:Publishing val (260 bytes) to homeassistant/sensor/TiW_Disp_1_build/config retain=1
Info:MQTT:Publishing val (291 bytes) to homeassistant/sensor/TiW_Disp_1_ssid/config retain=1
Info:MQTT:Publishing val (275 bytes) to homeassistant/sensor/TiW_Disp_1_ip/config retain=1
Info:MAIN:Time 16, idle 181320/s, free 57448, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Info:MQTT:Channel has changed! Publishing 0.000000 to channel 1 
Info:MQTT:Publishing val 0.000000 to obk689EE87D/1/get retain=0
Info:MQTT:Channel has changed! Publishing 0.000000 to channel 2 
Info:MQTT:Publishing val 0.000000 to obk689EE87D/2/get retain=0
Info:MQTT:Channel has changed! Publishing 0.000000 to channel 3 
Info:MQTT:Publishing val 0.000000 to obk689EE87D/3/get retain=0
Info:MQTT:Channel has changed! Publishing 0.000000 to channel 4 
Info:MQTT:Publishing val 0.000000 to obk689EE87D/4/get retain=0
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic obk689EE87D/1/get
Info:MAIN:Time 17, idle 212585/s, free 58320, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic obk689EE87D/2/get
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic obk689EE87D/3/get
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic obk689EE87D/4/get
Error:CMD:cmd again:y NOT found (args )
Info:TuyaMCU:Received: 55 AA 00 02 00 00 01 
Info:TuyaMCU:ProcessIncoming[v=0]: cmd 2 (MCUconf) len 7
Info:TuyaMCU:ProcessIncoming: TUYA_CMD_MCU_CONF, TODO!
Info:TuyaMCU:Received: 55 AA 00 05 00 05 09 04 00 01 00 17 
Info:TuyaMCU:ProcessIncoming[v=0]: cmd 5 (WiFiSelect) len 12
Info:TuyaMCU:V0_ParseRealTimeWithRecordStorage: processing id 9, dataType 4-enum and 1 data bytes
Info:TuyaMCU:V0_ParseRealTimeWithRecordStorage: byte 0
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Info:MAIN:Time 18, idle 127274/s, free 58320, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Error:CMD:cmd again:y NOT found (args )
Info:TuyaMCU:Received: 55 AA 00 05 00 08 0A 02 00 04 00 00 01 5E 7B 
Info:TuyaMCU:ProcessIncoming[v=0]: cmd 5 (WiFiSelect) len 15
Info:TuyaMCU:V0_ParseRealTimeWithRecordStorage: processing id 10, dataType 2-val and 4 data bytes
Info:TuyaMCU:V0_ParseRealTimeWithRecordStorage: int32 350
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Info:MAIN:Time 19, idle 313858/s, free 58320, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Info:MAIN:Time 20, idle 193190/s, free 58320, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:GEN:dhcp=0 ip=192.168.1.72 gate=192.168.1.1 mask=255.255.255.0 mac=d8:d6:68:9e:e8:7d
Info:GEN:sta: 1, softap: 0, b/g/n
Info:GEN:sta:rssi=-81,ssid=SALON,bssid=10:fe:ed:76:04:0c,channel=1,cipher_type:Error
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Info:MAIN:Time 24, idle 187143/s, free 58320, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Error:CMD:cmd again:y NOT found (args )
Info:TuyaMCU:Received: 55 AA 00 05 00 08 0C 02 00 04 00 00 00 4B 69 
Info:TuyaMCU:ProcessIncoming[v=0]: cmd 5 (WiFiSelect) len 15
Info:TuyaMCU:V0_ParseRealTimeWithRecordStorage: processing id 12, dataType 2-val and 4 data bytes
Info:TuyaMCU:V0_ParseRealTimeWithRecordStorage: int32 75
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Info:MAIN:Time 26, idle 186859/s, free 58320, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Info:MAIN:Time 31, idle 179048/s, free 58304, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Info:MAIN:Time 33, idle 189492/s, free 58304, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Error:CMD:cmd again:y NOT found (args )
Info:TuyaMCU:Received: 55 AA 00 05 00 08 12 02 00 04 00 00 00 3C 60 
Info:TuyaMCU:ProcessIncoming[v=0]: cmd 5 (WiFiSelect) len 15
Info:TuyaMCU:V0_ParseRealTimeWithRecordStorage: processing id 18, dataType 2-val and 4 data bytes
Info:TuyaMCU:V0_ParseRealTimeWithRecordStorage: int32 60
Info:MAIN:Time 35, idle 185815/s, free 58320, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Error:CMD:cmd again:y NOT found (args )
Info:MAIN:Time 42, idle 542106/s, free 58304, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Error:CMD:cmd again:y NOT found (args )
Info:TuyaMCU:Received: 55 AA 00 05 00 08 01 02 00 04 00 00 00 EE 01 
Info:TuyaMCU:ProcessIncoming[v=0]: cmd 5 (WiFiSelect) len 15
Info:TuyaMCU:V0_ParseRealTimeWithRecordStorage: processing id 1, dataType 2-val and 4 data bytes
Info:TuyaMCU:V0_ParseRealTimeWithRecordStorage: int32 238
Info:GEN:CHANNEL_Set channel 1 has changed to 238 (flags 0)

Info:MQTT:Channel has changed! Publishing 238.000000 to channel 1 
Info:MQTT:Publishing val 238.000000 to obk689EE87D/1/get retain=0
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic obk689EE87D/1/get
Info:MQTT:Publishing val {"Temperature":238,"Humidity":0,"Battery to obk689EE87D/DATA/get retain=0
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic obk689EE87D/DATA/get
Info:MAIN:Time 46, idle 188008/s, free 58304, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:MQTT:Publishing val TiW_Disp_1 to obk689EE87D/host retain=0
Info:MQTT:Publishing val OpenBK7231N 1.17.780 Nov 29 2024 09:48:51 to obk689EE87D/build retain=0
Info:MQTT:Publishing val d8:d6:68:9e:e8:7d to obk689EE87D/mac retain=0
Info:MQTT:Publishing val 35.37 to obk689EE87D/temp retain=0
Info:MQTT:Publishing val SALON to obk689EE87D/ssid retain=0
Info:MQTT:Publishing val 1734909423 to obk689EE87D/datetime retain=0
Info:MQTT:Publishing val 2 to obk689EE87D/sockets retain=0
Info:MQTT:Publishing val -82 to obk689EE87D/rssi retain=0
Info:MQTT:Publishing val 47 to obk689EE87D/uptime retain=0
Info:MQTT:Publishing val 58016 to obk689EE87D/freeheap retain=0
Info:MQTT:Publishing val 192.168.1.72 to obk689EE87D/ip retain=0
Info:MQTT:Channel has changed! Publishing 238.000000 to channel 1 
Info:MQTT:Publishing val 238.000000 to obk689EE87D/1/get retain=0
Info:MQTT:Channel has changed! Publishing 49.000000 to channel 2 
Info:MQTT:Publishing val 49.000000 to obk689EE87D/2/get retain=0
Info:MQTT:Channel has changed! Publishing 0.000000 to channel 3 
Info:MQTT:Publishing val 0.000000 to obk689EE87D/3/get retain=0
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic obk689EE87D/1/get
Info:MQTT:Channel has changed! Publishing 0.000000 to channel 4 
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic obk689EE87D/2/get
Info:MQTT:Publishing val 0.000000 to obk689EE87D/4/get retain=0
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic obk689EE87D/3/get
Info:MAIN:Time 48, idle 223341/s, free 58016, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:MAIN:Time 50, idle 189749/s, free 58320, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:GEN:dhcp=0 ip=192.168.1.72 gate=192.168.1.1 mask=255.255.255.0 mac=d8:d6:68:9e:e8:7d
Info:GEN:sta: 1, softap: 0, b/g/n
Info:GEN:sta:rssi=-78,ssid=SALON,bssid=10:fe:ed:76:04:0c,channel=1,cipher_type:Error
Info:MAIN:Time 55, idle 157007/s, free 58320, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:MAIN:Time 57, idle 187162/s, free 58320, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:MAIN:Time 59, idle 192763/s, free 58320, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:TuyaMCU:Received: 55 AA 00 05 00 08 02 02 00 04 00 00 00 31 45 
Info:TuyaMCU:ProcessIncoming[v=0]: cmd 5 (WiFiSelect) len 15
Info:TuyaMCU:V0_ParseRealTimeWithRecordStorage: processing id 2, dataType 2-val and 4 data bytes
Info:TuyaMCU:V0_ParseRealTimeWithRecordStorage: int32 49
Info:GEN:No change in channel 2 (still set to 49) - ignoring
    .

    I now do a reboot after every configuration change previously I thought that if I pressed "Save, Run file as script thread" it would automatically start it but in this case I don't think this is the case hence the false success. From the logs it looks like only 3 channels are being sent and the configured 4. HA still "can't see" both regarding the battery.
    Why the errors in the logs for the Tuya MCU? Maybe this version negotiates commas?
    When I press the button on the sensor to turn on the display backlight, zero values of the measurements are sent to the HA.
    Is there any chance to fully support this sensor and run more channels with minimum and maximum value settings and alarms?
  • #200 21359724
    smoeller95s
    Level 3  
    To change from F to C i try the command "tuyaMcu_sendState 9 4 0" This not work.
    I Capture data, the Tuya Firmware send ObtainDPcache the sendState command send SetDP.

    Is there any other command to send the Data?

    Screenshot showing data related to the SetDP command sent by a WiFi module. Screenshot showing data communication with the Tuya WiFi module, including ObtainDPcache and QueryInitStatus commands.
  • #201 21360569
    spin55
    Level 17  
    GAAD wrote:
    Why the errors in the logs for the Tuya MCU? Maybe this version negotiates commas?


    Error:CMD:cmd again:y NOT found (args )
    Error:CMD:cmd again:y NOT found (args )
    Error:CMD:cmd again:y NOT found (args )
    Error:CMD:cmd again:y NOT found (args )
    Error:CMD:cmd again:y NOT found (args )


    again:y <--- delete y
    delay_s 0.1
    if $CH1==0 then goto again
    -----------------------------

    Added after 1 [minutes]:

    smoeller95s wrote:
    To change from F to C i try the command "tuyaMcu_sendState 9 4 0" This not work.


    Try sending the command immediately after pressing the top button so that the device wakes up and can process it.
  • #202 21360586
    p.kaczmarek2
    Moderator Smart Home  
    I think OpenBeken has some dpCache mechanism. Open docs link here:
    https://github.com/openshwprojects/OpenBK7231T_App/blob/main/docs/commands.md
    and search for dpCache
    Helpful post? Buy me a coffee.
  • #203 21363871
    smoeller95s
    Level 3  
    >>21359724

    To solve the C F Display Problem i add
    delay_s 2
    uartSendHex 55AA001000070101090400010026

    to the autoexec.bat

    Now this works fine.
  • #204 21377331
    stefan94
    Level 1  
    >>21356710

    Seeing the photos I think I have exactly the same device.

    But flashing directly to CB3S doesn’t work. Already flashed other devices with my setup. Power source should be reliable.

    SMD soldering isn’t one of my skills. So I have to wait for a friend.

    Is there maybe another way to keep the UM8005 quiet?
  • #205 21377445
    p.kaczmarek2
    Moderator Smart Home  
    Cut the traces or try to find reset pin of UM8005.

    Here's the TuyaMCU guide: https://www.elektroda.com/rtvforum/topic4038151.html
    Helpful post? Buy me a coffee.
  • #206 21377577
    GAAD
    Level 17  
    There are two problems with me:
    1. for the channel setting temperature_div10 the system behaves as if the MCU divided the value by 10 and the OBK by another 10 i.e. total by 100 and instead of 22 degrees I have 2.2 degrees. If at runtime I change the channel in OBK to temperature without dividing by 10 it displays correctly but until restart because at restart autoexec reloads and I have divided by 100.
    2 The second problem is that I don't know how to OBK set the decimal places so that the temperature is with a precision of two and the humidity without commas.
  • #207 21377579
    p.kaczmarek2
    Moderator Smart Home  
    1 This is because you have mixed up the flags.
    https://github.com/openshwprojects/OpenBK7231T_App/blob/main/docs/flags.md
    It's all about the flag:
    Code: text Expand Select all Copy to clipboard
    
[MQTT] Apply channel type multiplier on (if any) on channel value before publishing it
    .
    If you do the HASS Discovery without this flag and then include it, you will get two divisions, and from 22.2 degrees (in Tuya 222) you will get 2.22

    Generally the temperature in the OBK channels should be without splitting, the same as from the MCU goes, only the channel type visually does the splitting.

    Another option is that you have unnecessarily added scaling in linkTuyaMCUOutputToChannel.... what whole autoexec.bat do you have?

    2 You need to be more specific, what do you have in mind?
    Helpful post? Buy me a coffee.
  • #208 21377603
    GAAD
    Level 17  
    The entire autoexec looks like this:
    Code: text Expand Select all Copy to clipboard
    
clearIO
startDriver NTP
ntp_setServer 192.168.1.253
waitFor NTPState 1
ntp_timeZoneOfs 1
startDriver TuyaMCU
startDriver tmSensor

setChannelType 1 temperature_div10
linkTuyaMCUOutputToChannel 1 val 1

setChannelType 2 Humidity
linkTuyaMCUOutputToChannel 2 val 2

setChannelType 3 ReadOnly //LowMidHigh
setChannelLabel 3 "Batt_state"
linkTuyaMCUOutputToChannel 3 val 3

setChannelType 4 ReadOnly
setChannelLabel 4 "Batt_level"
linkTuyaMCUOutputToChannel 4 val 4
    .

    After a reboot on OBK:

    Temperature 24.70C (1)
    Humidity 40.0% (2)
    Channel Batt_state = 2
    Channel Batt_level = 100
    NTP (192.168.1.253): Local Time: 2025-01-05 00:54:39
    3 drivers active (TuyaMCU,tmSensor,NTP), total 36
    Channel 1 = 247.00, Channel 2 = 40.00, Channel 3 = 2.00, Channel 4 = 100.00

    So correct but in HA:

    Screenshot of the Sensory panel displaying values in Home Assistant. .

    If I now change via web in the config tab the channel to temperature without dividing by 10 without rebooting

    Screenshot of a dropdown menu with channel settings.

    then on web OBK:

    Temperature 237.0C (1)
    Humidity 40.0% (2)
    Channel Batt_state = 2
    Channel Batt_level = 100
    NTP (192.168.1.253): Local Time: 2025-01-05 01:22:46

    for this in HA:

    Screenshot displaying sensor values. .

    Is there an option analogous to ESP with this syntax:

    Code: text Expand Select all Copy to clipboard
    
sensor:
  - platform: tuya
    name: "Temperatura"
    device_class: "temperature"
    sensor_datapoint: 3
    unit_of_measurement: "°C"
    accuracy_decimals: 1
    filters:
      - multiply: 0.1
    .

    The point is also that in HA there should not be those zeros after the decimals so that I can set the temperature to have 2 decimal places and the humidity only as a total, the battery percentages also as a total.
    In addition, when I press the highlight button, zero values are automatically sent to the HA, which clutters up the statistics a bit. Maybe OBK should save these measurements somewhere?
    I didn't write this autoexec it's more of a clumsy attempt to edit the ready-made one from this thread.
  • #209 21377733
    p.kaczmarek2
    Moderator Smart Home  
    Something must be wrong. Are you using our Home Assistant Discovery?
    https://www.youtube.com/watch?v=pkcspey25V4
    Until I ran the simulator and checked:
    Screenshot of OpenBeken simulator with an electrical circuit. .
    Screenshot of the WinTest_00000000 command tool with a command field. .
    Screenshot of Home Assistant configuration for the WinTest_00000000 device using MQTT. .
    And it works:
    Home Assistant interface displaying device information and logbook. .
    Or are you adding the device manually, via configuration.yaml? If so then the rounding is on your side.

    You could also give your own yaml on the OBK side to Discovery yourself, but this should not be necessary for such a simple device.

    If you want to remember previous measurements, then setStartValue 1 -1 where 1 is the channel number of the given channel to remember.
    Helpful post? Buy me a coffee.
  • #210 21378288
    GAAD
    Level 17  
    Thank you for your help.
    The temperature and humidity are now correct.
    I unchecked as you wrote
    Flag 33 - [MQTT] Apply channel type multiplier on (if any) on channel value before publishing it
    I don't know why they were on in both thermostats.
    Current autoexec:

    Code: text Expand Select all Copy to clipboard
    
clearIO
PowerSave 1
startDriver NTP
ntp_setServer 192.168.1.253
waitFor NTPState 1
ntp_timeZoneOfs 1
startDriver TuyaMCU
startDriver tmSensor
// Flags 134743044

setChannelType 1 temperature_div10
linkTuyaMCUOutputToChannel 1 val 1

setChannelType 2 Humidity
linkTuyaMCUOutputToChannel 2 val 2

setChannelType 3 ReadOnlyLowMidHigh
setChannelLabel 3 "Batt_state"
linkTuyaMCUOutputToChannel 3 val 3

//setChannelType 4 BatteryLevelPercent
setChannelType 4 ReadOnly
setChannelLabel 4 "Batt_level"
linkTuyaMCUOutputToChannel 4 val 4
    .



    User interface showing environmental parameters and battery status for Bedroom 1 .

    And everything reads perfectly, well almost, because the channel with the battery percentage if I set it to
    "BatteryLevelPercent" it displays the percentages nicely on OBK but does not send to HA
    if I set it to "readonly" it only sends without percentages, but this is not a problem.

    Unfortunately I also had to deselect sending flags because it was making a total mess of flags above 30.
    So it works fine thank you for your help.

    Maybe someone has channel settings ready with ranges and alarms?
Reply Cool? Ranking DIY | New topic
Notify about new articles
Report a violation of the law

Topic summary

The discussion revolves around the TH08 LCD Calendar/Clock/Temperature/Humidity device, focusing on its teardown, firmware flashing, and integration with OpenBK. Users share experiences with the device's functionality, including issues with sensor readings, MQTT communication, and NTP server configuration. Key points include the necessity of desoldering RX and TX pins for successful firmware flashing, the importance of correct NTP server settings for time synchronization, and methods to maintain Wi-Fi connectivity. Users also explore power management strategies for the device, including the implications of using external power sources and the impact on battery life. Solutions for ensuring accurate temperature and humidity readings are discussed, along with troubleshooting steps for connectivity issues.
Summary generated by the language model.
Popular Topics
ADVERTISEMENT