Just updated and two integrations problems:
Nest (The device is disabled by Config entry.) and my BMW integration (The device is disabled by Config entry.).
Should I delete and reinstall the integrations?
I had an issue with my Nest Thermostat which cleared after another restart.
I love the new area card. But is there any way to add switches as individual switches and not global switch? I have multiple light switches in each room and only see one on the area card. So it switches all at once. Same for power sockets. Not really that usefull to automatically add the global switch/socket/light etc.
Why not populate them each and skip the global one?
Well GitHub is where the discussions occur. It’s been that way for years. If you don’t want to take the time in participating in the conversation, then don’t. But don’t expect to make changes anywhere outside GitHub/feature requests.
It has been reported and fixed, should be in .1 release.
1 Like
Is anyone else having an issue with template entities with a device_class of timestamp showing as unknown? I have a ton of these for converting input_datetime helpers into read-only sensors for display in Lovelace and they all showing Unknown since updating to 2021.12:
template:
# Template Sensors
- sensor:
# Front Door Lock sensors
# Front Door Lock Last Activity sensor
- name: Front Door Lock Last Activity
device_class: timestamp
icon: mdi:history
state: "{{ states('input_datetime.front_door_lock_last_activity') }}"
I’m using shelly integration and my shelly switch is unreachable. it worked fine before the update and it also works fine directly on shelly app.
Which Shelly integration? The built in (core) one or shelly4hass?
The built in (core)
I had this too, immediately after upgrading on two of my five Shelly devices. I’m using the core integration. When I work up this morning, they were all working perfectly again (no changes from me).
Try reloading the integration (three dots icon).
Same here.
The MIIO integration partially works.
I have illuminance working, alarm entity unavailable and no light entity at all.
I have a lumi.gateway.v3 gateway.
I tried to remove and add it again. No luck
3 Likes
After updating the Vallox integration is broken.
Also I don’t understand the changelog “Entities provided by the Vallox integration now have unique IDs and can be adjusted from the UI” - there is no “Vallox” in the UI integrations.
1 Like
have the same error, unable to reload HA due to this error
I’m there - just don’t think most users are. If I must say - it’s also a crap attitude to take with the community considering new releases are announced here and this is where the feedback on those releases starts. Directing people over to git is great but I’d suggest the release notes should probably link to the existing feature or bug fix to aid in and expedite the resolution of reported issues / concerns.
1 Like
Can someone please share the default config to get a button working - there is no default config listed on the Button page.
I’ve tried this, and a couple of variations adding device class and so on. None work and throw errors when I try to reboot.
I’m sure I’m missing something simple.
button.yaml
garage_door:
name: Garage Door
Releases are announced on the website and are cross post on the forums, they are not announced on the forums. The actual blog on the website has everything you’re suggesting. Links to every breaking change, links to the issues page, and links to each pr. All on GitHub.
2 Likes
Release is on website and links right here to this forum thread. Your point is null and void. The actual blog does not have links to the githib for new features, it does have it for fixes.
1 Like
Scroll down a bit, it’s the issue tracker linked in the need help section prior to breaking changes.
- WLED devices can now be restarted and upgraded from Home Assistant.
This is a nice add, can’t wait to try it out.