Who has authorized?

[banybeer]

We are having 2 RFID cards for authorization. For each one a different backend reimbursement process is triggered. Does anyone know if there is already a sensor showing me which RFID card has authorized? Didn’t find any yet.

[leeyuentuen]

did you see them on my eve app with card goes to which backend?

[banybeer]

You see in the transaction the card tags. The tags are the important information. Best case would be even to have sensors which sum up the consumption in kWh per recognized tag.

[TeddyTBP]

I would be very interested in a sensor with the active RFID badge during charging. We could then link ID to a name and inform people if its time to get their car moved

[leeyuentuen]

testing in beta version: https://github.com/leeyuentuen/alfen_wallbox/releases/tag/2.7.33

[leeyuentuen]

i need someone with multiple tags to let me know of this works

[TeddyTBP]

Just installed .33 and i can see last tag is populated in the two fields. Wil do some more testing.

Not sure if its possible: but could we have one sensor where standard value is non and then on start we see new value en and stop we go back to none?

Kn this matter you would have a status of the card during transaction but if done and transaction is closed we would see none.

If then in HA we goto show more we would see who has charged and for how long.

[leeyuentuen]

new beta version: https://github.com/leeyuentuen/alfen_wallbox/releases/tag/2.7.35 I try to add the charging time and the total charge amount. but I think the transaction will not instantly update, maybe every 15 minutes or something like that. But maybe good try for the beginning

[leeyuentuen]

@TeddyTBP i think you see now the thing you needed?

@banybeer i think you can see the tag that is using the wallbox?

[TeddyTBP]

Hi, I can confirm that the vallues added in .36 are populating for me after the charge session has stopped during the session i didn't notice change.

[TeddyTBP]

For the Start en stop session it seems double the values do change if i scan another tag but if twice the same tag is used then there is no change in value.

In this case i think what would work beter is 1 sensor where that state is none by default. on start it gets the ID of the tag en on stop it reverts back to none. in this case you get a bar graph in the history with all the sessions marked inline. In the end it could like like the altered screenshot below.

[leeyuentuen]

Hi, I can confirm that the vallues added in .36 are populating for me after the charge session has stopped during the session i didn't notice change.

yes i notice this, there will be update soon (maybe within 1h). i've create an issue of it: https://github.com/leeyuentuen/alfen_wallbox/issues/117 but also commit the fix, but didn't make a new version yet. (doing other small fix)

[leeyuentuen]

For the Start en stop session it seems double the values do change if i scan another tag but if twice the same tag is used then there is no change in value.

In this case i think what would work beter is 1 sensor where that state is none by default. on start it gets the ID of the tag en on stop it reverts back to none. in this case you get a bar graph in the history with all the sessions marked inline. In the end it could like like the altered screenshot below.

i'll maybe remove the start and stop tag, only put the tag

[leeyuentuen]

@TeddyTBP latest beta has been updated, can you take a look if it is what we need?

[VmaxTurbo]

Would it be possible to start a charging session from HA, using my tag ID, without having to scan it at the RFID reader on the wallbox every time? Automating charging sessions from HA at low costs would be a nice to have...

[leeyuentuen]

Would it be possible to start a charging session from HA, using my tag ID, without having to scan it at the RFID reader on the wallbox every time? Automating charging sessions from HA at low costs would be a nice to have...

not checked yet. but i'm just tag them but set the amp to 0. if i want to charge, i set them max to 6 - 16A

[aritmeester]

For the Start en stop session it seems double the values do change if i scan another tag but if twice the same tag is used then there is no change in value.

In this case i think what would work beter is 1 sensor where that state is none by default. on start it gets the ID of the tag en on stop it reverts back to none. in this case you get a bar graph in the history with all the sessions marked inline. In the end it could like like the altered screenshot below.

If I were you, I wouldn't post my Tag ID online. This way your tag can easily be misused.

[leeyuentuen]

For the Start en stop session it seems double the values do change if i scan another tag but if twice the same tag is used then there is no change in value. In this case i think what would work beter is 1 sensor where that state is none by default. on start it gets the ID of the tag en on stop it reverts back to none. in this case you get a bar graph in the history with all the sessions marked inline. In the end it could like like the altered screenshot below.

If I were you, I wouldn't post my Tag ID online. This way your tag can easily be misused.

i've just changed that post. thanks for that

[TeddyTBP]

It was an empy tag for testing but indeed should be mindfull of what tags are posted. I see it was removed so thanks for the extra set of eyes :)

[banybeer]

thanks @leeyuentuen ! Just saw that it was added with the "Tag" and nicely works. Tried it with different RFID cards - perfect! will add it now in automations. If i come across an issues i will let you know.