Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Easy enable/disable PV/SG on Heat pumps #1720

Open
proddy opened this issue Apr 26, 2024 · 5 comments
Open

Feature: Easy enable/disable PV/SG on Heat pumps #1720

proddy opened this issue Apr 26, 2024 · 5 comments
Labels
enhancement New feature or request

Comments

@proddy
Copy link
Contributor

proddy commented Apr 26, 2024

In reference to #1678 (reply in thread) and #1600

@proddy proddy added this to the v3.7.0 milestone Apr 26, 2024
@proddy proddy added the enhancement New feature or request label Apr 26, 2024
@MichaelDvP
Copy link
Contributor

I think the input configuration is a one time task. Once configured the user may want to switch the input (invert), this is n´only a write 0/1 (off/on, false/true) to the config entity, no need for a long string.
If someone really want to configure often, mybe the PV byte, he can look into the list of #1600 (comment) and create a custom entity for PV1 0x486, offset 39, UINT8.

@proddy proddy changed the title New Feature: Easy enable/disable PV/SG on Heat pumps Feature: Easy enable/disable PV/SG on Heat pumps May 8, 2024
@proddy
Copy link
Contributor Author

proddy commented Jun 21, 2024

Ok. This was an idea from @bbqkees so I'll wait until we have clear requirements.

@proddy proddy removed this from the v3.7.0 milestone Jun 21, 2024
@proddy
Copy link
Contributor Author

proddy commented Sep 15, 2024

Still not sure what this would look like (UI wise) or whether it's practical. What does the community think? Let me know....

@suaveolent
Copy link
Contributor

By changing the config I assume one would write to EEPROM. I’m not entirely sure if this is something intended to be used. In the worst case writing too often could damage the EEPROM?

@MichaelDvP
Copy link
Contributor

By changing the config I assume one would write to EEPROM. I’m not entirely sure if this is something intended to be used. In the worst case writing too often could damage the EEPROM?

I think this affects all permanent values, eg. daytemp, etc. Only very few parameters are not permanent, seltemp, selflowtemp.
I don't know what Bosch uses to store the values. If it is a eeprom we can assume 1 mio cycles. To not damage in the next 30 years you can write 90 vales a day or ~4 per hour in average.
If they use flash with fixed adresses (i hope not), it's factor 100 less, better not change more than once a day in average. But this is worst case, for flash a wear leveling is very common and lifetime depends on free extra spac, that we also no know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants