Development of Heatzy service

duvalale · May 25, 2020, 9:46am

Hello everyone,

I’m making progress on the development of the Heatzy service, and I have 2 questions about « best practices » or what is generally done:

Heatzy devices do not send data; it is up to Gladys to fetch their status every X seconds by making a GET request to the corresponding API. Is there a standard way to do this, a generic interval? I haven’t found an example in the existing services yet.
For each device, there are several features, including the MODE which can take the values: [ECO, OFF, HORSGEL, COMFORT]. What is the best way to model this as a feature/category of features? I’m having a bit of trouble understanding how to best integrate the features of Heatzy devices into the Gladys model. (I also saw in another topic that the operation of devices and their features was going to be modified, perhaps it would be better to wait for this update…)

Thanks to those who can help me

pierre-gilles · May 25, 2020, 3:22pm

Yes! You need to implement a « poll » function that will be called every X seconds according to the configuration of each device.

You may have noticed that in the « t_device » table, there is an attribute « should_poll » and an attribute « poll_frequency ». If, when you create the device, you specify them, Gladys will call the « poll » function of your service every X seconds according to the specified frequency.

You can look at the example of the Philips Hue service →

github.com/GladysAssistant/Gladys

server/services/philips-hue/lib/light/light.poll.js

master

const { EVENTS, DEVICE_FEATURE_CATEGORIES, DEVICE_FEATURE_TYPES } = require('../../../../utils/constants');
const { LIGHT_EXTERNAL_ID_BASE } = require('../utils/consts');
const { xyToInt, hsbToRgb, rgbToInt, kelvinToRGB, miredToKelvin } = require('../../../../utils/colors');

const logger = require('../../../../utils/logger');
const { parseExternalId } = require('../utils/parseExternalId');
const { NotFoundError } = require('../../../../utils/coreErrors');
const { getDeviceFeature, normalize } = require('../../../../utils/device');

/**
 * @description Poll value of a Philips hue.
 * @param {object} device - The device to control.
 * @example
 * poll(device);
 */
async function poll(device) {
  const { lightId, bridgeSerialNumber } = parseExternalId(device.external_id);
  const hueApi = this.hueApisBySerialNumber.get(bridgeSerialNumber);
  if (!hueApi) {
    throw new NotFoundError(`HUE_API_NOT_FOUND`);

Ce fichier a été tronqué. afficher l'original

Or Camera:

github.com/GladysAssistant/Gladys

server/services/rtsp-camera/lib/poll.js

master

const logger = require('../../../utils/logger');

/**
 * @description Poll a camera.
 * @param {object} device - The camera to poll.
 * @example
 * poll(device);
 */
async function poll(device) {
  try {
    const cameraImage = await this.getImage(device);
    await this.gladys.device.camera.setImage(device.selector, cameraImage);
  } catch (e) {
    logger.warn('Unable to poll camera');
    logger.debug(e);
  }
}

module.exports = {
  poll,

Ce fichier a été tronqué. afficher l'original

For this, we were talking about a generic API for heating management, it goes with this debate I don’t remember, is there a topic where we talk about it?

On my side, it’s not in my short/medium term todos in terms of development, but I can give my point of view on proposals, so don’t hesitate to take the lead and start the debate on the community

duvalale · May 25, 2020, 3:44pm

Thanks for your reply, Pierre-Gilles, I’ll look into it

VonOx · December 30, 2020, 4:52pm

The service is currently in development by @duvalale. So, patience

duvalale · January 12, 2021, 9:30am

Hello @Lamyweb,

Sorry for the delayed response, I’m not seeing daylight these days
Unfortunately, I haven’t finished developing the service yet. I’m struggling to find time to work on it, and since it’s my very first service/dev on Gladys, it’s taking a while! If anyone is available to give me a hand, I’d be delighted

4get9 · February 9, 2026, 6:35pm

Hello @duvalale,

How’s your dev going?
I hope your « I haven’t seen daylight lately » period is over (it would

pierre-gilles · February 9, 2026, 6:50pm

@4get9 Their last login was in 2021, so you probably won’t get a reply in my opinion

If you want to get started, go ahead

And by the way, wouldn’t Heatzy benefit from having a Matterbridge integration to be available in Matter rather than Gladys? Both are possible

4get9 · February 10, 2026, 8:15am

Well, to be honest I don’t yet have a pilot-wire unit for my cellar (where I want to control my heaters), so it might be more relevant for me to look instead at a Matter-compatible pilot-wire heating control unit…

mutmut · February 10, 2026, 7:14pm

So I don’t know exactly what Heatzy is, but you mention a pilot wire and that gets my attention.

You mention Matter; I’d say Zigbee.
I currently have a Nodon SIN-4-FP-21 module on one of my radiators, and it lets me see the energy consumption.
1/ I was surprised to see that in frost-protection/eco mode, with 20°C in the room, the radiator was heating in regular spikes
2/ I think radiator control will be done with on/off and an external thermostat.

Anyway, long story short: either you control via z2m, or you absolutely want Matter — you can expose your z2m

ArMour85 · February 10, 2026, 8:43pm

For information on Matter and the new products, I follow the site https://www.matteralpha.com/.

Topic		Replies	Views
Gestion du chauffage native [Archive] Demande de fonctionnalités feature-request-core , chauffage	85	4529	February 10, 2023
Gladys / IKEA Dirigera / Module Zigbee : euh... comment je démarre? Configuration	23	197	March 14, 2026
Le chauffage discussion Développement	14	209	March 23, 2025
Chauffage au niveau du dashboard Développement service	12	822	May 12, 2020
Consigne thermostat Développement	6	878	December 11, 2020

Development of Heatzy service

Related topics