Skip to content

Troubleshooting

Jan Seidl edited this page Jan 6, 2022 · 5 revisions

If you've followed our installation instructions and our getting started guide, you shouldn't have any issues but I understand sometimes things can go sideways.

Enabling logging

First of all, make sure to enable at least info level (debug can be very noisy, only enable as a last-resort) logging by adding the following to your configuration.yaml.

logger:
    default: warning
    logs:
        custom_components.magic_areas: debug

If you know which feature you're debugging, you can specify which platform you want to log (e.g. media_player for Media Player Groups / Area-Aware Media Player):

logger:
    default: warning
    logs:
        custom_components.magic_areas.media_player: debug

If you're trying to debug loading issues, then it's better to enable debug globally then disable on all components

logger:
  default: warn
  logs:
    custom_components.magic_areas: debug
    custom_components.magic_areas.base: warn
    custom_components.magic_areas.binary_sensor: warn
    custom_components.magic_areas.light: warn
    custom_components.magic_areas.climate: warn
    custom_components.magic_areas.media_player: warn
    custom_components.magic_areas.sensor: warn
    custom_components.magic_areas.switch: warn
    custom_components.magic_areas.cover: warn
    custom_components.magic_areas.config_flow: warn

Usually the log messages are pretty forward towards what your issue is.

Common issues

Entity not being added to the area

If an entity fails to be added to an area, view the entity on Developer Tools or via the Entity filter menu.

Make sure the entity:

If everything else fails

Go ahead and open us a ticket! Make sure to include the relevant part of your logs and a full description of the situation.

Magic Areas Documentation

📚 Concepts

🪄 How-To

✨ Features (view all)

📒 Cookbooks (coming soon...)

  • Controlling lights' brightness
  • Automatic Turning on Fans
  • Magic Areas and Alarmo
Clone this wiki locally