Issue: mapping values are not allowed here in "/config/hki-base/base.yaml", line 998, column 18

[dnestico]

Hey, it's me again... :/

EVERYTHING was going perfect, I finally made the view how I wanted it, and then suddenly when I went to restart my home assistant again after adding "visibility" so that only certain users can see certain pages, it just all came crashing down and I have no idea why...

I tried replacing my base.yaml file with yours but nope even that didn't work, instead the UI just wouldn't load.

ERROR CODE: mapping values are not allowed here in "/config/hki-base/base.yaml", line 998, column 18

Here is my base.yaml file if you'd like to take a look at it that would be nice: ezyzip.zip

view_config file: ezyzip.zip

And here is the LOG:

LOG TEXT:

2022-02-19 07:53:32 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration browser_mod which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2022-02-19 07:53:32 WARNING (SyncWorker_3) [homeassistant.loader] We found a custom integration webrtc which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2022-02-19 07:53:32 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration google_home which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2022-02-19 07:53:32 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration simple_wyze_vac which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2022-02-19 07:53:32 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2022-02-19 07:53:32 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration lovelace_gen which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2022-02-19 07:53:32 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration wyzeapi which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2022-02-19 07:53:39 WARNING (MainThread) [homeassistant.helpers.entity] Entity media_player.browser_1410c718_00d26d9c (<class 'custom_components.browser_mod.media_player.BrowserModPlayer'>) implements device_state_attributes. Please report it to the custom component author. 2022-02-19 07:53:39 WARNING (MainThread) [homeassistant.helpers.entity] Entity light.browser_1410c718_00d26d9c (<class 'custom_components.browser_mod.light.BrowserModLight'>) implements device_state_attributes. Please report it to the custom component author. 2022-02-19 07:53:44 ERROR (SyncWorker_5) [custom_components.lovelace_gen] mapping values are not allowed here in "/config/hki-base/base.yaml", line 998, column 18 2022-02-19 07:53:45 ERROR (SyncWorker_6) [custom_components.lovelace_gen] mapping values are not allowed here in "/config/hki-base/base.yaml", line 998, column 18 2022-02-19 07:54:18 ERROR (SyncWorker_5) [custom_components.lovelace_gen] mapping values are not allowed here in "/config/hki-base/base.yaml", line 998, column 18 2022-02-19 07:54:18 WARNING (MainThread) [homeassistant.components.version] Configuration of the Version platform in YAML is deprecated and will be removed in Home Assistant 2022.4; Your existing configuration has been imported into the UI automatically and can be safely removed from your configuration.yaml file 2022-02-19 07:54:18 WARNING (MainThread) [homeassistant.components.version] Configuration of the Version platform in YAML is deprecated and will be removed in Home Assistant 2022.4; Your existing configuration has been imported into the UI automatically and can be safely removed from your configuration.yaml file 2022-02-19 07:54:20 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.browser_1410c718_00d26d9c (<class 'custom_components.browser_mod.sensor.BrowserModSensor'>) implements device_state_attributes. Please report it to the custom component author. 2022-02-19 07:54:23 WARNING (MainThread) [homeassistant.helpers.entity] Entity siren.front_doorbell_siren (<class 'custom_components.wyzeapi.siren.WyzeCameraSiren'>) implements device_state_attributes. Please report it to the custom component author. 2022-02-19 07:54:23 WARNING (MainThread) [homeassistant.helpers.entity] Entity siren.driveway_siren (<class 'custom_components.wyzeapi.siren.WyzeCameraSiren'>) implements device_state_attributes. Please report it to the custom component author. 2022-02-19 07:54:23 WARNING (MainThread) [homeassistant.helpers.entity] Entity siren.outdoor_cam_siren (<class 'custom_components.wyzeapi.siren.WyzeCameraSiren'>) implements device_state_attributes. Please report it to the custom component author. 2022-02-19 07:54:23 WARNING (MainThread) [homeassistant.helpers.entity] Entity siren.garage_cam_siren (<class 'custom_components.wyzeapi.siren.WyzeCameraSiren'>) implements device_state_attributes. Please report it to the custom component author. 2022-02-19 07:54:23 WARNING (MainThread) [homeassistant.helpers.entity] Entity siren.porch_siren (<class 'custom_components.wyzeapi.siren.WyzeCameraSiren'>) implements device_state_attributes. Please report it to the custom component author. 2022-02-19 07:54:36 ERROR (SyncWorker_2) [custom_components.lovelace_gen] mapping values are not allowed here in "/config/hki-base/base.yaml", line 998, column 18 2022-02-19 07:55:18 ERROR (SyncWorker_3) [custom_components.lovelace_gen] mapping values are not allowed here in "/config/hki-base/base.yaml", line 998, column 18 2022-02-19 07:57:19 ERROR (SyncWorker_5) [custom_components.lovelace_gen] mapping values are not allowed here in "/config/hki-base/base.yaml", line 998, column 18

[jimz011]

If you don't share the code I will never find your problem. Please share it.

Get Outlook for Androidhttps://aka.ms/AAb9ysg

---

From: David Nestico @.> Sent: Saturday, February 19, 2022 2:05:58 PM To: jimz011/homekit-infused @.> Cc: Subscribed @.***> Subject: [jimz011/homekit-infused] Issue: mapping values are not allowed here in "/config/hki-base/base.yaml", line 998, column 18 (Issue #130)

Hey, it's me again... :/

EVERYTHING was going perfect, I finally made the view how I wanted it, and then suddenly when I went to restart my home assistant again after adding "visibility" so that only certain users can see certain pages, it just all came crashing down and I have no idea why...

I tried replacing my base.yaml file with yours but nope even that didn't work, instead the UI just wouldn't load.

ERROR CODE: mapping values are not allowed here in "/config/hki-base/base.yaml", line 998, column 18

Here is my base.yaml file if you'd like to take a look at it that would be nice: ezyzip.ziphttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjimz011%2Fhomekit-infused%2Ffiles%2F8102200%2Fezyzip.zip&data=04%7C01%7C%7Cde6c59dec0fe4d0ef8d008d9f3a892fb%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637808727606397316%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=n%2BLR%2BiBVG20%2BNOxidtXGAz7wqvoxr1SXGcWkKuSho10%3D&reserved=0

And here is the LOG:

[Screen Shot 2022-02-19 at 8 03 30 AM]https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F3034555%2F154801946-c707b3de-632a-4ccd-abd5-68ca0d92c0ba.png&data=04%7C01%7C%7Cde6c59dec0fe4d0ef8d008d9f3a892fb%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637808727606397316%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=ZRFEmZoCQJ2gFi3TSG0pwF9hFyhPFURd57xZgT92iOs%3D&reserved=0

LOG TEXT:

2022-02-19 07:53:32 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration browser_mod which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2022-02-19 07:53:32 WARNING (SyncWorker_3) [homeassistant.loader] We found a custom integration webrtc which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2022-02-19 07:53:32 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration google_home which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2022-02-19 07:53:32 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration simple_wyze_vac which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2022-02-19 07:53:32 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2022-02-19 07:53:32 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration lovelace_gen which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2022-02-19 07:53:32 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration wyzeapi which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2022-02-19 07:53:39 WARNING (MainThread) [homeassistant.helpers.entity] Entity media_player.browser_1410c718_00d26d9c (<class 'custom_components.browser_mod.media_player.BrowserModPlayer'>) implements device_state_attributes. Please report it to the custom component author. 2022-02-19 07:53:39 WARNING (MainThread) [homeassistant.helpers.entity] Entity light.browser_1410c718_00d26d9c (<class 'custom_components.browser_mod.light.BrowserModLight'>) implements device_state_attributes. Please report it to the custom component author. 2022-02-19 07:53:44 ERROR (SyncWorker_5) [custom_components.lovelace_gen] mapping values are not allowed here in "/config/hki-base/base.yaml", line 998, column 18 2022-02-19 07:53:45 ERROR (SyncWorker_6) [custom_components.lovelace_gen] mapping values are not allowed here in "/config/hki-base/base.yaml", line 998, column 18 2022-02-19 07:54:18 ERROR (SyncWorker_5) [custom_components.lovelace_gen] mapping values are not allowed here in "/config/hki-base/base.yaml", line 998, column 18 2022-02-19 07:54:18 WARNING (MainThread) [homeassistant.components.version] Configuration of the Version platform in YAML is deprecated and will be removed in Home Assistant 2022.4; Your existing configuration has been imported into the UI automatically and can be safely removed from your configuration.yaml file 2022-02-19 07:54:18 WARNING (MainThread) [homeassistant.components.version] Configuration of the Version platform in YAML is deprecated and will be removed in Home Assistant 2022.4; Your existing configuration has been imported into the UI automatically and can be safely removed from your configuration.yaml file 2022-02-19 07:54:20 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.browser_1410c718_00d26d9c (<class 'custom_components.browser_mod.sensor.BrowserModSensor'>) implements device_state_attributes. Please report it to the custom component author. 2022-02-19 07:54:23 WARNING (MainThread) [homeassistant.helpers.entity] Entity siren.front_doorbell_siren (<class 'custom_components.wyzeapi.siren.WyzeCameraSiren'>) implements device_state_attributes. Please report it to the custom component author. 2022-02-19 07:54:23 WARNING (MainThread) [homeassistant.helpers.entity] Entity siren.driveway_siren (<class 'custom_components.wyzeapi.siren.WyzeCameraSiren'>) implements device_state_attributes. Please report it to the custom component author. 2022-02-19 07:54:23 WARNING (MainThread) [homeassistant.helpers.entity] Entity siren.outdoor_cam_siren (<class 'custom_components.wyzeapi.siren.WyzeCameraSiren'>) implements device_state_attributes. Please report it to the custom component author. 2022-02-19 07:54:23 WARNING (MainThread) [homeassistant.helpers.entity] Entity siren.garage_cam_siren (<class 'custom_components.wyzeapi.siren.WyzeCameraSiren'>) implements device_state_attributes. Please report it to the custom component author. 2022-02-19 07:54:23 WARNING (MainThread) [homeassistant.helpers.entity] Entity siren.porch_siren (<class 'custom_components.wyzeapi.siren.WyzeCameraSiren'>) implements device_state_attributes. Please report it to the custom component author. 2022-02-19 07:54:36 ERROR (SyncWorker_2) [custom_components.lovelace_gen] mapping values are not allowed here in "/config/hki-base/base.yaml", line 998, column 18 2022-02-19 07:55:18 ERROR (SyncWorker_3) [custom_components.lovelace_gen] mapping values are not allowed here in "/config/hki-base/base.yaml", line 998, column 18 2022-02-19 07:57:19 ERROR (SyncWorker_5) [custom_components.lovelace_gen] mapping values are not allowed here in "/config/hki-base/base.yaml", line 998, column 18

— Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjimz011%2Fhomekit-infused%2Fissues%2F130&data=04%7C01%7C%7Cde6c59dec0fe4d0ef8d008d9f3a892fb%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637808727606397316%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=INieHTmDe6166oJYUDYmEHYQAg2vPZhthBUKuzYCArw%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FALG6BXUJ5AIXUWEAWTTO4YTU36ITNANCNFSM5O2PWWXQ&data=04%7C01%7C%7Cde6c59dec0fe4d0ef8d008d9f3a892fb%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637808727606397316%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=tEsmvjYF6FOMrLkrwBD1z%2FzDk1JTVYoDi918Y%2BAe%2Fjs%3D&reserved=0. You are receiving this because you are subscribed to this thread.Message ID: @.***>

[dnestico]

I shared the base.yaml, view_config and error log, what code do you need?

[jimz011]

I see, I will take a look at the view config later when I get back. However if you made changes in the base.yaml file I will not give support on that. It would simply be too much if people also ask how to modify base files. Remember that I am the only dev working on this project.

In HKI 5 the base.yaml file doesnt need to be edited since it will address all of these things (including making a view visible for specific users).

Since the entire base file is a loop, you can't just add code to it. You can, but it will then render that same code on all your views unless you make it so that it takes the config from a dictionary.

I will take a look at the other file later.

[dnestico]

Well the thing is, I never touched the base.yaml file, which is why I don't understand why it broke, I never edit that file.

But yes please take a look when you have time thanks.

[jimz011]

Ah, I see, then you have configured the view config incorrectly. I'll take a look at it later

[dnestico]

Thanks! One last question, are you the one who developed all these add-ons or no, because I have a question for whoever did about the camera addon that I couldn't figure out last night but that's low priority I rather get my view back first haha. Thanks

[jimz011]

As stated in the documentation, I did not create any of the used addons.

The camera addon is just the default HA picture glance card used.

[dnestico]

Alright

[jimz011]

ezyzip (1).zip

So I will not correct it, but I did point out all the locations that have errors. Also if any piece of code is not documented, you won't be able to use it (with the exception of the custom addon).

Also in the future when editing views, if you are not sure. Please only do one view at a time and trial and error. It is super hard for you as a user to debug something if you made a ton of changes. Better change one thing, restart, see if it works and continue. If it doesn't work? Well then you will know immediately that the last line you have configured is wrong.

I will also suggest watching some video's on how YAML indentation works since most of your errors come from indenting the config incorrectly. Spaces are important in YAML don't use too little of them and don't use too much. A rule of thumb is always 2 spaces:

# example
- type: vertical-stack
  cards:
    - type: horizontal-stack
      cards:
        - type: markdown
          content: hello world

As you can see everything that is written here have 2 spaces between the different cards.

If you follow my documentation to the letter and copy the examples, you should have the correct indentations if you copy the example text and just edit those.

[dnestico]

Thank you I am taking a look now, not sure how the "visible" tag isn't functional when I got it from here: https://www.home-assistant.io/lovelace/views/#view-icon - I will remove it and try and figure out the rest now, ill come back here if I need more help, thanks.

[dnestico]

Well thanks once again, I followed your notes and my views are fixed!

I just wish this error would disappear everytime I restart HA, it's been there since I first started and it goes away after I click another view on left panel then come back to my views, but that's about it, thanks.

[jimz011]

The reason the visible tag isn't working is because HKI doesn't support all the core features from HA. HKI runs a loop with configuration. If it isn't documented in the HKI docs then you probably can't use it. It doesn't mean it isn't possible at all, it only means you must edit the base file to do so (which will make updating HKI very difficult for you).

Note that HKI 5 has this option available so you can use it soon.

[jimz011]

The error you have, is something that only very few people reported to me, and I am looking for a solution (though HKI 5 might not have the problem at all, I do not know).

I never have this, so maybe clearing cache might help? or try reinstalling swipe-card.

[dnestico]

I've reinstalled swipe-card and cleared the cache and unfortunately didn't work, I actually experience this when I restart it sometimes across all devices including the app and my MacBook and wall tablet I'm making now, hopefully, this can be resolved cuz would not be nice to see on the wall mount haha..

[jimz011]

Also try using quotes on your states:

- type: conditional
  conditions:
    - entity: lock.frontdoor
      state: "locked"

It might help with these errors

[dnestico]

Ok so I've added the quotes but the file is throwing indentation errors, and it seems to not have liked the added quotations... now it won't come back even after I put it back to how it was before.. 🙃

The errors: (there's 2 that happened at the same time so guess I'll paste both)

ERROR 1:

Logger: frontend.js.latest.202202031 Source: components/system_log/init.py:190 First occurred: 2:53:46 AM (2 occurrences) Last logged: 2:53:46 AM

http://homeassistant.local:8123/homekit-infused:0:0 Uncaught

ERROR 2: (i think this is the important one you need)

This error originated from a custom integration.

Logger: custom_components.lovelace_gen Source: custom_components/lovelace_gen/init.py:39 Integration: Lovelace Gen (documentation) First occurred: 2:41:48 AM (6 occurrences) Last logged: 2:53:46 AM

while parsing a block collection in "/config/hki-user/notifications.yaml", line 8, column 5 expected , but found '' in "/config/hki-user/notifications.yaml", line 9, column 6

Error on my view:

My files just in case:

ezyzip.zip

view_config, but don't think you'll need it cuz nothing is broken here:

ezyzip.zip

[jimz011]

well, the error literally says where you made a mistake:

This time I will not point out where the error is, but just look at the screenshot I have sent you, you should be able to find the error!

[dnestico]

Can I have a hint pls lol, Are you trying to point out that the entity name is wrong?

My front door lock entity name literally is "lock.front_door" so not sure what you are highlighting here.

-

-

[dnestico]

Oh my God I feel so dumb Idk how you put up with my issues LOL, looks like it really was an indentation problem.... my view is back now!

Just wish that dumb t.setConfig is not a function error would disappear with it!