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

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

On every restart of HA I am getting a newly discovered IPP printer, it is just a duplicate of the already added one. If I add, it adds another instance with these errors in the logs:

* Entity id already exists - ignoring: sensor.hp_photosmart_b110_series_black_ink. Platform ipp does not generate unique IDs
* Entity id already exists - ignoring: sensor.hp_photosmart_b110_series_cyan_ink. Platform ipp does not generate unique IDs
* Entity id already exists - ignoring: sensor.hp_photosmart_b110_series_magenta_ink. Platform ipp does not generate unique IDs
* Entity id already exists - ignoring: sensor.hp_photosmart_b110_series_yellow_ink. Platform ipp does not generate unique IDs
* Entity id already exists - ignoring: sensor.hp_photosmart_b110_series. Platform ipp does not generate unique IDs

thanks, couldn’t find it first time, saw it now :slight_smile:

so it seems, there is a problem in modbus rtu component and has suddenly stopped working in 0.108.0. This problem has been observed by many users. I also tried 108.1 & 108.2 but the component is still broken. This shows in logs.
WARNING (MainThread) [pymodbus.client.asynchronous] Not Importing deprecated clients. Dependency Twisted is not Installed

 ERROR (MainThread) [homeassistant.setup] 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_3'.

my config:

modbus:
  name: binu1
  type: serial
  method: rtu
  port: /dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0
  baudrate: 9600
  stopbits: 1
  bytesize: 8
  parity: N
-switch:
  - platform: modbus
    scan_interval: 5
    coils:
      - name: geyser
        hub: binu1
        slave: 1
        coil: 0
    registers:
      - name: first_ac      
        hub: binu1
        slave: 2
        register: 0
        command_on: 1
        command_off: 0
      - name: second_ac      
        hub: binu1
        slave: 2
        register: 1
        command_on: 1
        command_off: 0

on starting a notification says this:

Invalid config

The following integrations and platforms could not be set up:

* [modbus](https://www.home-assistant.io/integrations/modbus)
* modbus.switch

Please check your config.

I am running on Ubuntu 18.04.4 LTS docker
Anyone found the fix yet? kindly suggest?

This looks to be a bug with Google cast discovery, not with the vizio integration itself. You may want to open an issue on the GH issue tracker so someone can dig in: https://github.com/home-assistant/core/issues/new?template=BUG_REPORT.md

I did see someone else report a cast issue with 0.108 but not sure if it’s related: https://github.com/home-assistant/core/issues/33617