Open mschmitt opened 10 months ago
thanks for reporting, we will check this and maybe release another beta firmware with fixes applied
Please try to verify or change the configuration values of AllowOfflineTxForUnknownId, LocalAuthorizeOffline, LocalAuthListEnabled
Should we do a short meeting going through the stack? We would enable the go-e ocpp debug mode on your box so we see the incoming and outgoing traffic and all state transitions in between. You can also always ask the go-e support if you include timestamps and serial numbers, maybe ask them for a direct google meets link together with me, Daniel :)
I'll be glad to help out. Feel free to get in touch with me directly (the "href" link on my github profile).
If you need some sort of paper trail with support, I can also take that path.
In the mean time, the OCPP values you asked about:
{
"key": "AllowOfflineTxForUnknownId",
"readonly": false,
"value": "0"
},
{
"key": "LocalAuthorizeOffline",
"readonly": false,
"value": "0"
},
{
"key": "LocalAuthListEnabled",
"readonly": false,
"value": "0"
},
I'm working on a personal OCPP implementation (not pushed to Github yet) and have observed the following behaviour between Firmware 055.5 and 055.7 Beta when presenting an RFID tag that's locally known to the charger:
Is the Beta moving towards a new way of handling of locally known RFIDs where they are handled autonomously without OCPP interaction, or is this behaviour completely unintended?