No response for 'state' over Modbus on FW 2.30

[martijndierckx]

Hi

Just updated my SmartEVSE to 2.30.
Where I was able to get the state from address 0x00A0 on FW 2.13, I'm not able to get in from 0x0000 on FW 2.30.
Other addresses seem to work fine.

Any ideas?

Kind regards
M

[kennyschuoler]

I have the same issue it seems ( @martijndierckx thank you for your previous remark :) ).
Tomorrow i'll compile the latest version and check if it is already fixed in the meantime ( The charging current is also not working as it should , but looking at the commits that should be fixed )

[mstegen]

Please note that the modbus registers changed between v2.30 and <=2.20

use this list for 2.20 or earlier:
https://github.com/SmartEVSE/SmartEVSE-2/tree/b8b6a1a2def22a2bfc3cc30be2f2ef639e2d4389#modbus
and the default one for v2.30:
https://github.com/SmartEVSE/SmartEVSE-2/#modbus

[martijndierckx]

I’m using the new list. Everything seems to work except the first state address.

…

________________________________ Van: Michael Stegen ***@***.***> Verzonden: Tuesday, January 11, 2022 8:56:40 PM Aan: SmartEVSE/SmartEVSE-2 ***@***.***> CC: Martijn Dierckx ***@***.***>; Mention ***@***.***> Onderwerp: Re: [SmartEVSE/SmartEVSE-2] No response for 'state' over Modbus on FW 2.30 (Issue #26) Please note that the modbus registers changed between v2.30 and <=2.20 use this list for 2.20 or earlier: https://github.com/SmartEVSE/SmartEVSE-2/tree/b8b6a1a2def22a2bfc3cc30be2f2ef639e2d4389#modbus and the default one for v2.30: https://github.com/SmartEVSE/SmartEVSE-2/tree/b8b6a1a2def22a2bfc3cc30be2f2ef639e2d4389#modbus — Reply to this email directly, view it on GitHub<#26 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AA6KD7XE6DX5QQ6VSDC4HETUVSDPRANCNFSM5LXEYLWA>. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[kennyschuoler]

@mstegen It is a possibility that i have a slightly different issue then @martijndierckx , if it is the case i'll create a new issue

I am also using the latest registers - see screenshot ( Everything else is working as expected - ignore the the callibration value, i still need to display that one correctly )

• The charging current is 160 A ( while it is not charging atm, this is already fixed based on the commits )
• The state that is returned are numeric values ( i suppose 0=A, 1=B, 2=C, ... )
• The state is always 0 except when i set the access bit to 1 ( allowed ) and i switch at 22h from solar to smart, then the state is set to 2 ( but it seems i don't get the status 1 ). When the battery is full, i set the access bit back to 0 ( denied ) . Then it seems the state is shortly set to 1
• At 7h in the morning, i switch from smart to solar and set the access bit again to 0 ( denied ) , then it also shortly shows the state=1 ( plugged in ) but then the state returns to 0
  --> In case this is not working as expected, it'll probably have to do something with the access bit and the state update

[rvdgaag]

@kennyschuoler How did you manage to read the values of the Smart EVSE ?

I have also fw 2.30 installed but can't get any values via modbus from the smartevse, both SDM630 eastron units reply fine.

Any suggestions ??