I agree; I only mentioned it to serve as an example of how number
and select
are implemented.
I’m not sure what other integration(s) could implement a user-defined button. RESTful?
I agree; I only mentioned it to serve as an example of how number
and select
are implemented.
I’m not sure what other integration(s) could implement a user-defined button. RESTful?
I had the exact same issues. Rebooting the host fixed mine.
Usually because the custom developers do not keep up with the dev blog or the betas. And that is more a general answer than blame
Related, I think, I’m seeing this in my log after updating:
The websocket command ‘camera_thumbnail’ has been deprecated
I searched the forum and didn’t find anything about this. Is there a replacement command that performs similarly?
Not everyone uses the same integration or has the same set of automations. You can’t depend on beta testers to test each and every thing. All they do is confirm it works in their environment and most of the time that works out well. The more beta testers there are the more likely more issues will be found but you can never say they will find all issues introduced in a release.
Agree, I cant find any documentation on it either.
This rolls up all my switches (lights, fans etc…) and only shows temp, no humidity and sensor readings so unfortunately not useful at all. Am I missing something here that allows them to be expanded out individually or to be able to overwrite the default setting?
Ya, this new setup seems way less organized and clean.
When I first upgrades, I was in the camp of why drop the Supervisor menu into Configuration, same reason as everyone else more mouse clicks are bad. However, now I have been using it a couple of days it’s growing on me and the visual design of this new page I like, and think is an improvement.
For me, this along with the new visuals on Areas is a step in the right direction.
To prevent spam adding this comment here, I took the plunge and migrated my 22 Shelly devices from ShellyHass over to the official Shelly integration, when I say migrate, I mean manually set up again. Took about an hour, that includes my automations, not the end of the world and gave me an opportunity to better name everything. While ShellyHass was great for me, it looks like the official integration has now caught up on functionality and well worth considering,
Having the same issue. Flash no longer works with Hue.
Hello everyone,
Thank you to all developers for the hard job!
After added the shortcuts as explain above in menu, I appreciate the new UI. And the alert of new release is a great improvement.
Before the update I could switch in Lovelace a group direct on, now a click on the switch navigate to details and then I can switch the group with one device on! Any suggestions what I could do that I can switch the group direct on, without Detail Site?
Switches still work as they did before the update.
Are you perhaps using the custom card multiple-entity-row?
Id say a HA script
behaves just like a generic button
entity. Maybe it fits your needs too.
After the update I get an error with the Onvif integration and my Wansview cam. The following message appears after a few seconds (up to 30)
Log says:
2021-12-13 07:43:17 ERROR (stream_worker) [homeassistant.components.stream] Error from stream worker: Stream ended; no additional packets
Regarding the Alexa Media Player issue… …Restarting from the UI didn’t work for me either (Cause of the error above) but you can ssh (ex: if you have SSH& Terminal Addon installed) and run Hassio ha restart and it will work
Same issue. No flashing, no other effects, and transition times don’t work for color or brightness.
Edit: Transitions seem to have been fixed with 2021.12.1. Flashing and effects are still borked, but looks like it’s been reported.
I have a lot of devices connected to deconz which stopped working like all the Xiaomi Zigbee Sensors and devices.
Additionally i only see hue (through deconz/conbee2) light groups, but not the individual lights like before.
Is this a bug?
That’s not a switch. That’s a group.
Yes, it’s true, but it’s the consequence only. It all starts from the fact that API/framework changes very often. Likely custom components get more hits since they share the framework with core integrations. 3rd party devs are aware about this so it’s their responsibility. But still it doesn’t look nice (even for someone who doesn’t experience problems) if so many things fail every month. Also it might be discouraging for mentioned 3rd party developers. Some stability in this regard would help us all.