Open lloydbayley opened 3 weeks ago
same here on
and i cont find anything about this in the logs
I'm SO glad it's not just me. It's something very tricky!
same here ...
I fixed it by removing the integration, and then adding it back.
However, this appears after a restart now:
Logger: homeassistant.config_entries
Source: config_entries.py:933
First occurred: 11:05:48 (1 occurrences)
Last logged: 11:05:48
Error migrating entry for fontawesome
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 933, in async_migrate
result = await component.async_migrate_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/fontawesome/__init__.py", line 104, in async_migrate_entry
entry.version = 2
^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 443, in __setattr__
raise AttributeError(
AttributeError: version cannot be changed directly, use async_update_entry instead
Your fix didn't work for me. It's a weird one, isn't it?! Have you any ideas where to look for clues @thomasloven ?
Has anyone made any further progress on this? I've tried every bloody trick in the book and it still won't play ball. I'm thinking it might be a conflicting HACS module OR an integration but it's proving difficult to find.
Sadly still No success here
I'm trying to wrack my brains to work out which hacs components/addons/integrations I've installed in the last few months. I mean, I've sworn at it but surely it can take that.....
Did a new install on a fresh virtual machine to test and it works. Therefore, I'm thinking it must be a conflict between things. I think we'll have to wait to see if @thomasloven can help.
I think I fixed the issue and am waiting for a merge by the maintainer.
Another option is to downgrade to 2.2.1 for now.
@lloydbayley would it possible for you, to install step by step your other inegrations and addons on your virtual machine, to find out which is responsible for the conflict? It would be very helpfull for us ....
I think I fixed the issue and am waiting for a merge by the maintainer.
Another option is to downgrade to 2.2.1 for now.
@peteh I tried your c hange but it didn't fixed this problem. I am with @lloydbayley it must me a conflict another integration.
@lloydbayley would it possible for you, to install step by step your other inegrations and addons on your virtual machine, to find out which is responsible for the conflict? It would be very helpfull for us ....
I KNEW that was coming. :) I was going to do that anyway. I've been installing a new network system here but it's next on the list. I'll start with the HACS components first, as that will be easiest.
I, too, tried the fix and it hasn't worked for me either.
Curiously, on the odd occasion, when I go into the icons and start typing either fab, far, fapro, it can lock up the browser where Firefox actually says the page is being slowed down and do I want to end the action. This has me thinking it might be one of the "messing with the layout" addon thingies...But I've been lead up the garden path by coincidences before so I'm not being fooled!
Will report back after doing the HACS ones.
My apologies, I was just referring to this issue comment, which would be fixed by my PR:
I fixed it by removing the integration, and then adding it back.
However, this appears after a restart now:
Logger: homeassistant.config_entries Source: config_entries.py:933 First occurred: 11:05:48 (1 occurrences) Last logged: 11:05:48 Error migrating entry for fontawesome Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/config_entries.py", line 933, in async_migrate result = await component.async_migrate_entry(hass, self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/config/custom_components/fontawesome/__init__.py", line 104, in async_migrate_entry entry.version = 2 ^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/config_entries.py", line 443, in __setattr__ raise AttributeError( AttributeError: version cannot be changed directly, use async_update_entry instead
I'll remove this issue from the PR
Strange Things Happens, since an hour i finally See and can use my Icons again - idk why, i didnt Change a settings or an Update, i Just restarted the complete virtual Maschine Not only HA
Edit: nevermind, after reopen HA Android App and Open a new Browser Window, the Icons are gone again
For me the icons do not show when connected remotely through HA Cloud but they show when locally connected.
Still no icons here. Still doing the VM testing that @Obicom mentioned. Will have more (hopefully) soon! Whether it be little or lots, who knows?! :)
Hey @lloydbayley, try downgrading to 2.1.3. I was having the same symptoms as you and tried downgrading to 2.2.1 as @peteh suggested to no avail. Tried the usual incantations rebooting/restarting/reloading HA and shift-F5 in Firefox, but no custom icons in Firefox or the HA Android app. Someone suggested 2.1.3 in another issue so I downgraded to 2.1.3, specifically:
At that point I noticed the icons appeared in the HA app, but not Firefox. Did a shift-F5, and they appeared!
Like you, I was trying to use wolf's Bambu Lab dashboards. If the issue with the current versions is indeed caused by some conflict with another HACS component, I wouldn't be surprised if it was one of the ones wolf calls for in the guide:
Hope this works (and stays working) for you too! I'll update if they randomly disappear. This is the first time I've seen them, since I just started working on the X1C dashboard today.
Well cover me in egg and flour and bake me for 14 minutes! That bloody worked!
Now we have something we can work with....however, this opens up 1000 more possibilities. I've tried playing around with the components that Wolf calls for. I've reloaded them, deleted them, painted them purple and still nothing.
I'm going to keep at this in the background because there MUST be something that is causing this but finding this is another thing. I asked Inspector Clouseau but all he wanted to know is if my dog bites.
Thanks very much for the suggestion, as this means at least it's working for the meantime but tracing this will require some doing. Perhaps between the few of us, we will be able to work it out!?!
Glad that worked for you too! Now, back to keeping the printer 100% utilized! :)
G'day Thomas et al,
I'm loathe to start issues until I've exhausted all possibilities and I think I've been looking at this too-long. At some stage, the fa* icons have all decided to be blank. The MDI and PHU ones work fine.
What I've tried:
Uninstalled Fontawesome from the Integrations page Uninstalled Fontawesome from the HACS page Deleted the fontawesome folder from custom_components. Restarted HA.
Then I reinstalled the HACS fontawesome Reinstalled Integrations fontawesome Restarted HA.
I've cleared the cache, tried from different browsers, different machines...it's driving me NUTS! I've even uninstalled and reinstalled a load of other HACS components to see if they were causing issues.
Is there anything I can look at to see what is going wrong? The logs yield no results, and annoyingly, nor does the diagnostics for fontawesome. It's like it's teasing me..
Any Ideas?
Cheers!
Lloyd.