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

Warning: Entity implements HVACMode(s): heat, off, auto and therefore implicitly supports the turn_on/turn_off methods... #162

Closed
keesma opened this issue Feb 8, 2024 · 3 comments

Comments

@keesma
Copy link

keesma commented Feb 8, 2024

Describe the bug
I found this in the home assistant log after startup.
This might be related to issue #156

2024-02-07 23:33:02.238 WARNING (MainThread) [homeassistant.components.climate] Entity climate.01:026398 (<class 'custom_components.ramses_cc.climate.RamsesController'>) implements HVACMode(s): heat, off, auto and therefore implicitly supports the turn_on/turn_off methods without setting the proper ClimateEntityFeature. Please create a bug report at https://github.com/zxdavb/ramses_cc/issues

HVAC is a Buva Boxstream (in fact two of them are connected). I only have two remote controls to change the speed and a timer.

To Reproduce
Restart home assistant (?)

Expected behavior
No warning message.

Please complete the following information:

Screenshots
n/a

Additional context
HVAC Boxstream

@peternash
Copy link

peternash commented Feb 11, 2024

I'm seeing this warning message too. I suspect it's due to upgrading to HA 2024.2.x and this 10 month deprecation warning https://developers.home-assistant.io/blog/2024/01/24/climate-climateentityfeatures-expanded

@networkerict
Copy link

Seeing similar message: Entity climate.01:109777 (<class 'custom_components.ramses_cc.climate.RamsesController'>) implements HVACMode(s): heat, off, auto and therefore implicitly supports the turn_on/turn_off methods without setting the proper ClimateEntityFeature. Please create a bug report at https://github.com/zxdavb/ramses_cc/issues

01:109777 is my Evohome controller

@zxdavb
Copy link
Owner

zxdavb commented Feb 11, 2024

I'm seeing this warning message too. I suspect it's due to upgrading to HA 2024.2.x and this 10 month deprecation warning

Is the correct answer.

Please ignore this error message for now.

zxdavb added a commit that referenced this issue Feb 11, 2024
@zxdavb zxdavb closed this as completed Feb 11, 2024
zxdavb added a commit that referenced this issue Mar 10, 2024
* Initial config flow PoC

* Import from yaml is one-off

* Update device info as it becomes available and fix entry reload

* Majority of config flow now implenented

* Lint

* Restore support for reading remote commands from known list traits

* Working multi-stage serial port config

Plus various other tidy-up.

* known list fixes

* Add missing config translations

* Fix adding new entry and provide title for better messaging

* Better default serial port handling

* Guide user through all config on initial setup

* Primary entities use device name

* Set entity names via descriptions

* Friendly name for controller device

* Clearer label for send_packet advanced feature

* Lint

* remove debug code

* Fix discarding legacy restore_cache config on import if not present

* Remove example from schema config UI

This take up too much room and make maintenance harder.

* Ensure unique evohome controller device names

* Extend "Controler 01:123456" device naming to all system types

* Fix generated sensor entity ID

This got corrected behind the scenes before but was incorrect.

* Consistent approach to entity ID generation across all domains

* Lint

* Neaten entity descriptions

Explicitly set ramses_rf_attr so we no longer need to default these.

* Fix bad merge of message events regex match/search fix

* bump to 0.40.x

* fix #85 send_pkt fails with 18:730 as dest

* Final instead of Final[str]

* mypy work

* bump to 0.41.7

* Add description to cache clear config options step

This helps explain the new immediately clear behaviour as well as why you might want to be doing it in the first place.

* initial commit

* names should be restored if the schema is not restored

* fix #162

* evo_control test

* improve evo_control test

* tweak evo_control test

* add log file for tests

* tweak test

* tweak test

* tweak test log

* expose battery ESA more cleanly

* use WATER_HEATER_DESCRIPTIONS (for tests)

* evocontrol test - add temperature attr to namespace

* tidy up

* tidy up

* tweak test

* tidy up tests

* mypy

* minor tweak of test

* doctweak

* doctweak

* move tests folder

* lint

* correct .gitignore

* add test_setup

* doctweak

* working test

* pre-commit

* add virtual RF

* tweak test

* change required to make tests work

* refactor test

* tweak meta file

* tweak tests

* move test data

* tweak virtual RF

* tweak test data

* tweak test

* tweak tests

* tweak test_data

* tweak tests

* add services tests

* extend tests

* bugfix async_unload_entry, and changes for tests

* extend ests, mypy tests

* requirements fro HA 2024.02.x

* tweak manifest.json - add paho-mqtt

* possible bugfix #169

* assert fro bug #163

* doctweak

* use fixture

* add tests

* refactor, extend tests

* harden service schemas

* bugfix DHW_PARAMS schema

* add last tests

* doctweaks

* requirements

* isort config

* meta data

* lint

* requirements

* update requirements

* add logging for config_flow

* lint

* bump library ver (CP)

* tweak tests

* mypy fix (can CP)

* tweak requirements for HA 2024.3.0

---------

Co-authored-by: Trevor North <trevor@bugsnag.com>
@zxdavb zxdavb changed the title implements HVACMode(s): heat, off, auto and therefore implicitly supports the turn_on/turn_off methods without setting the proper ClimateEntityFeature. Warning: Entity implements HVACMode(s): heat, off, auto and therefore implicitly supports the turn_on/turn_off methods... Mar 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants