I’ve been clicking on the “email beta something something” (don’t have my phone in front of me) in the testflight Home Assistant app listing and sending brief findings to @robbiet480 and @blackgold9. I’m not entirely sure if we should open up an issue on github or not? One thing to test…If you go into settings, privacy, location services, system services and either clear the frequent locations OR turn them off completely it may clear up the issue since it’s using the SwiftLocation Visit stuff, albeit temporarily IF you only clear the locations until they’re “rebuilt.”
This is still happening for me in the latest version. I can work around it by disabling WiFi before trying to open settings, but it makes it very difficult to check the settings.
New version removes Visits which should clear up location issues. New version also hides away advanced options like use legacy auth and basic auth.
Keep the feedback coming!
Any further feedback in this? Why is it trying SSL when i’m connecting using HTTP.?
robbie Looking at the event log on the ios app version 1.05 the url appears to be filling out incorrectly when trying to show an image. this is what I get in the paylod file when I receive a notification with an image
“url” : “http://torn*****/local/front_door.jpg”
of course the formatting isn’t showing correctly
“url” : "http:Wtorn*****VlocalVfront_door.jpg
The link I get for the live feed view is
“url”: "/api/camera_proxy/camera.front_door_camera?token=XXXXXX
“url”: "VapiVcamera_proxyVcamera.front_door_camera?token=XXXXXX
Not sure if its relevant or not.
Hope this helps
The attachment and camera notifications are currently broken because of the new API, I believe @blackgold9 is shooting to have a fix out in the next 48 hours for both.
1 Like
SwiftLocation was a old framework we used. The Visits Location Service is just one of the location update systems that Apple provides us, much like significant location updates.
I’m getting all of it, if it needs a GitHub issue i’ll reply letting you know
No luck, keep on having same issue and this preventing any further testing. 
I can’t find any reports of this, but I’m 90% sure this is because of the iOS app so I’m reporting it here first.
I’m running the latest beta - 1.5.0 (10) - and it seems whenever the app does something I’m getting the following error in my Home Assistant logs. Looking at the time stamps for these errors, it seems to coincide with a location change, and I can reproduce it by opening the app (and having it auto or manually refresh).
2018-10-10 08:57:31 ERROR (MainThread) [aiohttp.server] Unhandled exception
Traceback (most recent call last):
File "/srv/homeassistant/lib/python3.5/site-packages/aiohttp/web_protocol.py", line 410, in start
await resp.prepare(request)
File "/srv/homeassistant/lib/python3.5/site-packages/aiohttp/web_response.py", line 300, in prepare
return await self._start(request)
File "/srv/homeassistant/lib/python3.5/site-packages/aiohttp/web_response.py", line 608, in _start
return await super()._start(request)
File "/srv/homeassistant/lib/python3.5/site-packages/aiohttp/web_response.py", line 367, in _start
await writer.write_headers(status_line, headers)
File "/srv/homeassistant/lib/python3.5/site-packages/aiohttp/http_writer.py", line 110, in write_headers
self._write(buf)
File "/srv/homeassistant/lib/python3.5/site-packages/aiohttp/http_writer.py", line 67, in _write
raise ConnectionResetError('Cannot write to closing transport')
ConnectionResetError: Cannot write to closing transportJust wanted to state this very clearly here since i’ve been getting a lot of confusion about it:
Unless you know what you are doing do NOT use the internal URL. Just use the normal URL. Internal URL is ONLY useful to you if you are unable to use the same hostname to access Home Assistant inside and outside of your network. If this situation applies to you, then set the Internal URL to the hostname used to access HA inside of your network and the other URL field to the URL you use to access HA outside of your network.
In other news, notification fixes should be released in the next 12 hours if all goes to plan!
2 Likes
The latest beta has been working great so far.
Small thing I’ve run into. I had allowed motion tracking, then revoked the permission. Now, every time I open the app it asks if I want to reenable it or leave it disabled.
With build 14 of 1.5.0, I’m now seeing this:
EDIT: my own fault!
With the latest build 1.5.0 (15) I’m able to create Hassio snapshots. However, I’m unable to delete previous snapshots.
Where the discovered IP is coming from? My server has IP address 192.168.1.155, but it’s showing 192.168.1.54.
The delete trashcan and some other side panel stuff isn’t working. The devs are aware of it and it’s going to be fixed.
what is the base_url in config yaml? That seems to be where it’s being read from (I think)
OK, found the solution to this and it is working now. Python does not come with certs by default and that is the issue.
I’m using Python 3.7 on a Mac and I had to open Terminal and run:
sudo /Application/Python\ 3.7/Install\ Certificates.command
After that I restarted HASS and it should work.
Note, I tried it before restarting and that did not work. Thus I ran the above command in my virtual environment for HASS as well but I do not believe this is required as it just came back to the requirement is already up-to-date.
Hope this helps anyone else with this issue. 
1 Like
You were right, I had bad address here. Thank you.
1 Like