Rewritten (v3.0.0-alpha-21) - Improved reauthentication #693
Replies: 9 comments 13 replies
-
|
What do you mean, It is no longer possible to turn on/off the camera entity - use appropriate switch instead I didn't quite understand? |
Beta Was this translation helpful? Give feedback.
-
|
Working fine for me on my old S50 ! Was login failed error on v2, never worked (new HA user). Now in v3 working like a charm ! |
Beta Was this translation helpful? Give feedback.
-
|
Hello, just letting you know I gave reconfiguring (after removing the old yaml configuration) this a try within home assistant today and both authentication methods failed. With the captcha, even when I knew I was typing in the correct characters within the home assistant dialog, it kept saying it failed. With the qr code method, when clicking the "link" or using the photo method by using the cell phone to take me to the link, it just took me to a page with a bunch of text. Is there something I can provide to help with tracking down these issues or is this expected behavior at this point. |
Beta Was this translation helpful? Give feedback.
-
|
I have successfully set up the integration via the UI. Now I want to customize the map colors (to match my dashboard theme). However, it seems I can only do this by adding the full configuration to configuration.yaml, which requires me to re-enter my username and password. Question: Is there a way to define only the colors section in YAML and inherit the credentials/connection from the existing UI integration? Or is the full YAML config (including credentials) mandatory for the map extractor to work, even if the device is already in HA via the UI? |
Beta Was this translation helpful? Give feedback.
-
|
Doesn't work any more. Clear install didn't help. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for your response!! Very appreciative.Sent from my iPhoneOn Jan 7, 2026, at 8:57 PM, Piotr Machowski ***@***.***> wrote:
I seem to remember the need to disable the map update when docked. Is this still a necessity with the new version? No, it is now built-in into the integration
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
I switched to this version a few weeks ago since the old one wasn't working any more, setup worked flawlessly, I entered the code received by email and it has been working without an issue ever since. Thank you very much for all the work! |
Beta Was this translation helpful? Give feedback.
-
|
I updated to this version since the old one wasn't working any more, everthing working without an issue ever since. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks! Everthing is perfect now.J.Odesláno z iPhonu28. 1. 2026 v 11:38, Piotr Machowski ***@***.***>:
Yes, in current version of the integration the old method of disabling the camera entity is no longer supported - this mechanism is now built info the integration itself
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.



Uh oh!
There was an error while loading. Please reload this page.
-
This is an early version of Map Extractor v3 release. It has been completely rewritten in order to provide better functionality and user experience. To use this version you have to remove old config from
configuration.yamlfile and use UI to add the integration again.Caution
Please keep in mind this is not a final release, so a lot of things might change or not work at all at this moment.
Does everything work correctly, or are there some missing functionalities? Please provide feedback in the comments below.
Changes
imageentitiesBreaking changes
cameraentity have been removed and added as separate entitiesThis discussion was created from the release Rewritten (v3.0.0-alpha-21) - Improved reauthentication.
Beta Was this translation helpful? Give feedback.
All reactions