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

Is anybody able to get lovelace cast to work with different lovelace panels? When I got to cast.home-assistant.io and log in, I’m not shown the extra lovelace panels. The cast.show_lovelace_view service has a parameter for dashboard-path, but even trying to call the service with that doesn’t work.

Not sure if I’m doing something wrong or it’s just not working (wanted to check before opening a bug report).

Same here!

0.108.2 modbus still not work

Logger: pymodbus.client.asynchronous
Source: components/modbus/__init__.py:6
First occurred: 8:28:35 (1 occurrences)
Last logged: 8:28:35

Not Importing deprecated clients. Dependency Twisted is not Installed
Logger: homeassistant.setup
Source: components/modbus/__init__.py:207
First occurred: 8:28:36 (1 occurrences)
Last logged: 8:28:36

Error during setup of component modbus
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/setup.py", line 171, in _async_setup_component
    hass, processed_config
  File "/usr/src/homeassistant/homeassistant/components/modbus/__init__.py", line 139, in async_setup
    await hass.async_add_executor_job(start_modbus)
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/src/homeassistant/homeassistant/components/modbus/__init__.py", line 111, in start_modbus
    client.setup()
  File "/usr/src/homeassistant/homeassistant/components/modbus/__init__.py", line 207, in setup
    loop=self._loop,
  File "/usr/local/lib/python3.7/site-packages/pymodbus/client/asynchronous/serial.py", line 75, in __new__
    yieldable = factory_class(framer=framer, port=port, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/pymodbus/client/asynchronous/factory/serial.py", line 104, in async_io_factory
    client = AsyncioModbusSerialClient(port, proto_cls, framer, loop, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/pymodbus/client/asynchronous/asyncio/__init__.py", line 689, in __init__
    self._connected_event = asyncio.Event()
  File "/usr/local/lib/python3.7/asyncio/locks.py", line 249, in __init__
    self._loop = events.get_event_loop()
  File "/usr/local/lib/python3.7/asyncio/events.py", line 644, in get_event_loop
    % threading.current_thread().name)
RuntimeError: There is no current event loop in thread 'SyncWorker_4'.

I think he mentions this in the latest state of the union

Does somebody know Broadlink is fixed in 0.108.2?

1 Like

What does it say in the changelog?

Well I did think the same but over the past 4-6 months I have looked for it several times (because this regularly has been a hot topic) but it has not turned up in my searching. Thanks for the suggestion anyway.

Broadlink works fine for me, on version 108 and now version 108.2

In both versions?
Do you use short IR commands?

@tom_l You mean this post?

4 Likes

Horizontal stack now handles different heights better

This only works in Home View, in other views there is still height differences.

1 Like

yes it worked fine in both versions, this is what’s in my config yaml:

switch:
  - platform: broadlink
    host: 192.168.0.84
    mac: "xx:xx:xx:xx:xx:xx"
    timeout: 15
    type: rm
    scan_interval: 10
    switches:
      dinning_room:
        friendly_name: "Dinning Room Lamp"
        command_on: "slYyAAYTEgcGExIHBhMGEwYTEgcGExIHBhMSBwYTEwcHExIHEgcSBwYTBhMGEwYTEgcSBwa8AAAAAAAA"
        command_off: "slwyAAYTEgcGExIHBhMGEwcTEgcGExIHBhMSBwYTEgcGExIHEgcSBwYTBhMSBxIHBhMGEwa8AAAAAAAA"

Thanks @Burningstone and @tom_l thats the one I think? I felt certain there may have been a more recent (similar) post later in 2019.

In generat got no issues with HomeAssistant upgrade (doker version). But starting with version 108.1, 108.2 the CPU utilization on Raspberry Pi 3, increased from 10% before, to 30% after upgrade. Anybody noticing the same ?
Thanks.

Yes these are very short commands. These will work.
The long ones as I mentioned in my reaction here above will not work
Thanks for sharing.

It’s not mentioned I just find out.
First I didn’t know where to check, but I did find the patch information at the bottum of the release notes

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

I can’t find this option anywhere.

at the bottom left on your name lettres

1 Like

My broadlink switches also stopped working, except one of them.
After a lot of trying to figure it out I changed the string length of one packet and it started working again and I re-learned for another switch, after about 10 attempts I found one that works again.

It is strange that it doesn’t even send the packets it doesn’t like.

Since config is now stored in JSON
and YAML is a superset of JSON.

why not generate it (in a consistent way and only if webui is used) as YAML ?

4 Likes