A few bizarre problems

[m4hill73-lab]

Hi firstly thanks for this project. I have a Palazzetti Elisabeth hydro stove & home assistant and it's been great at monitoring everything through homeassistant. I have now started to use the wpalacontrol to control the stove directly through home assistant and have run into some problems.

First problem, since about 09:00 on the December 23rd 2025 when the 3.5.1 firmware came out, i now have a new entity in home assistant called Stove Connectivity which seems to connect and disconnect every minute or so. The stove often now appears as unreachable in home assistant. This isn't a wifi connectivity issue as the uptime on the wpalacontrol device webpage is stable & has been stable ever since I have been using it.

The second problem comes from trying to control the stove using home assistant. If I start the stove using home assistant, the stove ignites successfully, then shuts down about 2 minutes after the green flame indicator on the pellet stove display changes from flashing to solid. There are no errors on the stove display at all. Home assistant activity logs state the stove is turned off. What is strange is that the circulation pump continues to run after the shut down and does not stop until the stove is unplugged.

The stove is currently set to mode 1, with a dry contact from an external thermostat.

If i start the stove with the external thermostat, it works fine. If i start the stove using the power on button on the display, it also works fine.

Update. If I use the palazzetti integration in home assistant to turn on the stove. It works fine.

Thanks
Martin.

[Domochip]

Hi,

What's the current version of the firmware in your WPalaControl?
And which one of Home Assistant?

[m4hill73-lab]

Hi, thanks for the reply. Wpalacontrol is 3.5.2 and home Assistant is Core
2025.12.5, Supervisor 2025.12.3, Operating System 16.3, Frontend 20251203.3
Running on bare metal. No docker etc

[Domochip]

OK, Could you try to flash to the firmware you had before and check if everything is stable?

[m4hill73-lab]

Back to 3.5.0?

[Domochip]

I think so if it was stable with this one (it is to test)

[ga3lig]

Hello,
Same problem here, with the before / after update (the "barcode" is the after) :

And for temperature :

I will make a rollback with the firmware tonight and tells if it solves the issue.

[ga3lig]

Hello,
Rollback to WPalaControl.3.5.0.bin solved this issue :

Before rollback : "barcode" due to many "became unavailable" - after rollback : normal

Note : My normal pattern is like described in issue #68 with "became unavailable" between every hour and every day, but it is not a problem for my use with homeassistant+MQTT.

[m4hill73-lab]

It seems it's not just me having problems with connectivity with 3.5.2, but at the moment I stay with 3.5.2 and use the palazzetti integration in home assistant and not MQTT, as everything is working absolutely fine for me with the Palazzetti integration.
It is so cold here at the moment that I don't want to mess with any settings!

I am using home assistant at the moment to start the stove automatically at 06:30 in the morning and also start an underfloor heating pump at the same time, then adjust water temperature & power level (1-5) during the day depending both the temperature outside and inside the house. With WpalaControl on version 3.5.2 & the Palazzetti integration this is all working perfectly. I have WPalaControl active in MQTT, but the "Stove" device disabled in MQTT

When it's not -12c outside, i'll be happy to experiment and help with anything i can. Again, thank you so much for this project

[Domochip]

Sure, I understand.
The problem I have is that I'm not able to reproduce the problem for now.
Could you share a maximum of infos about your configuration please.

[m4hill73-lab]

Update. I have figured out the 2nd problem I had in my first post. The reason I was having problems starting the stove using WpalaControl via MQTT was due to my setup, and the external thermostat I had connected to pins 8 & 7. If the external thermostat is calling for heat, then both the Palazzetti & MQTT integrations work fine. If the stove has been turned off via the external thermostat, and its no longer calling for heat, then both the MQTT & Palazzetti integrations will start the stove, ignite & run for a few minutes and then just turn the stove off with no errors.

I have also downgraded from 3.5.2 to 3.5.0 two days ago and the 'barcode' has gone away. I have not had a single connection issue since.

My configuration.
Stove - Palazzetti Elisabeth 15kw Hydro / idro stove. I am not using a cable splitter for WpalaControl, just using the cable that came in the box from tindie (bought late 2025) & it is around 6 years old.
Home assistant 2025.12.5 running on bare metal, Intel NUC N150 connected via ethernet to free.fr fibre. Remote access though cloudflare tunnel. Freebox has full stack stack IP4 fixed address
SMLIGHT SLZB-MR3 zigbee / thread coordinator connected via ethernet
Home wifi, 3 x TP link deco X50 POE all running as access points and not in router mode. I have one SSID for home use at both 2.4 & 5GHZ, and an IOT SSID at 2.4ghz only. WpalaControl is connected to the IOT SSID. Signal strength according to the Wpalacontrol webpage is normally between 50% & 70% depending.
I'm using Mosquito MQTT Broker, with no changes to default settings.

Please let me know if I can give you any more details of my configuration.