Skip to content

Add specific driver for Vimar Touch Thermostats of type 02952.b#29

Open
petero-dk wants to merge 17 commits intoathombv:masterfrom
petero-dk:device/vimar_thermostat
Open

Add specific driver for Vimar Touch Thermostats of type 02952.b#29
petero-dk wants to merge 17 commits intoathombv:masterfrom
petero-dk:device/vimar_thermostat

Conversation

@petero-dk
Copy link
Copy Markdown
Contributor

And before going into details on this implementation, I think it is worth to think about a future where all devices might not share the .homeycompose/drivers/pair/select_groupaddresses/index.html

Maybe there is a way to make it dynamic based on the settings object?

From a feature point of view this device is functioning quite well (running it now) but I am unsure about how you see the future of specific devices.

I specifically made this because it is a device that absolutely does not fit into the existing thermostat driver, and it is so specific that I don't think it would make sense to create a generic setpoint shift type thermostat.

What do you think? Because I don't see a way (new to Homey) that we could make a system like Zigbee/BLE/ZWave where other apps could be developed for specific devices? They all have to be in this repository, right?

@ttherbrink
Copy link
Copy Markdown
Contributor

Excuse the delay, We are discussing this internally

@petero-dk
Copy link
Copy Markdown
Contributor Author

Excuse the delay, We are discussing this internally

No problem, no rush for me.

Copy link
Copy Markdown
Contributor

@ttherbrink ttherbrink left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't forget to translate the setting labels/hints and the flow labels to dutch if you are able to.
Also it would be nice to have a custom icon and images for this device. You can request the icon here: https://github.com/athombv/homey-vectors-public

@petero-dk petero-dk force-pushed the device/vimar_thermostat branch from 24fd9b0 to d32c664 Compare August 26, 2025 13:58
@petero-dk
Copy link
Copy Markdown
Contributor Author

Excuse the delay, We are discussing this internally

Did you ever determine whether this would be better as part of the knx add-in or as a standalone add-in that builds on the KNX lib like Zigbee? And if so, how would that work?

p.s. sorry for the extreemly long delay in getting back on this, but was completely swamped.

@petero-dk
Copy link
Copy Markdown
Contributor Author

petero-dk commented Aug 29, 2025

I have rebased the branch to the most current version on main, and I have addressed the issues, and fixed a single bug. This has been running on my Homey since it was created and seems quite stable.

Sorry for the very long response time @MerelHudepohl @ttherbrink

@petero-dk
Copy link
Copy Markdown
Contributor Author

I will fix the linting issues

@petero-dk
Copy link
Copy Markdown
Contributor Author

@ttherbrink I have fixed the linting issues and cleaned a little bit of coding styles.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

3 participants