Multiple individual radiators being added as single accessory about homebridge-technotherm HOT 3 CLOSED

Thanks for lightning fast response, @duggan! 😃

The API response I'm getting only shows the Smartbox device, not the individual heaters. Our setups are certainly different, as you predicted.

Here's the snippet from my API response for reference:

[
    {
        "id": "cafeXXXXX",
        "name": "Home",
        "devs": [
            {
                "dev_id": "e698XXXXX",
                "name": "Smartbox",
                "product_id": "0106",
                "fw_version": "1.33.3",
                "serial_id": "12"
            }
        ],
        "owner": true
    }
]

The /api/v2/grouped_devs API isn't listing the heaters that are peered to my smartbox hub. I'll poke around their app a bit to understand how the "sub-devices" can be individually identified and controlled. I'm guessing that the product_id might be key to how the client behaves to different device types.

Thanks for putting me in the right direction! I'll come back with what I find and hopefully land a PR to add support for the DSM hubs (a.k.a. smartboxes)

from homebridge-technotherm.

Hey @Lngramos, I hope you can get it working for you!

I had my own set of these radiators installed a couple of months ago, and was told a couple of weeks before install that I'd be getting a more recent set that didn't require the smartbox, so that might be where the discrepancy is coming in.

If you enable debug mode you may be able to get enough information out of the logs to match up where my code is making assumptions about the API structure that aren't true for your own setup.

Just from what I remember of poking around with the API results, it may be that your results returned from getGroupedDevices are slightly different from mine.

If it helps, this is an example of the data I receive for groupedDevices:

[
  {
    "id": "f796dce0bc57XXXXXXXXXXXX",
    "name": "Home",
    "devs": [
      {
        "dev_id": "38a7f960XXXXXXX",
        "name": "Living Room",
        "product_id": "0433",
        "fw_version": "1.2.3",
        "serial_id": "2"
      },
      {
        "dev_id": "ef65b760XXXXXXXX",
        "name": "Ash’s Office",
        "product_id": "0433",
        "fw_version": "1.2.3",
        "serial_id": "2"
      },
      {
        "dev_id": "e882fc60XXXXXXXXX",
        "name": "Ross’s Office",
        "product_id": "0433",
        "fw_version": "1.2.3",
        "serial_id": "2"
      }
    ],
    "owner": true
  }
]

If you want to take a look at your own API results with more control rather than divining from the logs, this is how I use the client interactively:

Get an interactive Typescript prompt:

$ npx ts-node

Set up the client:

import { HelkiClient } from './src/helki_client';
const helki = new HelkiClient('api-lhz', '54bccbfb41a9a5113f0488d0', 'vdivdi', 'USERNAME', 'PASSWORD'); 

You should then be able to interact with the available methods to see what they return, and where it might be failing for you, e.g.:

const devices = await helki.getGroupedDevices();
JSON.stringify(devices);

from homebridge-technotherm.

I've raised a PR to fix the discovery for me whilst keeping it compatible with your setup.

Changing the target temperature of the heaters isn't currently working for me due to some API errors. I'll continue to look into this other issue and raise a second PR to cover this separately.

from homebridge-technotherm.