u/thearsenalinn

Is this possible?

I have just taken delivery of a Tavascan but for the next few weeks I still have a Born.

When I try to add the Tavascan I get a message saying the VIN is correct but not ready to link to the system.

Email back and forth with app customer care has resulted in them saying I need to take it to a dealer as the slowly blinking red light on the SOS button means there is a hardware fault.

Anyone else had such issues? Do I really need to go to dealer? They’re not exactly local.

Is this still broken by VW?

Still sat on my dashboard, can’t bring myself to delete it.

Not a problem at the minute but come winter not having an automation to heat the car in the morning if it’s below a certain temp is going to be a huge pain in the arse. (I suppose a reverse of this to cool it at the moment would be nice)

About to trade in my Born for a Tavascan and honestly this is one of the things giving me pause for thought at the moment.

I’ve seen a lot of posts about how amazing this is. People seem to have got immediate dashboard results.

I’ve been using this intermittently as a hobby to create and improve a tablet dashboard.

Automation writing is brilliant, problem solving a little hit and miss but definitely helpful. It’s also created a guide / instruction manual in parallel for both everyday use and under the bonnet code which is invaluable.

My biggest issue though: MCP drops constantly. At which point HA itself seems to be down. Claude goes in and does an update, but then any further investigation is impossible because it cannot communicate with MCP. I have to reset and HA now seems to take an age to reboot.

Has anyone else had similar problems?

I see a few posts with people using cheap Amazon Fire tablets as their Home Assistant dashboards.

I've done the same but I feel like I'm constantly fighting a losing battle against battery drain, how do people fix the following?

1. motion wake when approaching. if the tablet sleeps then when it wakes it wakes to an Amazon advert not Fully Kiosk. my solution was to change the automation so it changed screen brightness from 1 to lets say 100. ie. it's always 'on' but dimmed when no-one is near, however this leads to

2. excessive battery drain. i figured this was in part due to the always 'on' state but after some investigation with ADB it's more to do with the sheer amount of Amazon bloatware. Some I've managed to kill but Amazon protects a lot of it, and if you reset the tablet it boots up even more each time, meaning a quickly draining battery and multiple charging cycles in 24 hours,

3. i automated the charging so that the plug isn't on 24/7. Battery below 35% charger on, battery up to 80% charger off. problem seems to be that while a Fire tablet can charge at 15w, a new power cycle doesn't negotiate PD very well and often only connects at 4-5w. I've automated a 'retry' cycle if lower than 6w but often it just ends up around 8w. I have to physically unplug the cable from the tablet and then it immediately reverts to 12w or more.

Anyone else encounter issues like this? what do you do about them?