Krzysztof Korab

I'm not able to debug it right now, but I bet it's KDE Framework 6.1 changes.

Is anyone experiencing this problem on KDE Plasma 6.0.4 and KDE Frameworks 6.1.0?

No problems with other widgets or the Plasma itself? I see that there have been [some problems with the QML cache on Arch](https://www.reddit.com/r/kde/comments/18uq79e/plasma_6_beta_2_error_loading_qml_file/), causing similar errors of mismatched types.

I just tested the installation of a widget from Discover on a freshly installed, latest Tumbleweed (VM) - it works. Can you check if deleting `~/.cache/plasmashell/qmlcache/` has any effect?

According to [this issue](https://bugs.kde.org/show_bug.cgi?id=487464), it should be fixed in Frameworks 6.4. Until you get it, you can edit the plasmoid code locally - remove the [Action and helpfulAction property]( https://github.com/korapp/plasma-homeassistant/blob/0b266fadaea47d728867674acff6ae8fc1cc093b/package/contents/ui/FullRepresentation.qml#L66)...

Thank you for your feedback. 1. I am aware of this - it has been on my mind for some time. 2. (3). I'm considering a more customizable layout but...

Please check if the problem still occurs in v0.3.0.

Could you rebase your change onto dev branch and apply a "fix: " prefix to the commit message?

Does visiting `[your_ha_ur]/api/` also return a 404? (Trailing slash is important)

401 in this case is expected because no token was passed. The step was to make sure the API is reachable. Is it possible that you don't have a `default_config:`...