Hope you tried the app on the phone already. Not sure what can cause this.
I tryed now on iPhone and it worked. But its strange and should be investigated … normally im using the phone only to look or switch, not to repair device integrations. I do configuration mostly on my desktop.
Could be investigated. Probably a combination of a lot of different things. Feel free to do research on it and create a pr. Thanks and good to know that you have a working system now.
1 Like
Added support for energy tab. Currently in test
2 Likes
Unfortunately I encounter still device unavailable errors also with v0.7.7. Restarting the app solves the problem immediately (for a couple of hours or days)
As mentioned earlier this is not an issue in the app itself. This looks like an issue with the app communicating with the bmw server. What is the version of the homey server? Maybe disable ipv6 and try…
Using Homey Pro v12.4.6.
No IPv6 using on the LAN but I’ll be investigating further, thanks.
Same issue here since a couple of days. Not sure what changed…?
Different error message here, but this seems to happen every hour or even more often. This happens just after the log record "Adding capability ev_charging_state to device ‘carname’
Is there something we can debug (with HomeyScript)? Ik have found an article about handle the node.js ‘getaddrinfo ENOTFOUND’ error.
Best Practices for Handling getaddrinfo ENOTFOUND in Node.js
- Implement error handling mechanisms in your Node.js code to catch and log the
getaddrinfo ENOTFOUNDerror. - Consider retrying the DNS resolution
@bMi
Do you have the latest homey version. The app checks homey version validates that it is after 12.4.5 and only then adds the capability. Looking at the error seems like homey is complaining that the capability is invalid. Did you try pulling the plug and waiting then plugging it back in. Let me know.
Added a host table record in my router for cocoapi.bmwgroup.com with a cloudflare resolved IP address, maybe a temporary work around.
Within 48 hours a new different message.
What log level can I use to find some information about this?
Homey 12.4.7 - BMW/Mini Connected app v.0.7.7
Been having issues with lost connection for several weeks now. Fail 1-2 times a day at least. Worked perfectly until 0.6.4 update and after that failed constantly. Removed vehicle and added again, still same issue, cleared token as well.
Will push a new version where you can use a setting in the device to never put the device to unavailable. It will keep retrying and if it fails it will be silent.
I do like that as that allow me to know that there is an issue. But seems like a lot of people are having issue with that.
Will there be any cars that functions as start charging and stop charging?
My EV charger is an dumb charger unfortunately and wont detacet spotprice.
Have an IX40 changing to IX45 soon.
Not sure how it would work if I changed the 3 phase to a Shelly main fuse that monitors consumption and the program that one to allow charging when spotprices are low.
Hi, thanks. I do have the latest Homey version as it auto-updates. I will try to plug out and in after waiting a while when I get back home.
Hi All,
Please realize that this error was always happening as nothing changed on using the bmw api itself. As part of the streamlining of the login flow this unavailable marker was added. Previously the api would fail but no error would be reported anywhere. Thats why a lot of times people complained that there have been no update for a while.
Currently after a few failures the device is marked as unavailable and further attempts to communicate is stopped. Once i have some time i will push change where the attempts will keep continuing and mark the device again as available once the communication is reestablished.
1 Like
Not sure. But most likely it is the charger which shows a car. As it cannot be sure if your car is charging at home or charging somewhere else.
I have a smart meter on my dumb charger which is registered as a car charger and it does show in my garage.
