Roadmap

[AJediIAm]

This topic contains a collection of things which should or could be implemented. It's intended as an overview. Feel free to pick up an issue and make a pull request.

Release

Ready for testing:

• Add RBE sensor Add option for RBE functionality #346
• Add sensors or parameters - how to (in this case the new power limitation) #267, Implemented power limitation, #306

Ready for release:

• Add additional sensors Added additional sensors #289

Backlog

Must: breaking bugs

Should: core functionality

• Prevent freezes when heatpump is unavailable HA freezes when heatpump is unavailable #363

Could: nice to have

• New install always has Utility Room as area, should be empty #180
• Improve error message when adding a heat pump which already exists Invalid error message when trying to adding integration #321
• Investigate startup behavior The initial value of all entities is 'unknown'. #348
• Set holiday Set holiday via Luxtronik? #45
• Add pump speed entity Possible to set pump speeds? #252
• Add circulation pump sensors Add missing sensors ID_WEB_HUPout, ID_WEB_ZW1out, ID_WEB_Zaehler_BetrZeitZWE2 #239
• Add defrost demand Add sensor for Defrost Demand (question) #294

Won't: things that don't belong

Feel free to discuss and make suggestions. It's a democratic process.

[rhammen]

@AJediIAm My view regarding the short term roadmap is the following:

1. Make a 'latest' release, based on the current main branch.

• The current latest release is from 2024.9.30, and does not work corretly anymore with current luxtronik firmwares and HA versions. We really need a new beta-release.
• Target: ~2025-10-01, depending on when you have time to create such release

2. New beta-release "redesigned config-flow"

• main change: Redesigned config-flow #430
• I can imagine taking 2) along in the new lastest release 1). There is a bit more risk that we need create an additional release in case users discover issues with the updated config flow.
• another option in taking this one along in 3)

3. New beta-release "fix coroutine never awaited"

• main change: Fix coroutine never awaited #432
• code already includes Redesigned config-flow #430
• Some open questions still to be discussed (in Fix coroutine never awaited #432)
• Try to include Multiple heatpump / hub #392 at some point in time
• Create an alpha-release beginning of October?

3. New latest release

• Once beta-releases for 3) do not show significant issues anymore

[AJediIAm]

Let's go for option 1 because it is relatively well tested at the moment. Given the unstable test and release schedule, making small incremental beta changes and promoting specific beta changes to stable seems to fit the project. Looking back at the past few months, releases are still a bit too slow and big in my opinion (mainly due to my schedule).

Releasing a beta release for option 2 for the config flow update can follow shortly after or do you prefer to include the co-routine fix as well?