It’s true that a box like that looks much cooler, but it’s harder to make it compatible with all devices!
Hello, I’m following up — is there anything I can do to make progress on these topics?
1 Like
Jump in if you want to help 
No need to ask for permission — like any open-source project, PRs are open!
Has anyone been able to make progress on this topic?
For my part I finally completely removed Domoticz and integrated my heating into Gladys with Node-RED, MQTT, Z-Wave and Netatmo.
I’ve started testing what I did and it seems to work. The only thing I’m missing is a thermostat device. I can manage without one using scenes but it’s not practical to change the value manually.
So I’m hesitating to recreate a dashboard in Domoticz with these thermostats in the meantime!
I can’t wait for someone to start developing this type of device 
No development in progress to my knowledge. That said, as a first step of this development it could simply be to develop the UI of a thermostat device, with a setpoint temperature, a + button and a - button — it could be done in a few hours 
The proposal from @jgcb00 was good:
The per-room heating management part can come later.
Yes, let’s move forward little by little, especially if that allows us to have a first version of the heating management.
Yeah, totally — this device would (for me) allow managing one’s heating and would be a big step forward for Gladys.
With this device on the dashboard and two scenes to compare the temperature and the setpoint it would already make it possible to control any on/off heating system (boiler, electric radiator…)
Then, with other scenes and possibly the calendar you can create a schedule.
I don’t know what other users think, but in my case it would really be a plus.
If you look closely, a physical thermostat only works like this: it does on/off control by comparing two temperature values with schedule management.
I’m even ready to take a Gladys Plus subscription if this device could be developed.
2 Likes
It hasn’t fallen on deaf ears 
I’ll see what I can do!
It’s important to contribute — the more income I have from Gladys, the more I can free up freelance time to work on Gladys
1 Like
Don’t worry, I keep my word — I was looking for an excuse to get the subscription and contribute, so there you go, it’ll be with this device.
Sorry, the other G+ features don’t interest me so I’m hesitating to take the plunge, but if you do that I’m ready to contribute even if G+ won’t give me anything more.
Ready to test as soon as you can
2 Likes
So I was also considering as a solution placing a remote Zigbee thermostat in the rooms I need and retrieving the data I need via MQTT.
Voila ce que j’avais trouvé chez domadoo.
But it would be more expensive if I want several, since I manage my heating per room, compared to the Gladys+ subscription.
Also, I’d like to develop this thermostat myself but I haven’t yet had the time to really dig into Gladys’s code. And I also don’t know Preact.
Hi @_Will_71!
I’ve been working on this 
For now I can offer a direct control of a device in the UI:
Can be increased by clicking in 0.5 increments:
Great, the topic is moving forward
If I understand correctly, it’s up to the user to create an MQTT device « thermostat »?
A few questions:
- By default, is it one per room or a single general one?
- How do you handle the case where a thermostat per room is created (for example), but there are no sensors in that room?
- Do users necessarily have to create a thermostat via the MQTT integration?
- If so, is it possible instead to create a dedicated service (and enabled by default) in which Gladys creates the thermostats by default?
An option could also allow choosing to create one thermostat per room or only a general one.
Never mind, I didn’t have time to dig into the code but I had already set up the dev environment…
In any case I’ll look into it tonight after work…
And as promised I’ll take the Gladys+ subscription.
As with any development, you start from the core and move towards the integrations.
So for now my PR only adds this type of device to the core; there is nothing specific to any integration in the work I did.
The MQTT integration is a « flexible » integration that allows you to create « virtual devices », if I may say, controllable via MQTT.
From the moment a new device type is developed, the MQTT integration allows using this new type.
I believe that’s what @_Will_71 needed to do without Domoticz.
The next step, once this is in production, is for each integration developer to review their integration to see if « thermostat »-type peripherals exist in the integration and possibly code the compatibility
I think you didn’t quite understand the development ^^ There’s none of that, I just created a thermostat type like there are « lamp », « plug » types, etc.. Maybe the naming is wrong, should we call it « heating »?
Great, keep me posted!
And thanks for your support
Ok I see, indeed I skipped a few steps!
I had noticed it on the MQTT service, so handy for exactly what you mentioned.
It’s still a very good step, because it’s clearly a type that was missing
Thanks for your whole explanation!
1 Like
So I couldn’t wait to try it!
One remark: on PC it’s fine, no problem, and it will suit me at first to set the value, but on a phone or tablet I’m afraid the adjustment buttons will be too small! Right?
And I subscribed to Gladys+ 
.
All that’s left is to activate it, but I don’t know if I’ll have time before I go back to work!
1 Like