Where are my config files now?

[lucac81]

I’ve jumped from a 0.79 version to the latest, and while slick, I’m a bit confused.
Where are my configs now? I have installed a couple of integrations from the UI but I cannot find them in yaml files
Some integrations just don’t work, so I put them again in configuration.yaml (yeelight and xiaomi_miio for a vacuum)
My automations, luckily are in my old automations.yaml, but it is confusing, I cannot set properties all properties if I use a device from integrations, but I get back my old automations by calling a service with an entity.
Areas are a mistery, since they seems to work only for integrations… how I can “assign” a device to a room? (I now I can set the in lovelace but it’s bothering me to see areas in some entity and in others not)
I’m using mqtt autodiscovery with zigbee2mqtt, where are the discovered entities written? if I config permit_join false can I have a static file with all my entities mapped?
also there is one that is not getting the friendly_name that is setup by z2m and continues to refer to it is id, how can I change it?

Is there a way to get rid of integrations and return to old yaml files?
My setup is working right now, and I’m happy of the progresses of home-assistant ,but this situation is puzzling me, since I don’t know how can I put my config to git and configure an ansible script to setup a full recovery

[petro]

@lucac81

I have installed a couple of integrations from the UI but I cannot find them in yaml files

THey aren’t in yaml files. You shouldn’t need to ‘reconfigure’ or change anything. If it doesn’t work, then remove the integration and start again.

@lucac81

configuration.yaml (yeelight and xiaomi_miio

check your log for errors with yeelight and xiamo_miio. You can also see the logs in the UI through Configuration → logs.

@lucac81

My automations, luckily are in my old automations.yaml, but it is confusing, I cannot set properties all properties if I use a device from integrations, but I get back my old automations by calling a service with an entity.

I don’t know what you mean by this. If you’re using the automation editor, you can switch from a device trigger to a state trigger, etc. Device triggers are just a new trigger method. If it doesn’t do what you want to do, switch to another trigger type.

@lucac81

Areas are a mistery, since they seems to work only for integrations… how I can “assign” a device to a room? (I now I can set the in lovelace but it’s bothering me to see areas in some entity and in others not)

You can’t. It needs to come from an integration in order to assign to an area. Areas pretty much only auto generate your UI, like groups did in the old interface. You can take control of your interface and completely ignore areas.

@lucac81

I’m using mqtt autodiscovery with zigbee2mqtt, where are the discovered entities written?

auto discovered items are placed in .storage. A hidden folder inside your config. Be warned, these are not yaml files and they are not meant to be altered.

@lucac81

if I config permit_join false can I have a static file with all my entities mapped?

Sorry, don’t know the answer

@lucac81

also there is one that is not getting the friendly_name that is setup by z2m and continues to refer to it is id, how can I change it?

Change it through the UI. Either through customizations or go to the integration and click on entities and adjust it there.

@lucac81

Is there a way to get rid of integrations and return to old yaml files?

No.

@lucac81

My setup is working right now, and I’m happy of the progresses of home-assistant ,but this situation is puzzling me, since I don’t know how can I put my config to git and configure an ansible script to setup a full recovery

Use snapshots. But this depends on what installation method you chose. What did you use?

Also, if you really want to use git. Just pull your whole config folder. As I stated before, there’s hidden folders that contain this information inside your config folder.

[lucac81]

@petro

THey aren’t in yaml files. You shouldn’t need to ‘reconfigure’ or change anything. If it doesn’t work, then remove the integration and start again.

it can be ok, but still I have yaml files with custom sensors and automations that depend on what the integration provide (and I have to dig inside the ui to find the entities provided by the integration)

@petro

check your log for errors with yeelight and xiamo_miio. You can also see the logs in the UI through Configuration → logs.

No log from yeelight integration, just a generic ui error
and the xiaomi_miio integration wants to connect only to a mi gateway not the vacumm, that works fine using

vacuum:
  - platform: xiaomi_miio

@petro

I don’t know what you mean by this. If you’re using the automation editor, you can switch from a device trigger to a state trigger, etc. Device triggers are just a new trigger method. If it doesn’t do what you want to do, switch to another trigger type.

what I mean is that working with the concept of devices from an integration limits what I can do with that component for example:

  trigger:
  - platform: sun
    event: sunset
  condition: []
  action:
  - service: light.turn_on
    data:
      transition: 600
      color_temp: 324
      brightness: 255
    entity_id: light.terrazzo

the data part over there is simply not available for a device, it is limited to just the brightness, so what is the purpose of exposing a device instead of the entity?

@petro

You can’t. It needs to come from an integration in order to assign to an area. Areas pretty much only auto generate your UI, like groups did in the old interface. You can take control of your interface and completely ignore areas.

Which I’ll do, but I don’t like the inconsistency

@petro

auto discovered items are placed in .storage. A hidden folder inside your config. Be warned, these are not yaml files and they are not meant to be altered.

which is why I would prefer to be able to add them by hand to a single yaml file after the first configuration

@petro

Change it through the UI. Either through customizations or go to the integration and click on entities and adjust it there.

well it doesn’t change, homeassistant just reverts to the id everytime (z2m works fine with the friendly name)

@petro

No.

And that is a very big regression, hiding configuration is not a great thing especially if autocofiguration is half backed and inconsistent like it is now, config file are just better