EVBox ELVI: Setting Maximum_Current causes Rejected / Rejected while setting MeterValuesSampledData to ... #221
Comments
|
Does the charger provide a more detailed debug as to why the |
|
Maybe if I find out how to let it send more information over the service ocpp.get_diagnistics. Otherwise it does not give much information I fear... Where is the StackLevel defined / to be changed? |
|
In |
|
Or can you sniff message from App to charger to compare? |
|
Not really. The App communicates via Bluetooth. It's more a way to limit the borders of whatever way of load management is being used can tinker in. The app normally is for electricians setting up the box offline and online. (Still the only way to set a custom OCPP.) In the long horror report (#2) where we slowly but steadily got the box to behave I put a few network sniffs when the box communicates with Everon. Are these useful maybe? #2 (comment) Regarding the -1: I need to charge for that to work at all I guess? If not then we are still on Rejected, if yes, will try later at home after work. |
|
On IOS you can sniff bluetooth. See https://mezdanak.de/2019/07/12/ios-bluetooth-packet-logging/. |
|
Indeed there is... at least a HCI Log is possible. Gonna try later too. No clue if that helps at all as this is no OCPP connection, but we will see. |
|
BT Log. The device you are looking for is: u-blox_27:d8:f4 Regarding the charging active and om.stack_level.value: stack_level -1: |
|
I'm afraid without some detail from the charger on why the message is being rejected you're limited to trial and error changes to: If diagnostics or the manufacturer won't help some other things you could try:
Good luck getting to the bottom of it. |
|
OK, time for some tinkering... I found not much about that except the OCPP 1.6 Protocol documentation (https://www.oasis-open.org/committees/download.php/58944/ocpp-1.6.pdf) and that my box allows up to 25 schedules per profile und that current limit (A) is the way to go in theory: https://help.evbox.com/s/article/setup-charging-profile?language=en_US So first I will try stackLevel:0 and a lower ChargingProfileId. The rest should be fine according to the OCPP standards. Required is there, optional is not. Keeping you updated EDIT: In case of a log file I wanna download I checked for this: 2021-12-08 10:32:03 INFO (MainThread) [ocpp] EVB-P20482857: receive message [3,"943e39ff-698a-42cd-b992-9859993a8fbd",{"configurationKey":[{"key":"SupportedFileTransferProtocols","readonly":true,"value":"FTP"}]}] 2021-12-08 10:39:02 INFO (MainThread) [ocpp] EVB-P20482857: receive message [3,"d858bd97-4d11-4645-938b-a8caddc64fbb",{"configurationKey":[{"key":"ChargeProfileMaxStackLevel","readonly":true,"value":"6"}]}] 2021-12-08 10:40:34 INFO (MainThread) [ocpp] EVB-P20482857: receive message [3,"4e3e37cd-224c-4828-a87e-797e70b3f74e",{"configurationKey":[{"key":"MaxChargingProfilesInstalled","readonly":true,"value":"66"}]}] 2021-12-08 10:42:22 INFO (MainThread) [ocpp] EVB-P20482857: receive message [3,"572f8620-cdb2-4087-9136-195ceeb6f705",{"configurationKey":[{"key":"ChargingScheduleAllowedChargingRateUnit","readonly":true,"value":"Current,Power"}]}] 2021-12-08 10:43:49 INFO (MainThread) [ocpp] EVB-P20482857: receive message [3,"b160c6e0-459c-46d4-bde0-28b9202f92a7",{"configurationKey":[{"key":"ChargingScheduleMaxPeriods","readonly":true,"value":"25"}]}] 2021-12-08 10:45:16 INFO (MainThread) [ocpp] EVB-P20482857: receive message [3,"bc0f5603-5552-4b75-bdf5-5cc5f06af4db",{"configurationKey":[{"key":"ReserveConnectorZeroSupported","readonly":true,"value":"true"}]}] |
|
The readonly just means it is not a configuration key you can change. So to get diagnostics you'll have to use an ftp server rather than http. |
|
It would be worth trying the get diagnostics service to see if it provides a more detailed error log |
|
So, I added all parameters I think are interesting. Anything else interesting? I guess I just need a anonymous FTP running for that? |
|
I guess so, mine only uses http so can't help much I'm afraid. |
|
Even easier: I used the official FTP addin from Home Assistant and enabled uploading etcetc for one user and then used this on the diagnostic data service: ftp://hassio:hassio@192.168.181.42:21/config/ (last / is important!) I can verify that it's a rolling log file keeping ~1000 lines of data in csv format. As the last try is from yesterday I will do the real thing later at home, but for the ones curious, here a log without the events, but with all the settings: EVB-P20482857_211208_121633.csv Real one follows later. :D EDIT: Log with no car plugged in... looks useless... Tried a dozen times with rejected as answer the last hour. EDIT: What works is changing configuration parameters with the service for that: evb_MinimumChargeCurrent: 160 |
|
Hi |
|
It's sort of supported by now. If you wanna connect it, open the EVBox Connect App and in the Advanced settings set a custom server instead of the Everon Default setting. ws://IP.OF.HA:9000/ is the way to go. Dont forget the / at the end. |
add EVBox Elvi to supported devices (#221)
|
Hi @dreimer1986 Could you point me in the right direction where exactly I should define my the server URL of my HA? These are the steps I take:
I seem to be able to find the APN url, although that seems to be for the mobile data connection and not what I need. thanks for your help! Screenshot of the options in the Installer Mode: |
|
That Last Mile Solutions needs to be set to custom. |
|
Hi A second confirmation the Elvi is indeed supported ;-) thanks a lot! |
|
What happens to you if you try to change the Max Current? I am thinking about trying to contact EVBox by Mail. Last time they were not very helpful, but.... maybe |
|
Hi At home I only charge at 3,5kWh (1 phase). Is there something else you want me to test?
|
|
Could you check the log entries for a Rejected coming from the addin? |
|
Hmm, no reply, but likely the same problem anyways. Btw, with the new notifications I get these two now: Looking at report #263 I wonder where these values it wants to set there are coming from and stay empty for me. The report has the same rejected, but at least tries to send data. Running v0.4.3-beta btw |
|
The MeterValuesSampledData should contain the list of measurands the charger supports. They are selected when setting up the ocpp integration. If you look at your log for MeterValues you will see what your charger sends by default. |
|
Hmm, right you are. I added a few more checkboxes in Plugin config and now it is filled with a small list of measurands. Still rejected though ^^ |
|
If you look at your HA log for the MeterValues message you will see what your charger sends by default (ie supports) or refer to charger manual, then only select those when setting up Ocpp. |
|
Yes, I see the "Energy.Active.Import.Register". Still it dislikes and rejects both what was mentioned in the topic. Btw, no reply from the manufacturer yet |
It may be that it only supports Energy.Active.Import.Register , but unlikely, however it definitely will not support SoC (as it is for DC chargers) or export metrics unless it supports V2G. |
|
Well, it accepts it and it KNOWS about it, that is very clear now. I changed the allowed minimum from 6A back to 16A to get my car charged with some speed and then selected 14A in the unmodified version. And we went to SuspendedEV. So this looks more like on your side all is fine. Selecting 16A makes it resume the charging. I think here the story might be over for me for now. I will call the manufacturer tomorrow. Maybe that will be a bit faster than waiting for a mail reply. Maybe the culprit really is the missing Sensor. (Should not be the case as I can force it to the wanted power by modifying the minimum in the app though. But maybe the charger has some kind of firmware barrier here. I just wonder why it charged with full speed when combined with the official everon service. Thats the only thing I wonder how that changes anything here. Maybe time for some packet sniffing again ^^ |
|
Good luck, let us know if you get any further with it! |
|
issue seems to be resolved, closing |
|
Still not much news, but my traces found something useful: It tried to get firmware/G4P0422B0422v0.evb off it. |
@dreimer1986 I'm following your findings on EVBox Elvi and this integration in various issues in here with great interest. At the moment I use the integration in an automation that starts charging at non-peak hours. I'm also not able to get any (energy) sensor data out of the Elvi. Let me know if I can compare settings on my side. |
|
Well, I wonder if I am the only one with no way to set the current it should charge with. My Elvi prefers to stay on the minimum setting regardless what I say as allowed current in the addin. I will try the same again as soon as I find out why the firmware update service is gone from my HA setup., Now that I have a official FTP with always the most recent version the app always fails to install, I can at least try it with the same from the OCPP addin. |
|
Some more crazy news. After I sort of got back my services in a lil older version, I decided to try a firmware update to maybe fix a few of the problems. The Everon Cloud variant never worked and the App variant now out of nowhere finally showed the online available version 422v0, but failed to update too. (But gave me the FTP and login data in a new trace) And guess what. IT WORKED! The OCPP addin successfully managed to get a new firmware on my charger!!! What I did: Then I used that for the OCPP service: First I looked at the FTP logs: Looks good... Then I watched with sweaty hands at the Firmware Status sensor... And then... SUCCESS!!! Before: P0422B0422v0_RC3.210414_U6.0.0-050 So I finally bypassed the flakey App variant to update my firmware! It seems to behave nicely as far as I can tell from not at home. Charging test will follow this weekend. |
|
Congratulations Daniel, that is very encouraging to hear. Great that firmware updates are now working so you can leave the EVBox app behind. I am also glad that I don't have to rely on the Wallbox app any more for day-to-day use. Using the controls via HA is pretty much instant whereas the app would sometimes take up to 30 seconds to change the charging current. I don't know if I'll be brave enough to try a firmware update via OCPP or whether I'll return to the Wallbox app for that. Throughout most of last year there was a continual stream of updates from Wallbox but now everything has been stable for quite a while. Long may it continue! |
|
So. If I read things right, you select some limit on charger.Maximum_Current and it behaves nicely? Interesting... |
|
Sorry to get your hopes up Daniel. I have a Wallbox Pulsar Plus, not an Elvi 😒 However, it did take quite a few versions before the Set_Max_Current slider worked for me. Once it started, it hasn't stopped and I even have a similar control working in my Node-RED Dashboard, via a service call to HA. |
|
I see, still nice to see that things work on other boxes quite fine. ^^ |
|
@cheelio same questions to you: If not then I wonder which firmware you have. I really hope that my success helps out here. Sadly I first have to drive around again to get below 80% battery left to test. |
|
Thank you for your excellent writeup, I followed your instructions and updated the firmware (yolo) from 'P0417B0417v0_785.200220_U6.0.0-050' to 'P0422B0422v0.211223_U6.0.0-050'. I did not had time yet to play with the charger limit yet. At the moment I only charge with 1 phase and I'm still waiting for my energy company to dig a hole and bump it to a 3 phase installation. What I don't understand, How did you find out about the digital three-phase meter that's included our not? Is that some kind of additional option? |
|
You are even more crazy than I am :P Great that it works for you and we have another one with current firmware. So you had the services on 0.4.20? Here they are missing and I need to use a modified 0.4.16 for getting them back. I opened a report for that. It seems to be. There are Elvis with and without. And some even modified theirs to add the missing meter. (German forum with quite some success https://www.goingelectric.de/forum/viewtopic.php?f=34&t=64106&sid=06e79bd8018264f4f2e7d0fea5d2bfdc) It's not uber difficult, but I was not allowed to change anything inside the Box because of warranty. Thus I still think that missing the meter and it being disabled in the config app might cause all our problems. Likely it's a firmware limitation if the meter is not in the box... But maybe it was a firmware bug, too. We will see next time when I charge :D |
|
I actually had to downgrade the plugin to get the services working. Because the last working version you mentioned isn't available in HACS anymore, I had to pull the version directly from the github tag. After the firmware update I switched back to the last version of the plugin. |
|
Hmm, maybe because I have show Betas active... |
|
OK, I have GREAT news. I ran the car down to 71% and started a charging session. I immediately saw charge levels above 4000W which was the value it always stopped at with the older firmware. (min 6A was always used regardless what you tried to select) and tinkered around a bit with the charger.Maximum_Current selection. AND IT FINALLY WORKS! I can set around and the current is changing. I just set it to 16A and went up to >10000W again. Just like when I force it to do that with the min and max values in the app. @drc38 @lbbrhzn SO as a final and real conclusion... EVBOX ELVI is now 100% supported! You just might need to update the firmware first. (For that #389 needs a fix though. Looks like I am not the only one with that problem) |
Updating firmware via ocpp or the app should both be the same, as the charger controls the update process. Ocpp simply tells it where to download the firmware from, and then the charger reports back its progress. |
|
It should, yes. Just with the difference that this way I control the ftp. And it's stable and fast as it's local. It failed four times the official way yesterday, a dozen more times since I have the box and the update is a mess problem is quite well known with that box. For example the app should check for a newer firmware update version as soon as you log into the box by Bluetooth. Since forever it showed n/a there. That alone is wrong. The app always should show the most recent version, even if you have it flashed already. That is now the case, but still it never passed the downloading state. It always failed with the app variant. (Btw, there was a lil app update this week as it seems, so maybe that fixed the detection at least and thus managed to let the Box start an update, which allowed me to sniff the FTP data) |
|
I use this one for new discoveries if no one has a objection against it. Looks like it can "in theory" tell Current.Import and Voltage per phase? L1, L2 and L3 could mean something different of course... So you can select: Setting anything else causes a "Rejected" reply. Maybe these values do work if you have the more expensive version of the Elvi. Here all values reply with "Unknown", but feel free to try it out. |
|
The phases are defined in the OCPP standard. There is L1,L2,L3,N, L1-N, L2-N, L3-N, L1-L2, L2-L3, L3-L1. The integration supports additional phase info and stores it in the extra attributes of the relevant sensor entity when received. |
|
Hi @dreimer1986, Yesterday, my energy company changed my home power connection from 1x 35A to 3x 25A (Same tariff), My EVBox is already connected over three phases, so now I should be able to get more capacity out of it. My only problem is that in home assistant, the |
|
Sorry, I just read through all the posts in this issue and I just read that readding the plugin under a different name may work. And now I have a working slider. Can't wait to charge it. |
|
:D No problem. I made the mistake more than once in the past. Have fun. |
|
Small note for the Elvi owners: G4P0424B0424v0.evb is now available from FTP. I successfully updated once more by local FTP as explained on #221 (comment). Before: P0422B0422v0.211223_U6.0.0-050
Model changed, too: Before: G4E-WIFI Checking the diagnistic data the two changes above are found and a few more: Before: Before: |
|
I found out that the server these days is more this one here: ftp://35.233.114.176 This one is not so nicely filled with all kinds of firmware though... Seems like they changed some stuff. This server and newest Android App for configuration even seem to start a proper firmware d/l now, but even now it still is a... very unstable connection and aborts here at about 25 sec of loading data packets. I still have NO clue where the Wallbox gets these information from... App and Wallbox were tracked and there is nothing coming from the app to some place that looks fitting. Only the Box simply just says Hi to the new server and starts a ftp connection... |
|
I told you that I add news whenever I have some. After the warranty was over now, my Elvi was upgraded with a ABB B23 112-100 and the two Modbus wires were rebuilt. Now I confirm 100% compatibility with all and any sensor data including these: Energy.Active.Import.Register |
Version of the custom_component
0.3.21
Configuration
Describe the bug
Beforehand I have to say that I LOVE the work you all realized here. After the long time I lurk around here it became rock solid and shows all information I can get from the limited Wallbox I have. Thanks very much!
But sooner or later you will start to hate my Wallbox, that for sure. ^^ I kept the following a while by now and out of pure luck realized that it could be a problem I have with my Wallbox and getting information into my Home Assistant by the OCPP addin.
Some history beforehand. I wondered all the time why my 11 kWh Wallbox only charges with about 4 kWh. Now I found out why. I can set a minimum charge current (default 6 A -> ~4 kWh) and a maximum charge current (default 16 A -> ~11 kWh) in the App of the Wallbox. When I connect the box to the Everon service EVBOX provides it seems to happlily charge with full speed. When it's connected to the OCPP addin it seems to stay on 6 A aka the lowest setting. I can force the box higher by increasing the minimum setting in App, but that was not needed on Everon. So I thought, the addin should support setting the current as the Wallbox should have that feature. I tried the Maximum_Current bar selector while charging and moved it to 16 A aka a legit value. "Rejected" Then for fun I tried 10 A (at that time there still was a 6 A Minimum set up in App.) "Rejected". Setting the Maximum_Current to ANY value causes a "Rejected" answer. See log Part 1. Maybe something to do with the earlier configuration problem "Rejected while setting MeterValuesSampledData to" And yes, after the ...to there comes nothing in log. See Log Part 2.
Debug log
The text was updated successfully, but these errors were encountered: