Volkswagen ID Forum banner
1 - 20 of 50 Posts

·
Registered User
White Pro S
Joined
·
248 Posts
Discussion Starter · #1 ·
I've started using EV Notify on my id.4, and have it connected to ABRP. Let's get our discussion going for this app.

For starters, I'd love to know what people are using for consumption values.

I'm currently fighting with android to stop pausing the app. It's a pixel 3 and it's been a while since I've used android.
 

·
Registered User
White Pro S
Joined
·
248 Posts
Discussion Starter · #2 ·
I should also add that currently the ios version of evnotify is unavailable due to some account issues for the dev. You can use the web gui here to view the data.

There's no real point in using the ios version for anything other than looking at your status anyway, thanks to all the problems with BLE and whatnot. You can do it, but you're probably in for a difficult time.
 

·
Registered User
Joined
·
85 Posts
I had it working great - and actually there was an update over the weekend that improved it - however, it has been glitching badly, when running through android auto, so I run on a separate phone. You can see here

 

·
Registered User
Joined
·
85 Posts
When they are working together, it's dynamic - thats what's awesome. So I set my speed to limit + 10% in ABRP, arrival at SOC to 5%, Degradation to zero, and max charge to 80. Based on my driving (long fast trips this past weekend, ABRP is using 298 as a number for planning.
 

·
Registered User
White Pro S
Joined
·
248 Posts
Discussion Starter · #6 ·
I've been working on modifying an automate script that I found online. It's good, but I found that it needed some improvement and customization to my specific phone to keep the app active. I'll share it with some tips when I'm done.

If anyone is looking for a good phone to use as a dedicated evnotify device, i'd suggest something that is easily rooted like a pixel 3. You can get them on swappa for around a hundred bucks, or a 3a for around the same, it takes usb c and can rooted easily to work well for this purpose.

Once it's done, the script will turn the phone on when the car is on, connect automatically to the bluetooth and start pulling data, keep the app active if the car is on or charging, and automatically shut the phone down when there is no charging activity and power to the phone. Throw in a cheap sim with a 1gb data plan and you can pretty much stash the thing someplace. Mine's going in the trunk for now but I intend to power it from a fuse tap once i've gotten all the bugs worked out.
 

·
Registered User
Joined
·
85 Posts
Well I have a spare 3a here at the house. Lets consider that the dev device - Lets see where this goes :)
 

·
Registered User
White Pro S
Joined
·
248 Posts
Discussion Starter · #8 ·
I've just spent way too much time adding a bunch of features and testing them. I'll post the instructions and automate flow tomorrow, so anyone who would like to try it can do so.
 

·
Registered User
VW ID.4 1st Max | Mangan Gray
Joined
·
189 Posts
you need to select the live data instead the preconfigured values.. otherwise it isnt getting the live data
 

·
Registered User
White Pro S
Joined
·
248 Posts
Discussion Starter · #13 ·

·
Registered User
Joined
·
370 Posts
Mine's going in the trunk for now but I intend to power it from a fuse tap once i've gotten all the bugs worked out.
@dg4prez Can you better explain how you plan to use your setup with the phone in the trunk? I'm familiar with EVNotify as well the integration with ABRP, but I'm not sure what you are getting out of a phone in the trunk. You are just doing this for data logging? or something else I'm not figuring out? I assume with your phone in the trunk will only be be connected BT to the ODBII dongle and not the car...and isn't concurrently using Android Auto.

Also, your automate script requires the phone to be rooted because the phone otherwise won't execute the BT connection? Thanks.
 

·
Registered User
White Pro S
Joined
·
248 Posts
Discussion Starter · #16 ·
I have an iphone for my normal stuff, so the android phone is just for the evnotify data collection and upload. It's overkill but if we weren't enthusiasts we wouldn't be talking about cars on a web forum.

The root isn't for BT but for the ability for the automation script to keep evnotify running, close it when it stops working and reopen, automatically start the app when the phone boots up (when you start the car) and turn the phone off when the car is done charging. It can also be setup to send me emails or sms for certain conditions if desired, like if charging stops before a certain charge level, etc.

I know I said it was nearly done but I added some safeguards and realized that the whole thing was overly complex. I'm simplifying it down and testing.
 

·
Registered User
Joined
·
85 Posts
Hmmmm. Choices, Choices. I cant root the I use for work, Samsung A7, so maybe root the LG Wing. I would like to log the entire roadtrip if possible. Will rooting give any issue to AA ? At some point I hope to reliably use ABRP with AA
 

·
Registered User
White Pro S
Joined
·
248 Posts
Discussion Starter · #18 ·
I can't say, as I've not used it in that way.

The author is in need of sponsorship though - if you plan to use his software toss him a few bucks a month for his efforts!

 

·
Registered User
White Pro S
Joined
·
248 Posts
Discussion Starter · #19 ·
OK, here's the files:

Android Automate on the Play Store
EVNotify Manager 1.0
PDF of Flow

If you use EVNotify, consider sponsoring the developer so the app can continue to grow and improve!

What you'll need is a rooted android phone (I recommend an older pixel, they're pretty cheap and easy to root) and to download the automate software on the phone as well as EVNotify Manager above, which is a flow file for Automate. You'll want to go into EVNotify and get it all setup and working. Record your Akey and Token from credentials in the app and setup any integrations you want, like with ABRP. Once that's done, go into the settings page. Click on the version number multiple times very fast. The secret settings menu will come up. Activate background mode (and persistent notifications), save. This will prevent your phone from shutting the app down most of the time.

Next you'll want to go into Automate and import the EVNotify flow file, then edit it. At the flow beginning, you'll see a box with "Set variable evAKey to" (box 189) and you'll want to enter the Akey from evnotify here. Do the same for the box with "Set variable evToken to" (box 190) with your recorded token. This allows the app the verify that EVNotify is running and get info from the app using the application's web api. It will also allow for added functionality in case we want to add features like battery threshold notifications, things like that.

Now comes the tricky part. I've set this up for my device, which is a pixel 5. It's possible this will work just fine on your phone, and it's possible that it won't. When EVNotify Manager starts, it basically switches to EVNotify, clicks the settings button, then waits a bit and clicks the dashboard button. This is necessary to get everything moving sometimes. Unfortunately, because of how the app is built, it requires that we simulate a tap, which means that depending on your phone, the tap location could be completely different. You'll know it's working because when the app starts, it will wait 5s, say "click settings", and then go into settings. After another 5s, it will do the same for dashboard. If it does all of that, then you're all set! If it does not, then you'll need to edit the Interact touch click settings for each and find the right coordinates. The boxes are 15 and 34.

Once you've got all that sorted out, you can plug your phone into the car's power and forget it. I've got mine set to the accessory circuit on an addon tap under the dash with normal operation - off when the car is off. Leave the EVNotify manager running, and when the car starts, it will trigger the phone to turn on. Automate will then restart EVNotify and keep it running for as long as the car is running. Once the car is off, it will wait for ten minutes. If the car is plugged in and charging during that time, the phone will remain active and continue to update. Once charging is complete, the phone will wait ten minutes and shut down until the next time the car is started. If charging does not start within ten minutes, it will turn off the phone until the next car start. This value can be changed in box 68, timeUntilShutdown. Set it for as long as you want.

You'll want to mess with the phone settings as well to minimize data usage. I've got the cheapest data plan possible, a gig of data, and evnotify has used about 25mb in a month's time. If you don't disable most other things, google will absolutely suck up your data. Something called pixel tips used about 600mb of mine. So keep an eye on things at first.
 

·
Registered User
ID.4 FE MB
Joined
·
41 Posts
1 - 20 of 50 Posts
Top