MMM-weconnectid with 2 accounts

[sdetweil]

@chrisfr1976 try this

cd to the module folder

git fetch origin pull/6/head:test_multi
git checkout test_multi

then in config.js you can use multiple instances of this module with different config settings…

to go back to the old code if there is a problem

git checkout main

I don’t have a vehicle so I cant test it. no code logic was changed.

I submitted this as a change request to the module author…
if he accepts it, you would (in the module folder)

git checkout main
git pull

[chrisfr1976]

@sdetweil unfortunately it works just a little.

I can see two modules the first time on my screen but I can’t see the SoC and the loaded pictures shows the same car. That is clear for me when I check the module.js file. But 2 different cars are loaded what can be seen on the run kilometers.

So your approach works in general to show the module twice. Thank you for that. That might be helpful for other modules, too.
But to get the MMM-weconnectid fully working there needs to be some more coding in the module.js to be done. Python grabs the information I think since I see no errors or strange things in the log.
Unfortunately I’m a mechanical engineer who just starts with some very simple coding. I can’t fix that.

But again thanks a lot for your support and time you’ve spent!

Chris.

[sdetweil]

@chrisfr1976 each module 1 at a time works ok?

what is soc? state of charge?

[sdetweil]

@chrisfr1976 yes I see the issue. give me a little time.

[sdetweil]

@chrisfr1976 bug, sorry, he accepted code, but its broken

do this

git checkout main
git fetch origin pull/7/head:test_multi-2
git checkout test_multi-2

then try again

[sdetweil]

@chrisfr1976 said in MMM-weconnectid with 2 accounts:

So your approach works in general to show the module twice.

not mine. it’s the official way to support multiple instances.

[sdetweil]

@chrisfr1976 he has accepted that last pull request, so

git checkout main
git pull

try again

[sdetweil]

@chrisfr1976 did you see my note about an update?

[chrisfr1976]

@sdetweil Hello, yes, sorry for that delay. Yesterday I was out with my company colleagues :clinking_beer_mugs:

I’ve just tested the configuration:

1. same module, twice in the config
2. my copied module with new name with the original module together

then both versions with “git checkout main” and for doublecheck your “git checkout test_multi-2”.

And unfortunately without success. For Option 1 it stops with “loading…”. For Option 2 I get 1 car shown without any information from VW and the other stops also with “loading…” on the screen.

In the logs I just get this:

0|mm  | [22.02.2024 19:12.02.704] [LOG]   Got data from weconnectid for VIN WVWZZZE1ZNP0339xx
0|mm  | [22.02.2024 19:12.07.203] [LOG]   Got data from weconnectid for VIN WV2ZZZEB5PH0306xx

No Errors.

So same issue as last time. :crying_face:

[sdetweil]

@chrisfr1976 ok.

if you are willing to share your config via private message so i can run the module here.

maybe there is a syntax error

open the developers window, ctrl-shift-i,
select the console tab, and put we in the filter field

[sdetweil]

@chrisfr1976 thanks for your trust

do this

git checkout main
git fetch origin pull/8/head:test_multi-3
git checkout test_multi-3

and try again 1 instance and then both

[chrisfr1976]

@sdetweil Okay, nearly okay. I see the module twice on the screen. The following issues are on my Mirror:

• SoC for both cars is 0% - main point of interest :-)
• The pictures are the same (it is stored in the same folder with the same name. That is the reason for sure.) - not really needed
• My Calendar Ext3 stays empty. All events are broadcasted without any error. That is something in behind. I had that before when both modules (the original and my copy if both had enabled=true set). No error in the logs or any entry that is new for me.

[chrisfr1976]

@sdetweil

Short update: CalendarExt3 is now okay. Maybe it needed just some more time.

And the SoC is just missing. The remaining km-range is there. I checked it in the cars. The value is correct.

[sdetweil]

@chrisfr1976 pictures. I think that comes back on the API. let me check.

soc… also let me check.

ext3. yes, as it is getting data from the default calendar, he is trying not to flash the display too many times. some calendars can take 10 seconds to process with all the old dead entries. he doesn’t know(altho he could! hmmm)

you can change the Ext3 wait time if you know how long it takes roughly.

[sdetweil]

@chrisfr1976 ok, fixed

the author has accepted these fixes too

do this

git checkout main
git pull

the SoC value was not copied… don’t know where that went as I didn’t change that block. anyhow fixed

images, I made a sub folder by module instance… these should be correct now

[chrisfr1976]

@sdetweil Wow, thank you so much! Perfect :folded_hands: :grinning_face_with_big_eyes:

[sdetweil]

@chrisfr1976 awesome… thanks for the feedback…