Hello, I have a Palazzerri stove equipped with a Connection Box that works over Wi‑Fi and offers an API; I’d like to be able to integrate it into Gladys.
Hi @Steph38230 and welcome to the Gladys forum!
Do you have a website/example of Palazetti’s APIs?
Currently there is no integration of this kind but I think it’s possible to do things either directly with Gladys scenes (with HTTP requests) or by going through node-red, to be confirmed with your feedback.
EDIT: I just discovered the project palazetti2mqtt and if it’s possible for you to set it up at your home (with help if needed) then it will be possible to control your stove with Gladys 
(provided that the APIs used by this project are the same as Palazetti’s current ones).
Hello, actually the only info I have is that an integration was made for Home Assistant and that it’s therefore technically feasible to communicate with the Connection Box. HA.IO
I’ll set up my config by the end of February. As soon
2 Likes
Hello @mutmut, now that I’ve gotten a bit familiar with Gladys, Linux and
Hi @Steph38230
I’ll try to be as explicit as possible and assume we use as much as possible of what Gladys provides and manages by default.
And regarding your question about node-red, we won’t use it (and I’m not comfortable enough with it).
1. MQTT in Gladys
So first, we’ll enable Gladys’s internal MQTT integration:
2. Docker palazzetti2mqtt
Next we’ll run the palazetti2mqtt docker in the terminal on your machine.
You need to get the IP address of your Gladys « PC » as well as that of your stove and replace them in the following command line:
docker run -d --name palazzetti2mqtt \
-e MQTT_PORT=1883 \
-e MQTT_HOST=IP_DE_GLADYS \
-e MQTT_TOPIC=palazzetti \
-e MQTT_USER=gladys \
-e MQTT_PASSWORD=MOT_DE_PASSE_MQTT_DE_GLADYS \
-e PALAZZETTI_HOST=IP_DU_POELE \
-e PALAZZETTI_PULL_STATUS=5 \
leclubber/palazzetti2mqtt
3. Verifying proper operation
To be sure everything is working correctly at this stage, I recommend using MQTT Explorer to analyze the info coming from the stove. You create a new connection, save it, connect:
We’re good
Note: I don’t have a Palazzetti stove so you might have additional info/lines.
4. Creating the commands
Now we tackle the longest part: defining the different MQTT commands to control the stove.
In Gladys’s MQTT integration, you create a new device that will contain all the stove’s functionalities (commands):
And you save it.
Then we create a first feature which is to retrieve the stove’s temperature and it should be this one in the information from MQTT Explorer (and from GitHub):
You choose Température from Température de l'appareil and add the feature:
We fill in the information and display the advanced settings:
And you save.
5. Display on dashboard
You edit your dashboard and add an Devices widget:
and you save:
No value for me because I don’t have a stove.
I’ll come back later to edit this post and add an example command (ON/OFF of the stove for example) because we’ll probably need to go through one or two scenes, I think. Enjoy your meal 
1 Like
Great, I’m traveling but I’ll look at that as soon as I get back. Many thanks…
Here are all the commands you can test directly from a scene by using an action Make an HTTP request and in POST mode (if I’m not mistaken):
This will let you verify whether you can control the stove directly without going through palazetti2mqtt (it’s a test, I have an idea in mind
).
| function | topic | value | command url |
|---|---|---|---|
| turn on | mode | heat | http://IP_DU_POELE/cgi-bin/sendmsg.lua?cmd=CMD+ON |
| turn on | mode | off | http://IP_DU_POELE/cgi-bin/sendmsg.lua?cmd=CMD+OFF |
| power level | preset | 1 | http://IP_DU_POELE/cgi-bin/sendmsg.lua?cmd=SET+POWR+1 |
| power level | preset | 2 | http://IP_DU_POELE/cgi-bin/sendmsg.lua?cmd=SET+POWR+2 |
| power level | preset | 3 | http://IP_DU_POELE/cgi-bin/sendmsg.lua?cmd=SET+POWR+3 |
| power level | preset | 4 | http://IP_DU_POELE/cgi-bin/sendmsg.lua?cmd=SET+POWR+4 |
| power level | preset | 5 | http://IP_DU_POELE/cgi-bin/sendmsg.lua?cmd=SET+POWR+5 |
| set temperature | temp | 20 | http://IP_DU_POELE/cgi-bin/sendmsg.lua?cmd=SET+SETP+20 |
| fan | fan | off | http://IP_DU_POELE/cgi-bin/sendmsg.lua?cmd=SET+RFAN+0 |
| fan | fan | 1 | http://IP_DU_POELE/cgi-bin/sendmsg.lua?cmd=SET+RFAN+1 |
| fan | fan | 2 | http://IP_DU_POELE/cgi-bin/sendmsg.lua?cmd=SET+RFAN+2 |
| fan | fan | 3 | http://IP_DU_POELE/cgi-bin/sendmsg.lua?cmd=SET+RFAN+3 |
| fan | fan | 4 | http://IP_DU_POELE/cgi-bin/sendmsg.lua?cmd=SET+RFAN+4 |
| fan | fan | 5 | http://IP_DU_POELE/cgi-bin/sendmsg.lua?cmd=SET+RFAN+5 |
| fan | fan | high | http://IP_DU_POELE/cgi-bin/sendmsg.lua?cmd=SET+RFAN+6 |
| fan | fan | auto | http://IP_DU_POELE/cgi-bin/sendmsg.lua?cmd=SET+RFAN+7 |
| function | possible topic | retrievable value | retrieval url |
|---|---|---|---|
| stove | all statuses | http://IP_DU_POELE/cgi-bin/sendmsg.lua?cmd=GET+ALLS | |
| stove | « check online » | http://IP_DU_POELE/cgi-bin/sendmsg.lua?cmd=GET+STAT | |
| stove | current_temp | room temp | T1 |
| stove | target_temp | setpoint temp | SETP |
| stove | preset | power | PWR |
| stove | fan_mode | fan | F2L |
| stove | mode | mode | STATUS |
| stove | action | mode | STATUS |
For the rows that don’t have an http, these are results from the request for all statuses (and their possible MQTT payloads).
You can probably also find info on pypalazzetti and on the WPalaControl command list
Hello, HTTP requests in the scenes work perfectly.
However, with Palazzetti2Mqtt I can’t get anything to work. I’ll try by creating MQTT « devices » and reading and controlling them via node-red
1 Like
I think it’s because we don’t have the right MQTT topics.
When you look with MQTT Explorer, do topics coming from the stove appear?
That’s great news 
My idea is to create one or several scenes that would launch the command actions or the state reads with what I was able to find.
Perhaps even one scene for control and another scene that runs every 5 minutes to retrieve states (if you change something directly on the stove, for example).
To trigger these scenes (via actuators automatically), you’ll need to create MQTT devices (some for retrieving states, others for commands) and put them on the dashboard:
When you modify one of these actuators (fan speed for example), the command scene is triggered and will send the appropriate HTTP request.
So there’s no need to go through node-red!
If you need help with the scenes, no problem to give you a hand.
However if you’re much better with node-red and prefer that, I won’t be able to help much there 
(but I’d like some feedback).
What would be interesting to know are all the possible states of your stove and to choose the ones you absolutely want.
You can post the response to http://IP_DU_POELE/cgi-bin/sendmsg.lua?cmd=GET+ALLS here if that’s ok, I’m curious to see everything the stove returns as info (except the S/N of course) and what we can use afterwards for the scenes.
In any case, from what I saw with WPalaControl, you can even create heating schedules via HTTP 
. Not necessarily useful if Gladys fully manages the stove but it’s at least possible.
1 Like
With scenes, if I want to read the setpoint temperature I make a GET request with the parameter SETP, it returns this
{
"INFO": {
"RSP": "OK",
"CMD": "GET SETP",
"TS":
},
"SUCCESS": true,
"DATA": {
"SETP": 17
}
}
How do I then retrieve this value « 17 » to assign it to an object?
Once you have clicked on Essayer, you create a new action in a block below and you retrieve the variable with {{ , a list will appear :
To put this value into an MQTT device, you will need to get its full topic :
→ in MQTT
→ in the scene
Grrr I did try the {{ … but the list only appears after typing a space after the two braces 
In any case, thanks — I’ll continue that tomorrow, and in //
2 Likes