[FEATURE]: Two stromers under the same id

[aq18507]

Describe the bug.

Thanks for developing this fantastic integration. We have both of our stromers on the same ID. I am wondering first of all, whether it is possible to add them both using the integration. If not, this might be an additional useful feature to add to this already great app.
Thanks very much already.

What version of Home Assistant Core has the issue?

2024.1.6

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Supervised

How did you install the stromer integration

HACS

Logging

No response

Diagnostics information

No response

Additional information

No response

[CoMPaTech]

Seems to make sense, I would assume just 'multiple bike id's present but never looked for them. I'll get back to you on it.

[aq18507]

Fantastic, thanks so much. It must clearly broadcast both of them since I previously used a script running on AppDeamon with the same login credentials, and I was pulling the data from the other bike.

[CoMPaTech]

Trying a very preliminary in #82 just to test the waters (i.e. not breaking existing setups) as it's a bit more of a hassle than just iterating multiple times + not sure if the config_flow still works properly. It will probably take some time/iterations before it's in a usable form :)

[CoMPaTech]

I see I just use data[0] for the bike(s) retrieval, so that is/was probably the culprit and ensuring only the first bike's data is there.

[aq18507]

Amazing! I am not really using the integration at the moment so if you like I can test and give you some feedback (you might have to instruct me how to do this though as I have never done it before)

[CoMPaTech]

Sure, highly appreciated - I'll keep you posted. If you already have (it installed through) HACS it's only a matter of enabling beta downloads - but don't install any of the v0.4.xx yet, not sure how broken it is. (Yes, have done multi-device before but trying to cut some corners preventing a lot of additional work - that might bite)

ps I do have a separate instance for testing which makes it easier to make FUs which I'd rather not have on other peoples systems/data :)

[aq18507]

You are more than welcome. It is a good idea to start my own test instance to play around. I shall do that tomorrow and will report back in due course.

[CoMPaTech]

Adjusted the approach, basic idea I'm trying to cook up now is 'add integration Stromer' => ask for credentials (mail/password/client-id) => show available bikes and select one. A little more work for multi-stromer users, but I would guess do-able :) (You'll have to add it twice but this should ensure not too much changes for existing users).

The below would become a list (or just single bike in my case) displaying your bike id number and the nickname you gave it

Not sure if I can make it neater, but if I recall correctly lists in config_flow used to be tricky. I'll try from here to make it workable, but wanted to share progress.

[aq18507]

Sorry for the belated reply I was caught up with doing something else. I have now spun up a test instance and enrolled to the beta testing on your github repo. When I looked at your code (I am very much a Matlab coder and not at all proficient with python) I was thinking whether this would potentially be a solution to reduce the complexity. I guess that extra work might only apply to those weirdoes few (like myeslef and my partner) who share an account anyway.

Let me know when you want me to give it a try.

[CoMPaTech]

No worries, it's all life that gets in the way, I had some time to spare so tinkered something, it might be that v0.4.0a2 is do-able in the approach I outlined above. Just waiting for code checks to kick in and report back and re-install this on my dev machine (I was actually just tinkering there to get it done and shuffling it back into git now).

[aq18507]

Fantastic. I shall watch out for any version change and will give it a go.

[CoMPaTech]

v0.4.0a2 seems to function (at least on a single bike) when adding it as a new integration - didn't tinker with it on existing bike implementation, guessing it takes some additional work. #note2self, probably detect single bike or existing unique-id and work from there

If you HACS -> Integrations -> Stromer and right top click the dots to 'Re-download' (or something likewise) you can toggle 'beta' on, that should show you said version.

What it will do is ask for mail/password/clientv4-id and when clicking next should show you bike or bikes, ticking a bike should add that bike. Note that adding the bike takes some time before it asks you 'which room' to put it in - the API is not the fastest in the world as you probably already experienced with the dashboard.
You would have to redo that for the other bike - hopefully it tinkers the whole way through and fetch accordingly.