I might have spoken a bit too soon. Although it initially worked, data has freezed again. Right now all stats show ‘2 days ago’ as moment they last updated.
As mentioned earlier this charger is backoffice connected. I have a slight feeling that the backoffice connection might be overwriting things, it would help if someone could verify that this might actually be causing my issues.
Symptoms:
Connectivity worked, briefly
Connectivity than stops.
Rebooting either the charger, app or homey doesn’t help
Logging into the charger using ACE from my local network doesn’t work (Login request timeout)
When I connect the charger directly to my laptop, I can connect with ACE
Exit ACE (no changes made whatsoever)
Reconnect to my local network, connecting to the charger via ACE also works
Exit ACE (no changes made)
Enable the Homey app again, now works
Back to square one, this repeats itself over and over again
Due to these symptoms my gut feeling says that this loop triggers something that enables a local connection, but backoffice then pushes config which disables this again. The only thing not aligning with this assumption is that I’m not changing a thing in the charger, apart from connecting it to my laptop directly and then back into the network. Very weird behavior this, so I was wondering whether anyone else has had similar issues?
not similar, outside the fact that connection has become very unstable, and cant reach the charger to change anything anymore. Home can readout the power the charger gives, but every change (gree, comfort, default) triggers a timeout
Mine is also connected to a backoffice. And still works like a charm. (I haven’t tried the start and stop flows) Stopt working a week ago, but that had to do with the Shell tag. Shell change something and the charger refused the tag due to that. A phone call to the backoffice fixed it.
Has something change in you network that might trigger a new ip-address for your charger in stead of a fixed?
No changes as far as I know. I’m not changing any modes myself, I only need it for monitoring. The charger has a fixed IP which is assigned correctly, it’s always on the same IP. I have it in an IoT network / subnet, but Homey is on there as well so that shouldn’t be the issue either.
It stalled again. I tried disabling / enabling the app as a reboot mechanism, which didn’t work. I then thought I’d try something new to debug, so I removed the step with ACE. I did the following:
Disable the Alfen Homey app
Disconnect charger LAN cable, waited a few seconds and then reconnected it. No difference.
Disconnect charger LAN cable and plugged it into my laptop directly. Started ACE to verify the charger was visible, but apart from that didn’t establish any sort of connection.
Disconnected LAN cable from my laptop and reconnected it to the switch (same port, same IP)
Re-enabled the Homey app, now works again!
Fairly confident that it’ll stop working again soon, but this gives me a bit more information. It’s not a configuration change or anything ACE related.
Found something which might be useful in the logs:
Failed to parse property ‘2077_0’
Could this be related to the webserver calling quits? I also see evidence that points to the webserver restarting when the network connection changes, so that explains why the above helps in reestablishing a connection briefly.
You’ll need to help me out here, how do I do that? I don’t see anything that seems related in the logs. I’ve installed the MyEve app and successfully connected, but where do I see the codes of these properties?
This is quite interesting. You are on the latest test version of the app right (2.1.1)? I can’t find it in the code that it is retrieving that property. So I’m a bit confused how the Homey app can throw that property as an error…
Yeah latest version. I came to the same conclusion, so I’m not even sure that the log line is related to the app. It’s just something I though was worth mentioning. For clarity; the log line is on the charger itself, found it using ACE.
I just now used ACE to login to the charger again, after which the logs show the same error again. So might be something that ACE is trying to query and unrelated to the app. But that would leave me blank again trying to figure out why the app stops working after x amount of time.
It worked for quite some time, but this morning I noticed the updated have stalled again. For more debugging I’ll try disabling the app and use eve connect for a while. Let’s see whether that also fails over time, which would pinpoint the issue to the charger instead of the app or vice versa.
I found that this morning, the Eve Connect app also doesn’t want to connect to the charger any more. So that implies the issue is with the charger, not with the app. Might be the network cable, I’ll work that out. So for now I don’t think the app is to blame.
Here also still problems. MyEve can’t fetch property’s, EVE connect gives error code 206 and charger doesn’t charge the car (gives also error 206 in the display). Tag (laadpas) not accepted. Have version 2.1.1
If both Alfen apps cannot connect and your tag is not accepted then it is an issue with the setting in your charger. Doesn’t have much to do with this Homey app functioning or not.
I have a Algen account but is not for this app i discovered and (of course) password for de charger it self.
(I had never experimented problems so I am quite new in this)
For following people, problem solved with the ACE service installer software tool. As @Walter_vande_kerkhof mentioned was the socket “in-operative”. Possibly coursed by app issue? @Walter_vande_kerkhof Thans.
. Will send it to you in a personnal message
