Has anyone had any luck from trying access HA through Nabu Casa remote UI on the tesla web browser?
Not working for remote UI or local- by dns or IP. You get it to work?
I just tried it and after logging into Nabu Casa, I selected ‘connect’ then got a blank page with a url ‘about:blank#blocked’
Did anything ever come of this? Just got a model 3 and tried it through Nabu Casa and also got the about:blank#blocked
I gave up on Nabu Casa and configured my router to forward port 8123 to the HA raspberry pi.
Using my home ddns domain, I can now open HA UI on the Tesla browser and it works great.
Whats the performance like? The Tesla browser is so brutually slow…
I’m trying to understand your post. I use DuckDNS rather than Nabu Casa, and I have port 8123 forwarded for my HA instance, but still can’t load into HA in my car. Any advice?
OK so update 2022.12.3.1 rolled out last week, one of the undocumented changes was from Chromium 88 to Chromium 98. I don’t know how that would effect this originally being blocked but I am now getting access to my Home Assistant server using Nabu Casa!
2 Likes
I have a Model 3 (NZ new so versions and software options may be all over the place).
The software version is 2022.16.2 86e60d9a2bcf
First problem is that when I try to access wifi it constantly switches between wifi and LTE. That makes testing very hard. If anyone has any tips on that one let me know. The Tesla is about 4m from my garage AP.
Anyway, it won’t connect to Nabu Casa at all on either wifi or LTE. Nor, when on wifi, to HA on my home network. Via the home network it is only on http, and the Tesla tells me the situation is unsafe, but doesn’t allow the usual clickaround.
On LTE via Nabu, it cannot even get a DNS record when I enter https://mylongstring.ui.nabu.casa
Any other clues? And how can I see what version of Chromium I have?