2021.12.b0 device_state_attributes warnings
See original GitHub issueDescribe the bug
The Home Assistant 2021.12.b0 beta version generates the following warnings:
2021-12-04 13:05:45 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.waste (<class 'custom_components.garbage_collection.sensor.GarbageCollection'>) implements device_state_attributes. Please report it to the custom component author.
2021-12-04 13:05:45 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.recycling (<class 'custom_components.garbage_collection.sensor.GarbageCollection'>) implements device_state_attributes. Please report it to the custom component author.
Configuration
Do you configure the integration in YAML or Config Flow (GUI)? : YAML
garbage_collection:
sensors:
- name: "Waste" # Each week on Monday
frequency: "weekly"
collection_days: "mon"
hidden: true
- name: "Recycling" # Bi-weekly on Monday
frequency: "every-n-days"
period: 14
first_date: '2020-07-13'
hidden: true
Error log/debug information
Screenshots
Version
Integration version: 3.2.0
Home Assistant version: 2021.12.b0
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
2021.12b0 warnings · Issue #52 · pnbruckner/ha-sun2 - GitHub
Home Assistant 2021.12b0 reports a bunch of warnings for the Sun2 integration: 2021-12-04 13:04:42 WARNING (MainThread) [homeassistant.helpers.
Read more >Help with binary sensor not changing
i have the following setup, which works as a template, but the binary sensor is not changing? from config.yaml - platform: template sensors: ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Can confirm that it’s now fixed!
Ok, should be fixed in 3.21. I’d appreciate the confirmation. Thanks