Closed GaryOkie closed 5 years ago
Mode is not a valid option anymore and can be removed, you have disabled card tracking by specifying components so it will not handle cards at all.
Thanks for the advice. The tracker card is displaying now. It never occurred to me that in order for the card to display in the UI, that you were required to TRACK cards. I intentionally did not want to track cards at first because of this statement in your documentation:
If you use this component to upgrade custom cards, this has a lot of changes, if you only use it for component and/or python_scripts this will not change anything.
Well, not tracking cards certainly did change something critical - if you don't, the initial tracker-card.js will not download. So unless you had an old tracker.card.js previously installed, then you will get the error as I described here. That makes sense now, but the documentation, which I followed very closely, did not help me recognize that.
So I have a new problem - my custom components (from pnbruckner) are not being tracked in the card. I have them listed in the configuration.yaml under the custom_updater: Do they also need to be added to the trackers config in the tracker-card as well? That did not use to be required.
That is not a requirement. What are the full path to the file it does not track?
This is the URL entry in configuration.yaml. .. There are actually 2 custom components that I am using from this repo - "composite" and "life360" that I want to track.
custom_updater:
component_urls: https://raw.githubusercontent.com/pnbruckner/homeassistant-config/master/custom_components.json
That is fine, but where are the files located?
/root/config/custom_components/composite/device_tracker.py /root/config/custom_components/life360/device_tracker.py
your logs say that it track those files but did not find it (yesterday) can you paste new logs?
will do - but the log is huge, even right after startup. (The previous log above, I cherry picked relevant info). for some reason, I am getting debug output for ALL of the components even though I only have this specified.
logger:
logs:
default: error
custom_components.custom_updater: debug
pyupdate: debug
Your default is not correct placed :)
Ah! Much better. "check config" didn't catch that, but you did! Thanks.
I've edited the original debug log above and replaced it with the latest complete log. In addition, I get these 2 warnings which show that HA is recognizing these custom components OK...
You are using a custom component for composite.device_tracker which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant. 9:03 AM loader.py (WARNING) You are using a custom component for life360.device_tracker which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant. 9:03 AM loader.py (WARNING)
Oh... I see the issue, the structure of the json file is not in the expected format..
Great. Do you want to ask Phil @pnbruckner to fix it with your specific advice? I can open an issue with him if you would prefer.
I can open a PR to correct it when I get home (if no one beats me to it) :)
@ludeeus
Oh... I see the issue, the structure of the json file is not in the expected format..
What is the expected format? I haven't changed anything recently, other than to deal with the whole "great migration" mess, and to use the new resources option for the custom sun component, but I thought you agreed I did that correctly.
What exactly do I need to change now?
Thanks very much! I was comparing his custom_components.json to your documentation and nothing jumped out to me as an improper format. Did the docs not get updated yet with the proper format?
Also, would you mind updating the custom_updater wiki to remove that mode statement that is no longer required? Maybe also something about if you remove the tracker_card.js from www that you must enable custom card tracking in order for the new tracker card to download.
@GaryOkie someone beat me to it
but I thought you agreed I did that correctly.
@pnbruckner I'm sorry, I must have been unclear at some point...
Did the docs not get updated yet with the proper format?
There was nothing to update really, but I added an extra section about a week ago to try and make it clear (which I failed...)
Also, would you mind updating the custom_component doc to remove that mode statement that is no longer required?
Where is that mode section?
Maybe also something about if you remove the tracker_card.js from www that you must enable custom card tracking in order for the new tracker card to download.
Added to tracker-card "docs"
@ludeeus
I still have no idea what I'm supposed to do.
Where is that mode section?
I went looking for it and can no longer find it. I think it was spelled out in the custom_updater installation wiki
I remember seeing:
custom_updater:
mode: storage
There was also verbiage about mode being a new cool thing for Lovelace, but I don't find any of that now.
It was there (when it was a thing) I removed it when it was no longer supported ;)
@GaryOkie this should now show up as expected.
Hi @ludeeus - Yes! the tracker custom components are indeed showing up now after an HA restart. Thanks! Was this a change you made?
I see that the custom_updater is showing a new version, but I will need to manually update it as this updater tool won't update itself until a later fix, right?
@ludeeus - regarding that mode option that is no longer supported, I just found where it is still documented in the release 4.0.0 instructions....
Storage mode for lovelace is now supported. To enable this download this version then add mode: storage to your configuration.
custom_updater: mode: storage
Yes! the tracker custom components are indeed showing up now after an HA restart. Thanks! Was this a change you made?
nope, that is a result of https://github.com/pnbruckner/homeassistant-config/pull/108
I see that the custom_updater is showing a new version, but I will need to manually update it as this updater tool won't update itself until a later fix, right?
See this https://github.com/custom-components/custom_updater/issues/115 :)
regarding that mode option that is no longer supported, I just found where it is still
I see, it still belongs there, since it was valid for that version.
HASSIO Version 88.2
Tracker-card version 1.2.6
Describe the bug
Tracker-card.js apparently fails to download from github and can't be found, causing subject error. Custom_updater component is installed OK (except for mode error), it's just the card won't display. I saw another user had reported a similar issue and had to resort to copying the tracker-card.js to www (as it used to be done).
Custom element doesn't exist: tracker-card. { "type": "custom:tracker-card", }
custom_updater
configurationNOTE: I temporarily commented out mode: storage since it causes another error:
Resources in lovelace configuration
Tracker-card configuration
type: 'custom:tracker-card'
Debug log