What about alarm panel? Is it going to be fixed (small digits)?
2 Likes
It’s working fine for me. Hassbian, HA 0.91 and Alexa Media Player 1.2.3.
same for me working HA 0.91 and AMP 1.2.3 working good!
I tested Preload camera and showing cam image of 5/6 hours before not real time… is a bug anyone had this problem?
Thanks, it’s also working OK for me, it’s just that I’ve not seen that error before in the logs.
Anyway I’ve only had the error show up 3 times since, and it’s still working great, so it could just be amazons server being unreachable or something like that! 
Good morning,
I updated the Home Assistant to version 0.91.
My Foscam C1 camera has stopped working in streaming video, I see the static image, but when I click to start the video roaming it loads to infinity, without showing the video.
how can i solve?
Thank you
I think they are fixing the bug in version 0.91.1
https://github.com/home-assistant/home-assistant/pull/22755
Konnected is now generating new entity ID’s every time HA is restarted, this means every time you restart you have to go into the entity register and change the entity names again.
Hi all.
On 91.1 yeelight lamps do not work with the following error in log:
module ‘yeelight’ has no attribute ‘enums’
On 91.0 they work as usual.
I’m on 0.91.1, but the battery state sensor for my iPad with the iOS app installed still shows as Unplugged instead of Not Charging:
Am I misunderstood something about this?
give it another reboot, after i updated to 91.1, there were yeelight errors, rebooted, no more errors
worth a shot
Updated to 91.1 and lost access to 3 HomeKit iSwitch’s anyone have any ideas how to get them showing up again?
I seem to be having a strange issue where the buttons on the configuration page don’t load in a new page. They seem to load as a sort of frame in the page below. Anyone else seeing the same thing? I went from 0.86 to 0.91.1.
Do you have the Custom UI component installed? That’s what was identified to cause the behavior you’ve described back in version 0.90.
The Custom UI component was updated and, I can confirm, it eliminated the problem in 0.90 and in 0.91.
Thanks for this. It certainly looks like this is the issue.
Many thanks, it worked.
Do not say such comments without any evidence to support your assertions. There has been no evidence or announcement of deprecating Z-Wave. It has been frustrating that development on OZW has been stale, but does that doesn’t mean it’s being pulled out of Home Assistant.
What is the phrase to say to make a camera show on my Home Hub or Chromecast? Do I need to do anything in the cloud component? Referring to this release note:
- Support to ask Google Assistant to show your camera on its display or on a Chromecast
Anyone having issues with “Login attempt or request with invalid authentication from 127.0.0.1”?
I’m getting hundreds of of these errors and can’t identify why. I thought it was nodered using the legacy Auth, which stopped the messages. But I’m now getting it again every few minutes.
Any ideas on how to isolate what’s causing this?
When I upgraded to 0.91.1, I had trusted sites under http. Removed those and made sure authentication is set to home assistants new method.
Am having the exact same problem with konnected. Each restart generates a new unique ID. Delecting the old entry from the entity registry gets it working again, until you restart and then new ones come along again.
Really frustrating!