0.108: Logos, Area Pages, Lovelace Entity Card, Lovelace Map History

[Robban]

You could achieve the same by just creating a custom component version where you bring back yaml. No need to fork everything.

[Skully]

I’m not seeing CPU utilization going up but it’s definitely got issues with performance. I’ve reverted back to 107.7 too for now.

[Ayoubmx (Ayoub HAJJAM)]

i’m waiting for the update where you will integrate the samsung TV NU7300

[nickrout]

In the meantime you produced no debug information or useful data.

[wmaker (Tommy Long)]

Hi Thanks @ochlocracy for adding Camera support to Alexa! I just got this working on my FireTV Stick

@ochlocracy

For this particular function, your ISP should not be involved. The echo device makes the request from your LAN to the camera stream URL. As long as domain in that URL resolves to your HA instance either local IP of HA or external IP of your router (using Hairpin-NAT), the request should not leave your network.

As I understand from this, the video stream does not go up somewhere to the cloud and back, but stays local; Something like camera->HA->router’s hairpin->AlexaDevice. Correct?

@ochlocracy

Also, If you’re using a custom Alexa skill with your own Lambda function you should be sending requests externally to Home Assistant on port 443 already; assuming you’re port forwarding from 443 to 8123 in your router.

I’m using Haaska in my setup. However I’m not using port 443, as I’ve configured Haaska to use another port. I’ve found that camera support for Alexa works fine using this other port, although I had to change the HA Alexa entity.py code to get around the 443 check. Would it be possible for you to remove the 443 check in a future release?

Thanks!

[Nie3mals (Kevin Meier)]

Hi, I have the Same!

Logger: homeassistant.core
Source: components/mystrom/switch.py:60
First occurred: 15. April 2020, 21:28:28 (1 occurrences)
Last logged: 15. April 2020, 21:28:28

Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 295, in async_add_entities
    await asyncio.gather(*tasks)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 447, in _async_add_entity
    await entity.async_update_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 284, in async_update_ha_state
    self._async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 320, in _async_write_ha_state
    state = self.state
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 612, in state
    return STATE_ON if self.is_on else STATE_OFF
  File "/usr/src/homeassistant/homeassistant/components/mystrom/switch.py", line 60, in is_on
    return bool(self.data["relay"])
KeyError: 'relay'

[skipper22hassio]

I also have a problem with HACS: Error setting up integration hacs - received exception

[umerfraz]

Quite relieved to see this sorry. It was driving me crazy, i have RM Pro 3+ and 50% of my devices have stopped working. My RF curtains Arent working but RF lights and all IR stuff is still working. I then recalled that this started happening after the upgrade and finding that other have had same problem was a relief as i started looking at other ways of controlling my curtains. I have a feeling its because of way codes are being encoded or parsed (not an expert here) which is why some are failing and some arent.

What did others do to fix this can you share please? just a roll back? any help/instructions will help.
UPDATE: saw one fellow giving instruction to roll back. appreicated.

[umerfraz]

I saw no log entry for broadlink even with debug level thats why i gave up. I dot know of any way to dig deeper. But i am planinng to downgrade now, after i test release 108.5. Some of my RF stuff is working and most isnt.

[Canedje]

There is a workaround. See earlier in this threath

[auredor]

I’ve finally updated to HA 108.1 without any issue. The sonoff integration works as before.

However, I’ve used again the “Check Home Assitant Configuration” tool against the last Home Assistant version (108.5) and the same error keep to be displayed.

So, I don’t think this is a real issue but the information is misleading and maybe there’s something wrong with this tool or with the Sonoff Integration.

My sonoff devices are managed through a custom instegration :https://github.com/AlexxIT/SonoffLAN

Hope it helps !

[sbach (Steve)]

Hi I updated to 0.108.1 and ever since, my presence detection from Unifi will say unknown after every reboot until the person is detected as ‘home’ then works as expected. I’ve updated to every version up to 0.108.5 and still happens.

[woody4165 (Woody)]

@slovenc

• Selecting your default Lovelace dashboard has been moved to the user profile page.

I can’t find this option anywhere.

I can’t find it neither.
Is it possible to combine user and dashboard?
And also have the possibility to hide primary dashboard, in my case Yaml mode, to other users?
Thanks

[firstof9]

I was able to locate it here:

[fversteegen (Frank)]

Can anyone give me some guidance on how to upload the request logos? I have read the entire GitHub page on how to do it, but am more accustomed to Photoshop then to GitHub I guess

Want to contribute to getting those in the right format, but as I don’t know how to send them it’s a bit of a challenge…

[nickrout]

Are you wanting to add logos? Submit a PR!

[tom_l]

It’s not that easy for providers with existing logos.

[woody4165 (Woody)]

Thanks, but I don’t see in what menu is been shown.
Your main dashboard is in yaml or storage mode?

[nickrout]

I am not sure what that means, perhaps I am not understanding.

[Robban]

There is an issue reported on that. https://github.com/home-assistant/core/issues/34140