Firmware 4.0 for go-e-charger with new parameter "amx" for PWM Signalisierung.
Closed this issue · 6 comments
Hello colleagues,
first of all: thank you for providing this adaper for iobroker - this is working great on my side.
I am not sure if you saw the latest 4.0 firmware change. According to
goecharger/go-eCharger-API-v1@3d46503
there was a new set parameter "amx" created in parallel to "amp" to set one and the same value. The basic difference between amx and amp is, that since firmware 040.0 there is a possibilty to change the max_load parameter only in "ram" of the machine and not writing it to the flash (and yes, it will be copied from flash during a re-boot). Flash write access is limited both from space also from lifetime, so it makes sense to use amx instead of amp for setting max_load.
Is it possible to implement something like this -that shouldn´t be a big thing. I could offer to code if my help is needed.
if firmware >= "040.0"
use set (amx)
else
use set (amp)
Bests,
Markus
Sounds like a very good idea - I will check this
You could do me a favour.... my charger is still on firmware 033 - I would need someone to test on 040 if the object info.firmware is filled correctly. Version 0.3.2 reads the firmware.
Of course I could offer to check that and thank you verry much for catching that up!
http://192.168.178.nn/status delivers me:
{
version: "B",
tme: "1112201404",
rbc: "36",
rbt: "1718508044",
car: "1",
amp: "8",
[...]
There is no amx parameter delivered at the moment in status.
Perhaps we do nevertheless have a chance to check that: by getting a setter for amx I could set that. It should (?) be visible in the app accordingly. After reboot it should be then "the old amp" value. Indircet evidence, I know - but that could be a way of testing as long it is not delivered in /status.
Updated my system to 040.0
"amx" is implemented, but not working.
As you've noted, it isn't delivered in /status, but after setting it's value is responded as "amp". In the app you can't notice something and in the next status the old "amp" value is delivered again.
OK - my vault - two agents tried to write o the same box simultaneously.
It's working in my setup. Adapter version 0.4.0
Release of version 0.4.0