Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Documentation does not mention minimum version HA.
See original GitHub issueProblem/Motivation
After upgrading to add-on v1.0.0, I could not logon to the WEB UI, using my HA Authentication as this new version mandates. At the time I was running hardware/versions:
-----------------------------------------------------------
amd64 / Ubuntu 18.04.1 LTS / HA 0.79.3 / SU 138 / stable
-----------------------------------------------------------
After upgrade HA to version ‘latest’, I am able to logon again using my HA Authentication credentials, without the need to ‘leave_front_door_open’. Banner now shows:
-----------------------------------------------------------
amd64 / Ubuntu 18.04.1 LTS / HA 0.81.2 / SU 138 / stable
-----------------------------------------------------------
Expected behavior
Be able to logon using my HA Authentication.
Actual behavior
'Access Denied' using my (correct and otherwise working) HA Authentication credentials.
Downgrade to HA v0.79.3.
(How can someone else make/see it happen)
Proposed changes
Perhaps add an update to the documentation, for other users, mentioning the minimal version needed of Home Assistant for this add-on version to be able to logon using the HA Authentication. Initially I wanted to wait with the newer HA 0.8x.x versions, as it breaks my current LoveLace config. If I had know beforehand that this upgrade was needed, I probably would have waited upgrading the add-on.
Thanks!
Issue Analytics
- State:
- Created 5 years ago
- Comments:14 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hi @nigel914,
About the testing. This latest update has been pending a long time, because of the testing. All community add-ons are tested against the following:
In fact, it is the amount of testing that caused a delay in the release for weeks (sorry about that), since the following issues were discovered and fixed upstream:
node-red-contrib-home-assistant-websocketbased on issues found).Issues & PR’s still open, but should not affect the current release (at least, not as much as the previous release):
I know what sarcasm looks like, thanks for mocking me. My response was an “I don’t care response”. You should use whatever you like and feel comfortable with. You don’t have to use any of my things (so please do not use any of the Community add-ons, because, well yeah, that’s almost all my “untested” shit).
At least, thanks for trying the add-on. If you ever feel like testing it again, feel free to join or Discord, so we can help you in case you run into problems. And, if we discover a new issue, I will create a proper fix (or get the right people to help with that) and improve the add-on for the whole community.
Thank you again for being so kind and understanding @nigel914 😉
Signs of a great dev.