hassio-addons/addon-lovelace-migration

Lovelace Migration - Community Hass.io Add-on for Home Assistant

Community Hass.io Add-ons: Lovelace Migration

This add-on automatically converts your existing UI to the new Lovelace UI.

About

The new Lovelace UI for Home Assistant is here, and it is extremely fast, extremely customizable and extremely extensible.

Building the Lovelace UI configuration from scratch can be a bit of a daunting task, so this add-on helps create a starting point to work from. In most cases you will only need to run this add-on once, but if ever you do you need to run it again, backups of your existing ui-lovelace.yaml file are automatically created and maintained.

Click here to read more about Lovelace UI

Installation

The installation of this add-on is pretty straightforward and not different in comparison to installing any other Hass.io add-on.

1. Add our Hass.io add-ons repository to your Hass.io instance.
2. Install the "Lovelace Migration" add-on
3. Start the "Lovelace Migration" add-on
4. Navigate to http://your.domain.com:8123/lovelace to see the new UI.

NOTE: Do not add this repository to Hass.io, please use: https://github.com/hassio-addons/repository.

Docker status

Configuration

Even though this add-on is just a basic add-on, it does come with some configuration options to play around with.

Note: Remember to restart the add-on when the configuration is changed.

Lovelace Migration add-on configuration:

{
  "log_level": "info",
  "output": "/config/ui-lovelace.yaml",
  "auto_backups": true,
  "init_commands": [],
  "post_commands": []
}

Option: log_level

The log_level option controls the level of log output by the addon and can be changed to be more or less verbose, which might be useful when you are dealing with an unknown issue. Possible values are:

• trace: Show every detail, like all called internal functions.
• debug: Shows detailed debug information.
• info: Normal (usually) interesting events.
• warning: Exceptional occurrences that are not errors.
• error: Runtime errors that do not require immediate action.
• fatal: Something went terribly wrong. Add-on becomes unusable.

Please note that each level automatically includes log messages from a more severe level, e.g., debug also shows info messages. By default, the log_level is set to info, which is the recommended setting unless you are troubleshooting.

Option: output

Sets the output file location of the Lovelace config. If the file exists, it will automatically be backed up. This value is set to /config/ui-lovelace.yaml by default.

Option: auto_backups

This option allows you to enable/disable automated backups. Each time the add-on runs, it will ensure your existing Lovelace configuration is stored safely in the /backups/lovelace-migration folder.

Option: init_commands

These commands are executed before the Lovelace config file is generated. This is useful if you want to keep the backup files in a separate location.

Option: post_commands

These commands are executed after the Lovelace config file is generated. This is useful if you want to keep the backup files in a separate location.

Changelog & Releases

This repository keeps a change log using GitHub's releases functionality. The format of the log is based on Keep a Changelog.

Releases are based on Semantic Versioning, and use the format of MAJOR.MINOR.PATCH. In a nutshell, the version will be incremented based on the following:

• MAJOR: Incompatible or major changes.
• MINOR: Backwards-compatible new features and enhancements.
• PATCH: Backwards-compatible bugfixes and package updates.

Support

Got questions?

You have several options to get them answered:

• The Community Hass.io Add-ons Discord chat server for add-on support and feature requests.
• The Home Assistant Discord chat server for general Home Assistant discussions and questions.
• The Home Assistant Community Forum.
• Join the Reddit subreddit in /r/homeassistant

You could also open an issue here GitHub.

Contributing

This is an active open-source project. We are always open to people who want to use the code or contribute to it.

We have set up a separate document containing our contribution guidelines.

Thank you for being involved! 😍

Authors & contributors

The original setup of this repository is by Dale Higgs.

For a full list of all authors and contributors, check the contributor's page.

We have got some Hass.io add-ons for you

Want some more functionality to your Hass.io Home Assistant instance?

We have created multiple add-ons for Hass.io. For a full list, check out our GitHub Repository.

License

MIT License

Copyright (c) 2018-2019 Dale Higgs

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

addon-lovelace-migration's Issues

Password is not echoed: 'Not a tty'

Problem/Motivation

Lovelace Migration erroring because of 'Not a tty'

Expected behavior

Lovelace Migration finishing everything and writing the output file

Actual behavior

Starting lovelace migration for the first time. Throws me following error:

INFO: Output file is set to: /config/ui-lovelace.yaml
TRACE: hass.config.has_value: init_commands
TRACE: hass.jq.has_value: /data/options.json .init_commands
TRACE: hass.jq: /data/options.json .init_commands | if (. == {} or . == []) then empty else . end // empty
TRACE: hass.has_value: 
/usr/lib/python3.6/getpass.py:91: GetPassWarning: Can not control echo on the terminal.
  passwd = fallback_getpass(prompt, stream)
Warning: Password input may be echoed.
Enter password: Traceback (most recent call last):
  File "/usr/lib/python3.6/getpass.py", line 69, in unix_getpass
    old = termios.tcgetattr(fd)     # a copy to save
termios.error: (25, 'Not a tty')

Steps to reproduce

I am using hass.io installed on a RPi3 with docker.

Migrate undo

Error on logs

Getting an error when i begin the add-on.

  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
    return cls.from_config(config)
  File "/root/lovelace_migrate.py", line 229, in from_config
    return super().from_config(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.

Problem in migrate

When I try to migrate the following error appears:

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
[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.

Problem/Motivation

(Why the issue was filed)

Expected behavior

(What you expected to happen)

Actual behavior

(What actually happened)

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)