Wood PelletStove Project

[cafedelmar01]

Hi Jeff,

I saw your pellet stove project Very Nice! and immediately thought of the display of my own pellet stove! I bought the stove in the Netherlands through the supplier 'Justfire.nl'. ( https://justfire.nl/ps-15-9-round-9kw.html )
The only difference is that an esp8266 is present with this wifi module, but I think the control is the same because the display you have was used on this heater before.
Would there be a certain way to find out if this control from your project could also be used for the installation of my stove?
Info about the preset chip: https://justfire.nl/media/wysiwyg/handleidingen/WiFi_Module_Handleiding_3_.pdf
Here is a picture of the early pellets stove with the same display: https://justfire.nl/media/wysiwyg/folders/folder%20kachels_ps-15-3.pdf
Installation Setup: https://justfire.nl/media/wysiwyg/handleidingen/Justfire_WIFI_Technische_montage_handleiding_Wifi_Module.pdf

At first site the motherboards look the same 🤔

Kind Regards:

Wouter Dijkstra

[jazzmonger]

ok, that is SUPER interesting!!!!! That is a D1 mini in your stove!!! And, its the exact same controller(motherboard control unit) thats in in all the stoves I reference.

take a look at this discussion - I use the exact same chip when I replace the TYWE1S chip w/ a D1 mini:
#23

the short answer is PROBABLY, YES it will work, and it will be extremely easy to reflash. just plug in a USB cable on the D1 Mini and use ESPHome to upload my basic control file:
https://github.com/jazzmonger/wood-stove-with-TYWE1S-Tuya-chip/blob/main/ESPHome%20config%20file%20for%20wood%20pellet%20stove.yaml

the communication from the display to the motherboard will likely be exactly the same. The question is does the display unit with the D1 mini use the Tuya Cloud platform for its control and are the datapoints all the same as the ones I programmed for?

SO, we need to check a few things first. a couple notes/questions:

• does the D1 Mini wifi module unplug from the display board? can you take some pics? Its not clear in the docs
• if it uses the Tuya Cloud then this is probably a slam dunk
• Having a D1 mini already installed gives you LOTs of new options. Like the Pellet level sensor, and the new real-time exhaust sensor I'm working on.

you could also try using the Tuya app and pair your D1 Mini with that. If that works, you're golden. I can also try the app they reference in one of the many display units I have. if that App works in my display, then you're golden.

I'll fire up my pellet stove in my freezing shop right now and go check it out! More soon.

[cafedelmar01]

Hi! Wauw! amazing to here you so enthausiastic about this!

This would be great if its integratable in my home automation!
Just a little extra info::

• This Justfire@Home app is based on a 'Blynk' installation ( https://blynk.io/ ) with a reverse proxy solution towards the esp on the stove
• Yes the ESP is remountable and replaceable ;)

Tomorrow i'll could take some extra pictures, the stove is running atm :)

[jazzmonger]

ok, I braved the cold in my shop and found out the JustFire@home app wouldn't connect to my wifi module. That doesn't really mean anything though.

Id still try the Tuya App with your D1 Mini. That will tell us a lot. Select Small Home Appliances/Wifi Stove in the Tuya app when you try to add it.

some additional tests:

• find the ip address the D1 min is using, your router should tell us that.
• create a new device in ESPHome. just the basics. we just want to use the logging function
• Try to connect to it over Wifi using the Log function.
• if this doesn't work, connect a USB cable to the D1 min and see if you can view logs that way.
• its possible the supplier disabled the ESP logs in the final version of their code.

if you get logs, post the first part here. it will tell s A LOT. Heres part of mine:

[09:50:56][C][wifi:504]: WiFi:
[09:50:56][C][wifi:362]:   Local MAC: 58:BF:25:D7:56:83
[09:50:56][C][wifi:363]:   SSID: [redacted]
[09:50:56][C][wifi:364]:   IP Address: 192.168.1.189
[09:50:56][C][wifi:365]:   BSSID: [redacted]
[09:50:56][C][wifi:367]:   Hostname: 'house-wood-pellet-stove'
[09:50:56][C][wifi:369]:   Signal strength: -61 dB ▂▄▆█

[09:50:56][C][uart.arduino_esp8266:104]:   RX Pin: GPIO3
[09:50:56][C][uart.arduino_esp8266:106]:   RX Buffer Size: 80
[09:50:56][C][uart.arduino_esp8266:108]:   Baud Rate: 2400 baud
[09:50:56][C][uart.arduino_esp8266:109]:   Data Bits: 8
[09:50:56][C][uart.arduino_esp8266:110]:   Parity: NONE
[09:50:56][C][uart.arduino_esp8266:111]:   Stop bits: 1
[09:50:56][C][uart.arduino_esp8266:113]:   Using hardware serial interface.
[09:50:56][C][uart.arduino_esp8266:102]: UART Bus:
[09:50:56][C][uart.arduino_esp8266:103]:   TX Pin: GPIO15
[09:50:56][C][uart.arduino_esp8266:104]:   RX Pin: GPIO13

Youre Looking for this:

[09:50:57][C][tuya:033]: Tuya:
[09:50:57][C][tuya:048]:   Datapoint 1: switch (value: ON)
[09:50:57][C][tuya:054]:   Datapoint 105: enum (value: 0)
[09:50:57][C][tuya:054]:   Datapoint 4: enum (value: 2)
[09:50:57][C][tuya:054]:   Datapoint 101: enum (value: 1)
[09:50:57][C][tuya:050]:   Datapoint 106: int value (value: 69)
[09:50:57][C][tuya:050]:   Datapoint 107: int value (value: 66)
[09:50:57][C][tuya:050]:   Datapoint 108: int value (value: 228)
[09:50:57][C][tuya:050]:   Datapoint 109: int value (value: 90)
[09:50:57][C][tuya:056]:   Datapoint 104: bitmask (value: 0)
[09:50:57][C][tuya:062]:   GPIO Configuration: status: pin 5, reset: pin 0
[09:50:57][C][tuya:068]:   Product: '{"p":"8Dj5zVjGqPSXaUgf","v":"1.0.0","m":0}'

Next, backup your D1 Mini firmware:
https://community.blynk.cc/t/how-to-backup-restore-official-firmware-on-any-espressif-esp8266-esp32/34309/3

once you get that done, you can experiment with my code and always go back if it doesn't work.

[cafedelmar01]

I have a few esp8266s laying around here so I might experiment with the esp-home install
(have no experience with esp-home)
How do I put it in logging mode? with a clean esp/install the logging option sounds perfect!

i don't want to fry or disturb the Main Control Unit (motherboard).

• I already have a copy of the original esp :) if you are interested.. ;)

[cafedelmar01]

Got exactly the same 'daughtboard' !!!

Only with an esp8266

image

[cafedelmar01]

Uploaded the excisting config received it in Home Assistent
Did find the logging!

Received this messages:

[16:29:29][D][sensor:126]: 'sensor_uptime': Sending state 460.65500 s with 0 decimals of accuracy
[16:29:35][D][sensor:126]: 'Wood Pellet Stove Signal': Sending state -63.00000 dBm with 0 decimals of accuracy
[16:29:39][E][tuya:409]: Initialization failed at init_state 0
[16:29:54][E][tuya:409]: Initialization failed at init_state 0
[16:30:09][E][tuya:409]: Initialization failed at init_state 0
[16:30:24][E][tuya:409]: Initialization failed at init_state 0
[16:30:29][D][sensor:126]: 'sensor_uptime': Sending state 520.65503 s with 0 decimals of accuracy
[16:30:35][D][sensor:126]: 'Wood Pellet Stove Signal': Sending state -64.00000 dBm with 0 decimals of accuracy
[16:30:39][E][tuya:409]: Initialization failed at init_state 0
[16:30:54][E][tuya:409]: Initialization failed at init_state 0
[16:31:09][E][tuya:409]: Initialization failed at init_state 0
[16:31:24][E][tuya:409]: Initialization failed at init_state 0

Could it be possible that the pins (RX/TX) are elsewhere?

[jazzmonger]

Ok, what did you upload? My code??

And you can't "fry" anything. The stove will work without the Wifi module plugged in.

Send me the entire beginning of the log!

[cafedelmar01]

Post it right here ?

[jazzmonger]

Yes. And send me the esp code. I'll upload it to my D1 mini.

[email protected]

where are you located??

specific questions:

• what is the version of the display board. Your pics are just blurry enough to not be able to make it out.
• I think u uploaded my code to the esp and plugged it into the stove, correct? Or are you powering it via usb and it's out of the stove??

[cafedelmar01]

Thanks! Just sent you the original backup of the esp, logging will sent asap, running a new config atm :)

• I'm located in the Netherlands

version of the board is: QNQ1_A_S3 2017-5-20 Exactley the same as yours :)

[jazzmonger]

I looked at Blynk a while ago. It interesting. It's not tuya. So that might pose some issues.

Ill do some investigation, it's possible they implemented a proprietary protocol to the UART on the display board.

You might be onto something with the rx/tx. The tywe1s used gpio 13/15 and a software based UART. I don't know why they didn't use the hardware UART in the esp.
You could try replacing this in my ESPHome file:

  - id: tywe1s_uart
    rx_pin: GPIO13 #D7 goes to RX on TYWE1S (really!)
    tx_pin: GPIO15 #D8 goes to TX on TYWE1S
    baud_rate: 9600

With this

  - id: tywe1s_uart
    rx_pin: RX #D7 goes to RX on TYWE1S (really!)
    tx_pin: TX #D8 goes to TX on TYWE1S
    baud_rate: 9600

or swap them (it's hard to know sometimes)

  - id: tywe1s_uart
    rx_pin: TX #D7 goes to RX on TYWE1S (really!)
    tx_pin: RX #D8 goes to TX on TYWE1S
    baud_rate: 9600

[jazzmonger]

Ok, try replacing the UART stuff. I'll bet that's what it is.

[cafedelmar01]

Will try it! Thanks!!

[jazzmonger]

If your display board is the same version as mine, then the Dutch company reverse engineered the Tuya protocol that's sitting inside the chip on the display board, and that is hard coded...

I'm sure they wanted the cheap Chinese control electronics & pellet stove hardware but didn't want to pay for the corporate Tuya licensing fees. It honestly wouldn't be that hard to do. It's just a serial protocol over a UART at the insane speed of 9600 baud!

I decoded part of it already as you can see in my hardware mods to the control module.
we just need to find out which GPIOS are used on the D1 Mini.... duh! ok, that's it. That's simple.... I'll trace my TYWE1S pins and tell you what to look for. We can brute force it!

[jazzmonger]

lots to report...
I frankensteined my setup and flashed your code onto a spare D1 mini I had. I had to use the esptool.py to flash it. it was stubborn.

once I got it flashed, I hacked around until I could get the app working. which I did. It connected. Then I looked at the logs. You can see my D1 go into AP mode:

[39224] Connecting to 0.0.0.0
[45497] Blynk v0.3.10 on Arduino

thats good. this is when the app registered the device on the Blynk network. Then I found the pin on the D1 that the TX line from the display goes to - D5 or GPIO14. With that connected, pressing buttons on the display I got this:

[1354077] Connecting to justfire.blynk.cc:80
[1354507] Ready (ping: 0ms).
Stove On sent
on Clock
off Clock
on Clock
off Clock
on Clock
off Clock
on Clock
off Clock
on Clock
off Clock
on Clock
off Clock

the on/offclock was me pressing any button, or the on/off. I assume its just a message received ack'd exchange.

I "think" t( but I'm not 100% sure) he other wire goes to D0. I scoped it and there is a data signal present on that wire. Its a 3.3v signal and it needs to be level converted to 5V for the display board MCU to receive commands. I didn't go further than that.

So, some combination of D0 & D5 are "probably" the Tuya UART's RX & TX inside the display unit.

the app sure does disconnect and reconnect A LOT. You probably see that on the app screen...

I don't know if this will get you where you need to be. But it does tell us a lot of info!
Keep experimenting, you might find the winning combo!

I must say, even though I don't read Dutch, the APP is 1000% better than the Tuya app.

[cafedelmar01]

This is the full log atm:

INFO Reading configuration /config/esphome/esphome-web-78234b.yaml...
INFO Updating https://github.com/esphome/esphome.git@pull/4032/head
INFO Detected timezone 'Europe/Amsterdam'
INFO Starting log output from wood-pellet-stove.local using esphome API
INFO Successfully connected to wood-pellet-stove.local
[22:04:44][I][app:102]: ESPHome version 2022.12.8 compiled on Feb 10 2023, 21:46:02
[22:04:44][C][wifi:504]: WiFi:
[22:04:44][C][wifi:362]: Local MAC: XXXXXXXXXXX
[22:04:44][C][wifi:363]: SSID: [redacted]
[22:04:44][C][wifi:364]: IP Address: 192.168.1.252
[22:04:44][C][wifi:365]: BSSID: [redacted]
[22:04:44][C][wifi:367]: Hostname: 'wood-pellet-stove'
[22:04:44][C][wifi:369]: Signal strength: -65 dB ▂▄▆█
[22:04:44][C][wifi:373]: Channel: 11
[22:04:44][C][wifi:374]: Subnet: 255.255.255.0
[22:04:44][C][wifi:375]: Gateway: XXXXXXXXXXX
[22:04:44][C][wifi:376]: DNS1: XXXXXXXXXXX
[22:04:44][C][wifi:377]: DNS2: 0.0.0.0
[22:04:44][C][logger:293]: Logger:
[22:04:44][C][logger:294]: Level: DEBUG
[22:04:44][C][logger:295]: Log Baud Rate: 115200
[22:04:44][C][logger:296]: Hardware UART: UART0
[22:04:44][C][uart.arduino_esp8266:102]: UART Bus:
[22:04:45][C][uart.arduino_esp8266:103]: TX Pin: GPIO1
[22:04:45][C][uart.arduino_esp8266:104]: RX Pin: GPIO3
[22:04:45][C][uart.arduino_esp8266:106]: RX Buffer Size: 256
[22:04:45][C][uart.arduino_esp8266:108]: Baud Rate: 9600 baud
[22:04:45][C][uart.arduino_esp8266:109]: Data Bits: 8
[22:04:45][C][uart.arduino_esp8266:110]: Parity: NONE
[22:04:45][C][uart.arduino_esp8266:111]: Stop bits: 1
[22:04:45][C][uart.arduino_esp8266:113]: Using hardware serial interface.
[22:04:45][W][uart.arduino_esp8266:127]: You're using the same serial port for logging and the UART component. Please disable logging over the serial port by setting logger->baud_rate to 0.
[22:04:45][C][uptime.sensor:031]: Uptime Sensor 'sensor_uptime'
[22:04:45][C][uptime.sensor:031]: Device Class: 'duration'
[22:04:45][C][uptime.sensor:031]: State Class: 'total_increasing'
[22:04:45][C][uptime.sensor:031]: Unit of Measurement: 's'
[22:04:46][C][uptime.sensor:031]: Accuracy Decimals: 0
[22:04:46][C][uptime.sensor:031]: Icon: 'mdi:timer-outline'
[22:04:46][C][template.sensor:023]: Template Sensor 'Wood Pellet Stove Uptime'
[22:04:46][C][template.sensor:023]: Device Class: 'timestamp'
[22:04:46][C][template.sensor:023]: State Class: ''
[22:04:46][C][template.sensor:023]: Unit of Measurement: ''
[22:04:46][C][template.sensor:023]: Accuracy Decimals: 0
[22:04:46][C][template.sensor:024]: Update Interval: never
[22:04:46][C][tuya.select:042]: Tuya Select 'ESPH House Power Select'
[22:04:46][C][tuya.select:043]: Select has datapoint ID 4
[22:04:46][C][tuya.select:044]: Options are:
[22:04:46][C][tuya.select:047]: 0: P1
[22:04:46][C][tuya.select:047]: 1: P2
[22:04:46][C][tuya.select:047]: 2: P3
[22:04:46][C][tuya.select:047]: 3: P4
[22:04:46][C][tuya.select:042]: Tuya Select 'ESPH House ECO Select'
[22:04:46][C][tuya.select:043]: Select has datapoint ID 101
[22:04:47][C][tuya.select:044]: Options are:
[22:04:47][C][tuya.select:047]: 0: ECO1
[22:04:47][C][tuya.select:047]: 1: ECO2
[22:04:47][C][tuya.sensor:028]: Tuya Sensor 'Stove-Power On'
[22:04:47][C][tuya.sensor:028]: State Class: ''
[22:04:47][C][tuya.sensor:028]: Unit of Measurement: ''
[22:04:47][C][tuya.sensor:028]: Accuracy Decimals: 0
[22:04:47][C][tuya.sensor:029]: Sensor has datapoint ID 1
[22:04:47][C][tuya.sensor:028]: Tuya Sensor 'Stove-Error Code'
[22:04:47][C][tuya.sensor:028]: State Class: ''
[22:04:47][C][tuya.sensor:028]: Unit of Measurement: ''
[22:04:47][C][tuya.sensor:028]: Accuracy Decimals: 0
[22:04:47][C][tuya.sensor:029]: Sensor has datapoint ID 104
[22:04:47][C][tuya.sensor:028]: Tuya Sensor 'Stove-ECO Mode'
[22:04:47][C][tuya.sensor:028]: State Class: ''
[22:04:47][C][tuya.sensor:028]: Unit of Measurement: ''
[22:04:48][C][tuya.sensor:028]: Accuracy Decimals: 0
[22:04:48][C][tuya.sensor:029]: Sensor has datapoint ID 101
[22:04:48][C][tuya.sensor:028]: Tuya Sensor 'Stove-Power Mode'
[22:04:48][C][tuya.sensor:028]: State Class: ''
[22:04:48][C][tuya.sensor:028]: Unit of Measurement: ''
[22:04:48][C][tuya.sensor:028]: Accuracy Decimals: 0
[22:04:48][C][tuya.sensor:029]: Sensor has datapoint ID 4
[22:04:48][C][tuya.sensor:028]: Tuya Sensor 'Stove-DP#105'
[22:04:48][C][tuya.sensor:028]: State Class: ''
[22:04:48][C][tuya.sensor:028]: Unit of Measurement: ''
[22:04:48][C][tuya.sensor:028]: Accuracy Decimals: 0
[22:04:48][C][tuya.sensor:029]: Sensor has datapoint ID 105
[22:04:48][C][tuya.sensor:028]: Tuya Sensor 'Stove-Set Temp'
[22:04:48][C][tuya.sensor:028]: State Class: ''
[22:04:48][C][tuya.sensor:028]: Unit of Measurement: ''
[22:04:48][C][tuya.sensor:028]: Accuracy Decimals: 0
[22:04:48][C][tuya.sensor:029]: Sensor has datapoint ID 106
[22:04:49][C][tuya.sensor:028]: Tuya Sensor 'Stove-Current Temp'
[22:04:49][C][tuya.sensor:028]: State Class: ''
[22:04:49][C][tuya.sensor:028]: Unit of Measurement: ''
[22:04:49][C][tuya.sensor:028]: Accuracy Decimals: 0
[22:04:49][C][tuya.sensor:029]: Sensor has datapoint ID 107
[22:04:49][C][tuya.climate:151]: Tuya Climate 'Wood Pellet Stove'
[22:04:49][C][tuya.climate:153]: Switch has datapoint ID 1
[22:04:49][C][tuya.climate:157]: Target Temperature has datapoint ID 106
[22:04:49][C][tuya.climate:159]: Current Temperature has datapoint ID 107
[22:04:49][C][homeassistant.time:010]: Home Assistant Time:
[22:04:49][C][homeassistant.time:011]: Timezone: 'CET-1CEST,M3.5.0,M10.5.0/3'
[22:04:49][C][captive_portal:088]: Captive Portal:
[22:04:49][C][mdns:103]: mDNS:
[22:04:49][C][mdns:104]: Hostname: wood-pellet-stove
[22:04:49][C][ota:093]: Over-The-Air Updates:
[22:04:50][C][ota:094]: Address: wood-pellet-stove.local:8266
[22:04:50][C][api:138]: API Server:
[22:04:50][C][api:139]: Address: wood-pellet-stove.local:6053
[22:04:50][C][api:143]: Using noise encryption: NO
[22:04:50][C][wifi_signal.sensor:009]: WiFi Signal 'Wood Pellet Stove Signal'
[22:04:50][C][wifi_signal.sensor:009]: Device Class: 'signal_strength'
[22:04:50][C][wifi_signal.sensor:009]: State Class: 'measurement'
[22:04:50][C][wifi_signal.sensor:009]: Unit of Measurement: 'dBm'
[22:04:50][C][wifi_signal.sensor:009]: Accuracy Decimals: 0
[22:04:50][C][tuya:033]: Tuya:
[22:04:50][C][tuya:036]: Initialization failed. Current init_state: 0
[22:04:50][C][tuya:041]: If no further output is received, confirm that this is a supported Tuya device.
[22:04:55][D][sensor:126]: 'sensor_uptime': Sending state 155.41200 s with 0 decimals of accuracy
[22:04:58][E][tuya:409]: Initialization failed at init_state 0
[22:05:13][E][tuya:409]: Initialization failed at init_state 0
[22:05:23][D][sensor:126]: 'Wood Pellet Stove Signal': Sending state -65.00000 dBm with 0 decimals of accuracy
[22:05:28][E][tuya:409]: Initialization failed at init_state 0
[22:05:43][E][tuya:409]: Initialization failed at init_state 0
[22:05:55][D][sensor:126]: 'sensor_uptime': Sending state 215.41299 s with 0 decimals of accuracy
[22:05:58][E][tuya:409]: Initialization failed at init_state 0
[22:06:13][E][tuya:409]: Initialization failed at init_state 0
[22:06:23][D][sensor:126]: 'Wood Pellet Stove Signal': Sending state -64.00000 dBm with 0 decimals of accuracy

Is it an good idea to change the RX and TX like u mentioned?

[cafedelmar01]

@jazzmonger RX - GPIO16 -> TX GPIO14 generate this error:

INFO Reading configuration /config/esphome/esphome-web-78234b.yaml...
INFO Updating https://github.com/esphome/esphome.git@pull/4032/head
INFO Detected timezone 'Europe/Amsterdam'
Failed config

uart: [source /config/esphome/esphome-web-78234b.yaml:45]

Pins GPIO16 and GPIO17 cannot be used as RX pins on ESP8266.
rx_pin: GPIO16
tx_pin: GPIO14
baud_rate: 9600

[jazzmonger]

try this:

tx_pin: GPIO16 #D0
rx_pin: GPIO14 #D5 < --

GPIO14 I know for sure is right and it has the datastream from the display on it.

the TX pin might one of any of the other pins on the D1 Mini...

this is what we need to solve:

[22:04:50][C][tuya:033]: Tuya:
[22:04:50][C][tuya:036]: Initialization failed. Current init_state: 0

[cafedelmar01]

Yes thats accepted, only... with the same Initialization failed :'( could it be still the wrong rx and tx pins?

[jazzmonger]

i just traced mine and I have D5/GPIO14 on your d1 mini flashed device wired to the RX pin of where the TYWE1s chip used to sit. so this should be right:
RX_pin: GPIO14

So, try playing w/ the TX line.
You have all these pins to test :)

[jazzmonger]

If that doesnt work, then the display board very well may use a different protocol than TuyaMCU.... I find it hard to believe tho since the version on your board is the same as mine.

Also, see if you can get your APP to connect w/ just RX_pin: GPIO14 defined. It should connect and if you try logging from ESPHOME
https://web.esphome.io/?dashboard_logs using Chrome or IE only.
You should see the same logs I did.

[cafedelmar01]

unfortunately... all other gpio just started for the TX along unfortunately without result :( Normally you should only receive information when connecting the RX correctly? would it be wise to go through everything for this?
Is it also possible to put the esp in some kind of listening mode? as soon as he can check what is happening in terms of supply and demand?

[jazzmonger]

yes, the TuyaMCU need to initialize. and I ran thru all the possibilities on my end...

Im afraid it might not be a Tuya implementation... after looking closer at the app

I see all kinds of problems. the temp should be normal, its not. that means the data the D1 Mini is getting on its serial line is not what it expects. when I press any button I should see the corresponding items change, like up or down. on/off should show me its on or off. I'm not seeing that happen unfortunately. The D1 is getting data from the display, it just cant interpret its protocol.

So, Im not sure what else we can try :(

[cafedelmar01]

Thanks for all the help and enthusiasm, indeed it seems that the sign on the display wants to hear something else.
Would there still be ways to find out?

[jazzmonger]

I didn't get into looking at the protocol between the D1and the display. That's all handled by the TuyaMCU piece of ESPHome. You would have to build a protocol analyzer to look at and decode that data. That is a BIG lift. Way past my skill level, for sure.