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

123 · April 9, 2020, 2:05pm

I don’t share that opinion.

I feel that whatever was said many months ago is subject to change. As I see it, the evidence of that change is appearing slowly but surely.

SpikeyGG · April 9, 2020, 2:17pm

@bdraco I just updated to 0.108 and saw that NUT is an integration! Exciting! I removed the NUT details from my configuration.yaml file and restarted hass.io. When it came back I tried to set up my NUT integrations and apparently there’s a limit of only one NUT integration. Even though I’m pointing to a different IP address on my network for the source data, hass.io reports this message:

I guess I’ll stick with the manual configuration method for now…

– EDIT –

Haha, I guess I can’t go back. I put the entries back into my configuration.yaml, removed the integration and restarted hass.io. When it came back it “automatically discovered” two new integrations without configuration info. It looks like the only way to get those back into the system is through the “add integration” method which won’t let me add more than one.

dknt · April 9, 2020, 2:19pm

I have also experienced the modbus problem:

2020-04-09 16:00:42 WARNING (MainThread) [pymodbus.client.asynchronous] Not Importing deprecated clients. Dependency Twisted is not Installed
2020-04-09 16:00:42 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 103, in async_setup
    hub_collect[client_config[CONF_NAME]] = ModbusHub(client_config, hass.loop)
  File "/usr/src/homeassistant/homeassistant/components/modbus/__init__.py", line 175, in __init__
    self._config_delay = client_config[CONF_DELAY]
KeyError: 'delay'
2020-04-09 16:00:43 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform modbus.sensor: Unable to set up component.

modbus:
  name: hub1
  type: serial
  method: rtu
  port: /dev/ttyUSB0
  baudrate: 9600
  stopbits: 1
  bytesize: 8
  parity: N

Problem is, when trying to downgrade from console using:
ha core update --version=0.107.7
I get an error message:
unknown flag: --version

–edit
used:
ha update --version=0.107.7

aidbish · April 9, 2020, 2:21pm

Ahh, The twice yearly YAML v UI config argument has returned. YAY

decairn · April 9, 2020, 2:23pm

I am on 107 still and have had this error for a few days.

gerritv · April 9, 2020, 2:27pm

Perhaps it is that the YAML config option remains but fewer devs are using it in their implementations. Maybe you should chat directly to those integration devs not impementing that anymore, that might have an effect.

afxefx · April 9, 2020, 2:28pm

Appears to be that way as I had mine set the same way and since updating to 108 it no longer works.

Edit: Backend-selected still appears in profile on my laptop but no when I view my profile on my phone, same user though.

Edit2: Nevermind, it appears to be a bug with the dropdown menu showing the first entry, backend-selected, behind the title bar.

aidbish · April 9, 2020, 2:29pm

Your correct it is up to the the DEV of an integration which methods he supports, yaml, ui or both. They are not forced to support both methods

Thomy · April 9, 2020, 2:34pm

Thanks for sharing this workaround!
My temporary solution is:
Manually toggle all the switches by calling the switch.toggle service after a Home Assistantant restart. This way, the entities are back to Lovelace somehow as long as I’m not restarting…
Not very feasible, but I’m confident the myStrom Integration will be fixed soon.

bdraco · April 9, 2020, 2:41pm

@SpikeyGG Would you please open an issue here:

It should allow multiple devices.

123 · April 9, 2020, 2:49pm

My guess is that the configuration info remained available in one (or more) of the JSON files located in the .storage sub-directory. If I were faced with the same situation, and wanted to revert to using configuration.yaml, I would backup the contents of .storage, shutdown Home Assistant, and use a text editor to find and remove anything related to NUT. Don’t skip making a backup because if you corrupt a file’s contents you may prevent Home Assistant from starting normally.

Vartkat · April 9, 2020, 3:02pm

Hi,

Running Docker on Ubuntu 19 on Rasp 4.
I just ran Check Home Assistant configuration, current version 107.7 target version 108.1.

The log says :


[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] udev.sh: executing... 
starting version 3.2.9
[16:43:51] INFO: Update udev information
[cont-init.d] udev.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[16:43:51] INFO: Setup udev devices
[16:43:56] INFO: Don't worry, this temporary installation is not overwriting your current one.

[16:43:56] INFO: Installing Home Assistant: latest...
[16:43:56] INFO: Please be patient, this might take a few minutes...
[16:46:02] INFO: Installed Home Assistant 0.108.1
[16:46:02] INFO: Making a copy of your configuration for checking...
[16:46:08] INFO: Checking your configuration against this version...
[16:52:20] ERROR: The configuration check did not pass!
[16:52:20] ERROR: See the output below for more details.
INFO:homeassistant.util.package:Attempting install of colorlog==4.1.0
Testing configuration at /tmp/config
INFO:homeassistant.util.package:Attempting install of influxdb==5.2.3
INFO:homeassistant.util.package:Attempting install of hass-nabucasa==0.32.2
INFO:homeassistant.util.package:Attempting install of home-assistant-frontend==20200407.1
INFO:homeassistant.util.package:Attempting install of PyNaCl==1.3.0
INFO:homeassistant.util.package:Attempting install of defusedxml==0.6.0
INFO:homeassistant.util.package:Attempting install of netdisco==2.6.0
INFO:homeassistant.util.package:Attempting install of distro==1.4.0
INFO:homeassistant.util.package:Attempting install of aiohttp_cors==0.7.0
INFO:homeassistant.util.package:Attempting install of HAP-python==2.8.1
INFO:homeassistant.util.package:Attempting install of sqlalchemy==1.3.15
INFO:homeassistant.util.package:Attempting install of mutagen==1.43.0
INFO:homeassistant.util.package:Attempting install of gTTS-token==1.1.3
INFO:homeassistant.util.package:Attempting install of aiosysbus==0.1.3
INFO:homeassistant.util.package:Attempting install of aiofreepybox==0.0.8
INFO:homeassistant.util.package:Attempting install of python-nmap==0.6.1
INFO:homeassistant.util.package:Attempting install of getmac==0.8.1
INFO:homeassistant.util.package:Attempting install of meteofrance==0.3.7
INFO:homeassistant.util.package:Attempting install of vigilancemeteo==3.0.0
INFO:homeassistant.util.package:Attempting install of xml2dict
Failed config
  General Errors: 
    - Component error: securitas_direct - No module named 'xmltodict'

Successful config (partial)
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

I believe this means xmltodict is missing from the docker image (correct me if I’m wrong), so I have to install it but I don’t know

in which docker container I have to do that (Supervisor or HomeAssistant ?)
How to do it so that it’s permanent in Docker ?

If I’m wrong what should I do ?

Thanks for helping.
V.

Artekus · April 9, 2020, 3:06pm

Was just quick feedback after trying it out. I expected the integration to work out of the chute since it only required Username and Password -its a fresh install I’m working with. I’ll follow up with a separate post with more details for figuring it out. I wasn’t expecting an answer on this post.

Thanks for the constructive criticism.

Canedje · April 9, 2020, 3:24pm

I do have exactly the same.
Broadlink is broken in 108.1
None are working.
Somebody know the solution?

mcarty · April 9, 2020, 3:41pm

I was hoping for a fix in 0.108.1 .
Guess we will have to wait…

Canedje · April 9, 2020, 3:43pm

I did a downgrade to 107.7
Broadlink is working fine again.

I will do an ugrade to 108.1 to see if something is written in the logfile about broadlink.
Someone already did find some error login about Broadlink?

did somebody already made an issue on Github?
I did an upgrade again to 0.108.1 to see the log. No logs about Broadlink.

I will again go back to 107.7 until Broadlink is fixed in the next 108.x version

I’m running HA on a Raspberry PI 4+ 4Gb

sgw · April 9, 2020, 3:49pm

Is json_attributes still working in the REST platform?

dshokouhi · April 9, 2020, 3:51pm

Did you read the breaking changes?

rodrigocoelho · April 9, 2020, 4:00pm

I still can’t upgrade to 0.108.1.

ha core update --version=0.108.1 finishes without any error, but the docker image is still 0.107.7

I tried to downgrade to 0.106.5 using ha core update and worked as expected. Tried again to upgrade using ha core update to 0.108.1, and it remained on 0.106.5. So, I updated to 0.107.7 and worked.

No way to update to 0.108.1

Any idea?

Thanks

sgw · April 9, 2020, 4:22pm

I did.
I see: " Support for json_attributes is removed from MQTT sensor, json_attributes_topic should be used instead."
I just want to be sure that there was no omission in the breaking changes for json_attributes in general, and that my REST sensors do not need to be updated.