Community Hass.io Add-on: Lovelace Migration

Yes @dale3h

I have disabled the ip_enable option to re-launch the add-on and now it gives me a different error.

I have a question. Should I disable ip_enable to run the add-on and then re-activate it?
or could I do something extra to quit?

172.30.32.2:
banned_at: ‘2018-08-06T23:02:33’

[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] 10-run: applying... 
[fix-attrs.d] 10-run: exited 0.
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing... 
-----------------------------------------------------------
 Hass.io Add-on: Lovelace Migration v0.2.0
 Automatically convert your existing UI to the new Lovelace UI
 From: Community Hass.io Add-ons
 By: Franck Nijhof <[email protected]>
-----------------------------------------------------------
 armhf / Resin OS 2.3.0+rev1 / HA 0.75.3 / SU 125 / stable
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
Log level is set to INFO
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] 02-updates.sh: executing... 
INFO: You are running the latest version of this add-on
[cont-init.d] 02-updates.sh: exited 0.
[cont-init.d] 10-auto-backup.sh: executing... 
[cont-init.d] 10-auto-backup.sh: exited 0.
[cont-init.d] 11-cleanup-old.sh: executing... 
[cont-init.d] 11-cleanup-old.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
INFO: Output file is set to: /config/ui-lovelace.yaml
Traceback (most recent call last):
  File "/root/lovelace_migrate.py", line 844, in <module>
    sys.exit(main())
  File "/root/lovelace_migrate.py", line 779, in main
    states_json = hass.get_states()
  File "/root/lovelace_migrate.py", line 711, in get_states
    request = self.get('/states', **kwargs)
  File "/root/lovelace_migrate.py", line 699, in get
    request.raise_for_status()
  File "/usr/lib/python3.6/site-packages/requests/models.py", line 939, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 403 Client Error: Forbidden for url: http://hassio/homeassistant/api/states
[cmd] /usr/bin/run.sh exited 1
[cont-finish.d] executing container finish scripts...
[cont-finish.d] 99-message.sh: executing... 
-----------------------------------------------------------
s6-maximumtime: warning: unable to wait for child process: Operation timed out
 v0.2.0 / armhf / Resin OS 2.3.0+rev1 / HA 0.75.3[cont-finish.d] 99-message.sh: exited 99.
[cont-finish.d] done.
[s6-finish] syncing disks.
[s6-finish] sending all processes the TERM signal.

:tada: Release v0.2.1

Full Changelog

Changed

  • Upgrades base image to v2.1.2

Questions? Join our Discord server! https://discord.me/hassioaddons
Enjoying my add-ons? Consider supporting my work: https://patreon.com/frenck

2 Likes

Hello. I Update to 0.2.1.
And this is my Error. It should be noted that I have disabled everything from ip_ban

[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] 10-run: applying... 
[fix-attrs.d] 10-run: exited 0.
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing... 
-----------------------------------------------------------
 Hass.io Add-on: Lovelace Migration v0.2.1
 Automatically convert your existing UI to the new Lovelace UI
 From: Community Hass.io Add-ons
 By: Franck Nijhof <[email protected]>
-----------------------------------------------------------
 armhf / Resin OS 2.3.0+rev1 / HA 0.76.1 / SU 127 / stable
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
Log level is set to INFO
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] 02-updates.sh: executing... 
INFO: You are running the latest version of this add-on
[cont-init.d] 02-updates.sh: exited 0.
[cont-init.d] 10-auto-backup.sh: executing... 
[cont-init.d] 10-auto-backup.sh: exited 0.
[cont-init.d] 11-cleanup-old.sh: executing... 
[cont-init.d] 11-cleanup-old.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
INFO: Output file is set to: /config/ui-lovelace.yaml
Traceback (most recent call last):
  File "/root/lovelace_migrate.py", line 844, in <module>
    sys.exit(main())
  File "/root/lovelace_migrate.py", line 779, in main
    states_json = hass.get_states()
  File "/root/lovelace_migrate.py", line 711, in get_states
    request = self.get('/states', **kwargs)
  File "/root/lovelace_migrate.py", line 699, in get
    request.raise_for_status()
  File "/usr/lib/python3.6/site-packages/requests/models.py", line 939, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 403 Client Error: Forbidden for url: http://hassio/homeassistant/api/states
[cmd] /usr/bin/run.sh exited 1
[cont-finish.d] executing container finish scripts...
[cont-finish.d] 99-message.sh: executing... 
-----------------------------------------------------------
                Oops! Something went wrong.
 
 We are so sorry, but something went terribly wrong when
 starting or running this add-on.
 
 Be sure to check the log above, line by line, for hints.
-----------------------------------------------------------
[cont-finish.d] 99-message.sh: exited 0.
[cont-finish.d] done.
[s6-finish] syncing disks.
[s6-finish] sending all processes the TERM signal.

Hello friends, I want to tell you that after I have updated to version 0.2.1 I have restarted HA and I have re-launched it, it has worked for me.

Thank you so much

@dale3h @frenck
:slight_smile:

Hi Guys

I was having the same “403 Client Error: Forbidden for url: http://hassio/homeassistant/api/states” error message which made me think, Hang on, http://blahblahblah but I am using https

so, disable https, change my base url back to http, rebooted and ran the add-on and guess what, it created my file and I now have the ui-lovelace.yaml created

Hope this helps

Hi,

Thanks to everyone for your hard work on this and HA overall! It’s great!

I’m still getting an error. I have updated my RPI3 to addon v2.1 and am still receiving errors.

Let me know how I can help. I’m also getting an error on two other development implementations, - --one in a Docker container, (Error =RecursionError: maximum recursion depth exceeded in comparison)

  • another on a RPI2 running HASSOS (same error as RPI3).

I can post those logs if it helps? Thanks!

`
----------------------------------------------------------- Hass.io Add-on: Lovelace Migration v0.2.1 Automatically convert your existing UI to the new Lovelace UI From: Community Hass.io Add-ons By: Franck Nijhof <[email protected]> ----------------------------------------------------------- armhf / Resin OS 2.3.0+rev1 / HA 0.77.2 / SU 128 / stable

File “/root/lovelace_migrate.py”, line 129, in from_config
return fx(config)
File “/root/lovelace_migrate.py”, line 277, in from_group_config
card = Lovelace.Card.from_config(entity)
File “/root/lovelace_migrate.py”, line 234, in from_config
return cls.from_config(config)
File “/root/lovelace_migrate.py”, line 229, in from_config
return super().from_config(config)
File “/root/lovelace_migrate.py”, line 129, in from_config
return fx(config)
File “/root/lovelace_migrate.py”, line 277, in from_group_config
card = Lovelace.Card.from_config(entity)
File “/root/lovelace_migrate.py”, line 234, in from_config
return cls.from_config(config)
File “/root/lovelace_migrate.py”, line 229, in from_config
return super().from_config(config)
File “/root/lovelace_migrate.py”, line 129, in from_config
return fx(config)
File “/root/lovelace_migrate.py”, line 277, in from_group_config
card = Lovelace.Card.from_config(entity)
File “/root/lovelace_migrate.py”, line 234, in from_config
return cls.from_config(config)
File “/root/lovelace_migrate.py”, line 229, in from_config
return super().from_config(config)
File “/root/lovelace_migrate.py”, line 129, in from_config
return fx(config)
File “/root/lovelace_migrate.py”, line 277, in from_group_config
card = Lovelace.Card.from_config(entity)
File “/root/lovelace_migrate.py”, line 234, in from_config
return cls.from_config(config)
File “/root/lovelace_migrate.py”, line 229, in from_config
return super().from_config(config)
File “/root/lovelace_migrate.py”, line 129, in from_config
return fx(config)
File “/root/lovelace_migrate.py”, line 277, in from_group_config
card = Lovelace.Card.from_config(entity)
File “/root/lovelace_migrate.py”, line 234, in from_config
return cls.from_config(config)
File “/root/lovelace_migrate.py”, line 229, in from_config
return super().from_config(config)
File “/root/lovelace_migrate.py”, line 129, in from_config
return fx(config)
File “/root/lovelace_migrate.py”, line 277, in from_group_config
card = Lovelace.Card.from_config(entity)
File “/root/lovelace_migrate.py”, line 234, in from_config
return cls.from_config(config)
File “/root/lovelace_migrate.py”, line 229, in from_config
return super().from_config(config)
File “/root/lovelace_migrate.py”, line 129, in from_config
return fx(config)
File “/root/lovelace_migrate.py”, line 277, in from_group_config
card = Lovelace.Card.from_config(entity)
File “/root/lovelace_migrate.py”, line 234, in from_config
return cls.from_config(config)
File “/root/lovelace_migrate.py”, line 229, in from_config
return super().from_config(config)
File “/root/lovelace_migrate.py”, line 129, in from_config
return fx(config)
File “/root/lovelace_migrate.py”, line 277, in from_group_config
card = Lovelace.Card.from_config(entity)
File “/root/lovelace_migrate.py”, line 234, in from_config
return cls.from_config(config)
File “/root/lovelace_migrate.py”, line 229, in from_config
return super().from_config(config)
File “/root/lovelace_migrate.py”, line 129, in from_config
return fx(config)
File “/root/lovelace_migrate.py”, line 277, in from_group_config
card = Lovelace.Card.from_config(entity)
File “/root/lovelace_migrate.py”, line 234, in from_config
return cls.from_config(config)
File “/root/lovelace_migrate.py”, line 229, in from_config
return super().from_config(config)
File “/root/lovelace_migrate.py”, line 129, in from_config
return fx(config)
File “/root/lovelace_migrate.py”, line 277, in from_group_config
card = Lovelace.Card.from_config(entity)
File “/root/lovelace_migrate.py”, line 234, in from_config
return cls.from_config(config)
File “/root/lovelace_migrate.py”, line 229, in from_config
return super().from_config(config)
File “/root/lovelace_migrate.py”, line 129, in from_config
return fx(config)
File “/root/lovelace_migrate.py”, line 277, in from_group_config
card = Lovelace.Card.from_config(entity)
File “/root/lovelace_migrate.py”, line 234, in from_config
[cmd] /usr/bin/run.sh exited 1
[cont-finish.d] executing container finish scripts…
[cont-finish.d] 99-message.sh: executing…
-----------------------------------------------------------
Oops! Something went wrong.

 We are so sorry, but something went terribly wrong when
 starting or running this add-on.
 
 Be sure to check the log above, line by line, for hints.
-----------------------------------------------------------
[cont-finish.d] 99-message.sh: exited 0.
[cont-finish.d] done.
[s6-finish] syncing disks.
[s6-finish] sending all processes the TERM signal.

`

Hi,

I am getting the following errors in the log. I have followed all the tips but nothing seems to work:

[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] 10-run: applying... 
[fix-attrs.d] 10-run: exited 0.
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing... 
-----------------------------------------------------------
 Hass.io Add-on: Lovelace Migration v0.2.1
 Automatically convert your existing UI to the new Lovelace UI
 From: Community Hass.io Add-ons
 By: Franck Nijhof <[email protected]>
-----------------------------------------------------------
 amd64 / Resin OS 2.3.0+rev1 / HA 0.77.2 / SU 128 / stable
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
Log level is set to INFO
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] 02-updates.sh: executing... 
[cont-init.d] 02-updates.sh: exited 0.
[cont-init.d] 10-auto-backup.sh: executing... 
[cont-init.d] 10-auto-backup.sh: exited 0.
[cont-init.d] 11-cleanup-old.sh: executing... 
[cont-init.d] 11-cleanup-old.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[cmd] /usr/bin/run.sh exited 1
[cont-finish.d] executing container finish scripts...
[cont-finish.d] 99-message.sh: executing... 
-----------------------------------------------------------
                Oops! Something went wrong.
 
 We are so sorry, but something went terribly wrong when
 starting or running this add-on.
 
 Be sure to check the log above, line by line, for hints.
-----------------------------------------------------------
[cont-finish.d] 99-message.sh: exited 0.
[cont-finish.d] done.
[s6-finish] syncing disks.
[s6-finish] sending all processes the TERM signal.

After installing a fresh image of hassio I cannot enter the UI and get this message:

Could not find ui-lovelace.yaml in your config dir

Since it’s a fresh install I have not setup Lovelace or any addon installed. How can I bypass this? (

:tada: Release v0.3.0

Full Changelog

Changed

  • Adds Hassio API security role
  • Upgrades base image to v2.3.0
  • Upgrades Python to 3.6.6-r0

Questions? Join our Discord server! https://discord.me/hassioaddons

Is it possible to use iframes and plugins with this migration?

I have tried things from My Lovelace Plugins and https://home-assistant-lovelace-gallery.netlify.com/# with no luck :frowning:

Hello

Only to give thanks to the creators. Apparently, everything worked just fine:

[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] 10-run: applying... 
[fix-attrs.d] 10-run: exited 0.
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing... 
-----------------------------------------------------------
 Hass.io Add-on: Lovelace Migration v0.3.0
 Automatically convert your existing UI to the new Lovelace UI
 From: Community Hass.io Add-ons
 By: Franck Nijhof <[email protected]>
-----------------------------------------------------------
 armhf / Resin OS 2.3.0+rev1 / HA 0.81.0 / SU 138 / stable
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
Log level is set to INFO
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] 02-updates.sh: executing... 
INFO: You are running the latest version of this add-on
[cont-init.d] 02-updates.sh: exited 0.
[cont-init.d] 10-auto-backup.sh: executing... 
[cont-init.d] 10-auto-backup.sh: exited 0.
[cont-init.d] 11-cleanup-old.sh: executing... 
[cont-init.d] 11-cleanup-old.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
INFO: Output file is set to: /config/ui-lovelace.yaml
INFO:__main__:Lovelace UI successfully written to: /config/ui-lovelace.yaml
[cmd] /usr/bin/run.sh exited 0
[cont-finish.d] executing container finish scripts...
[cont-finish.d] 99-message.sh: executing... 
[cont-finish.d] 99-message.sh: exited 0.
[cont-finish.d] done.
[s6-finish] syncing disks.
[s6-finish] sending all processes the TERM signal.

Cheers!

This is interesting. I might have to take the lovelace plunge.

Has anyone got any before and after screen shots?

No need, it looks exactly the same bar anything not supported by Lovelace but that’s mostly custom_ui bits.

1 Like

Doesn’t work on hassos 13, get an error

Followed all the tips in this thread, but still broken for me. Any ideas?

Add-On: 0.3.0
HA Version: 0.83.1
HassOS 1.12

[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] 10-run: applying... 
[fix-attrs.d] 10-run: exited 0.
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing... 
-----------------------------------------------------------
 Hass.io Add-on: Lovelace Migration v0.3.0
 Automatically convert your existing UI to the new Lovelace UI
 From: Community Hass.io Add-ons
 By: Franck Nijhof <[email protected]>
-----------------------------------------------------------
 armhf / HassOS 1.12 / HA 0.83.1 / SU 140 / stable
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
Log level is set to INFO
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] 02-updates.sh: executing... 
INFO: You are running the latest version of this add-on
[cont-init.d] 02-updates.sh: exited 0.
[cont-init.d] 10-auto-backup.sh: executing... 
[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] 10-run: applying... 
[fix-attrs.d] 10-run: exited 0.
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing... 
-----------------------------------------------------------
 Hass.io Add-on: Lovelace Migration v0.3.0
 Automatically convert your existing UI to the new Lovelace UI
 From: Community Hass.io Add-ons
 By: Franck Nijhof <[email protected]>
-----------------------------------------------------------
 armhf / HassOS 1.12 / HA 0.83.1 / SU 140 / stable
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
Log level is set to INFO
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] 02-updates.sh: executing... 
INFO: You are running the latest version of this add-on
[cont-init.d] 02-updates.sh: exited 0.
[cont-init.d] 10-auto-backup.sh: executing...

Migrated successful :+1:

 Hass.io Add-on: Lovelace Migration v0.3.0
 Automatically convert your existing UI to the new Lovelace UI
 From: Community Hass.io Add-ons
 By: Franck Nijhof <[email protected]>
-----------------------------------------------------------
 armhf / HassOS 1.13 / HA 0.83.3 / SU 140 / stable

Hello,

I used the migration addon and it generates the lovelace file.
Only thing is whatever I change it doesn’t appear in the interface. I even cleared the file but I don’t get the changes and still see what I see when I click " Try out the new Lovelace UI"

How to I activate my own ui-lovelace.yaml file ?

Ok found it I think
Had to add the following to the configuration.yaml

lovelace:
  mode: yaml

:warning: Deprecation warning

With the latest release of Home Assistant, this add-on has become obsolete.

Therefore, it is deprecated immediately and removed from the add-on store.
The source code remains on GitHub, available for anybody who is interested.

Thank you all for your interest, support and using this add-on.

:wave: