MMM-weconnectid with 2 accounts

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:

same module, twice in the config
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: