The whole api was changed for hue, check out the breaking changes.
1 Like
The context menus (at least on Apple devices) are cropped for month. UI gets partly unusable to configure. Example Philips Hue integration:
Is there any info when that will get fixed?
Check GitHub frontend repo and see if anyone even wrote that up
I raised an issue at the beginning of August.
And what has been said in it? Have you kept bumping it?
Alright, then you have all the information you need. You’ll know it’s fixed when it’s closed.
I have no information at all if the frontend guy will fix it or not. And this is far from satisfactory because they force an UI configuration but this is not possible if you can’t configure an integration in the UI.
It’s an issue, it’ll get fixed. As stated multiple times across multiple threads: Be patient or fix it yourself.
1 Like
Still working for me.
well, tbh Petro, this has been one of the most annoying Frontend issues for a long time, and being told to be patient is really not the correct attitude towards your end-users on a matter of this impact.
Fix it yourself is hardly an option either, because if the frontend dev’s cant, how could we mere mortals 
there are more issues on this, eg: https://github.com/home-assistant/frontend/issues/9416 which I have just kept alive.
Some extra effort, or at least a signal people are looking at it would be appreciated. Adding the iOS tag some weeks ago only means it has been recognized.
Id be glad to test, add logs, whatever the dev might need. Without feedback, we have to sit on our hands.
1 Like
With IOS you have no choice but to be patient because releases take so much due to Apples policies. I understand the frustration but we are all in the same boat on that.
ofc, I am aware.
though its not unique to the IOS app, that was what I tried to bring across linking my issue. the same happens in Desktop.
Hope Philip sees this, and gets back to us.
thx!
I don’t see it on desktop
Are you referring to a Mac OS desktop?
yep:
Why on earth would you have posted that. … if you have nothing useful to add , simply don’t.
1 Like
Yeah that would be why then. Im not sure if any of the devs have macs lying around. Safari/Apple has been a pita with its browser recently
Bram just said ( in my FE issue) it will be fixed next week!
1 Like
This is really a pitty, because there are such lot of bugs now for month in Safari. And most of the related github entries (and/or most of all open frontend issues) do not have a single reaction. Forntend is currently not really a topic, someone cares to solve the bugs after introducing them. And we are not talking about 1px here and there
- History overview charts not working
- energy dashboard not working (if you press any button)
- input selects not working with themes anymore
- the both topics Marius has mentioned
- etc,
Of course, all this is relying on volunteers who are on top able to code, but if so many things are not working anymore in Safari/webkit, HA is not a real cross platform UI automation system anymore. Safari/webkit is buggy, but not that unusual, as every iPad, iPhone, … is relying on it. Esp. if these users don’t have a choice to use someting else than Safari/webkit.
Really don’t know, how to get the core devs again into it or to priritze bugfixing over changing the UI, esp. if the topic of the year is streamlining. A (again) working UI is for me the most important topic in streamlining. But most probably the Safari users can only live with it.
1 Like