1.5.0 Feedback

beta-testing
Tags: #<Tag:0x00007f47fea6f598>

#42

Can confirm. I am no longer seeing my camera snapshot via iOS notifications either.


#43

I’m using 1.2.0 version of Home Assistant Companion, installed on iPad 2, iOS 9.3.5
as per suggestion from @DavidFW1960 from post
I just fill in the URL and tap save https://community.home-assistant.io/t/home-assistant-url/21483/25
however I never get any prompt for username and password and still getting below error:

after click on Done, connection error:


#44

I loaded the beta app v 1.2.0 running against Home Assistant 0.79.2 (HassIO). I can connect to Home Assistant, but the app doesn’t display any of the HA interface, just the blue header bar.

(tried to upload an image - not sure if it will display)

I’m still using an iPhone4s running iOS 9.3.5. I should also mention that Safari hasn’t been able to display the HA interface since the upgrade to HA 0.79. Both the app (1.1.2) and Safari were working with HA 0.78.3

Thoughts?


#45

Is there a way to force some reasonable dimensions to iFramed content. Here’s an example of my glances screen on iPhone X for instance.


#46

I am having this problem too. Have you had any luck?


#47

No luck, using the latest beta version (1.2.0 38).

If I leave “External URL” empty and just fill in “Internal URL” then it states the URL is invalid. When I provide an external URL then it tries to connect but still fails with “Error: invalid client id or redirect url” and in HASS I can see:

2018-10-03 07:14:41 ERROR (MainThread) [homeassistant.core] Error doing job: SSL handshake failed on verifying the certificate
Traceback (most recent call last):
File “/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/asyncio/sslproto.py”, line 625, in _on_handshake_complete
raise handshake_exc
File “/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/asyncio/sslproto.py”, line 189, in feed_ssldata
self._sslobj.do_handshake()
File “/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/ssl.py”, line 763, in do_handshake
self._sslobj.do_handshake()
ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1045)

I am providing http://:8123 as the URL for both internal and external since leaving External blank prevents me from saving it.


#48

Some wrong texts in the settings screen in 0.38.

Listened to the new podcast and wow what a nice features are planned to add to the app. Thanks @robbiet480 and @blackgold9! You guys are doing a great job with this new version and really looking forward to 2.0 :+1:


#49

I had the 1.2 beta installed for a few days… every day when I would leave or arrive at home, HA would mark me home, then 5-10 min later, mark me away. The opposite would happen when I would leave: It would first mark me away, then a 5-10 min later (when I was miles away from my Home) it would mark me present again.

Is this known?


#50

@ha_steve, I’ve had a similar issue occurring in both the 1.2 and 1.5 betas…I leave home and 5-6 minutes later the app marks me as “home” for a minute and then back to “not_home”. Additionally, I’ve been having issues with the app never moving from a region to “not_home” (it was noted in recent beta build notes but has returned) even though a notification pops up on the device indicating the device left a specific zone. I’ve attached my debug stuff (sanitized) below:

2018-10-05 08:28:03 INFO (MainThread) [homeassistant.components.http.view] Serving /api/ios/identify to 127.0.0.1 (auth: True)
2018-10-05 08:28:03 INFO (MainThread) [homeassistant.components.http.view] Serving /api/services/device_tracker/see to 127.0.0.1 (auth: 

True)
2018-10-05 08:28:03 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event call_service[L]: domain=device_tracker, 

service_data=host_name=xx, attributes=trigger=Geographic Region Exited, source_type=gps, battery=98, gps=[xx.xxxx, -xx.xxxx], dev_id=xx, 

gps_accuracy=75, service=see, service_call_id=a495b5bc0f3c4cb58aec2912bdc61ffc>
2018-10-05 08:28:03 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=device_tracker.xx, 

old_state=<state device_tracker.xx=MLMS; latitude=xx.xxxx, trigger=Geographic Region Entered, longitude=-xx.xxxx, source_type=gps, 

friendly_name=nick, entity_picture=/local/nick.jpg, gps_accuracy=75, battery=99 @ 2018-10-05T08:22:54.641833-04:00>, new_state=<state 

device_tracker.xx=MLMS; latitude=xx.xxxx, trigger=Geographic Region Exited, longitude=-xx.xxxx, source_type=gps, friendly_name=nick, 

entity_picture=/local/nick.jpg, gps_accuracy=75, battery=98 @ 2018-10-05T08:22:54.641833-04:00>>
2018-10-05 08:28:03 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_executed[L]: 

service_call_id=a495b5bc0f3c4cb58aec2912bdc61ffc>
2018-10-05 08:28:03 DEBUG (MainThread) [homeassistant.components.websocket_api] WS 1673362736: Sending {'event': {'origin': 'LOCAL', 

'data': {'domain': 'device_tracker', 'service_data': {'host_name': 'xx', 'attributes': {'trigger': 'Geographic Region Exited'}, 

'source_type': 'gps', 'battery': 98, 'gps': [xx.xxxx, -xx.xxxx], 'dev_id': 'np', 'gps_accuracy': 75}, 'service': 'see', 'service_call_id': 

'a495b5bc0f3c4cb58aec2912bdc61ffc'}, 'context': {'user_id': '933584a4b61e4a1891f637ee1867236e', 'id': 'bc6a1ee974d045d8a52cbe0588e0592c'}, 

'time_fired': datetime.datetime(2018, 10, 5, 12, 28, 3, 276263, tzinfo=<UTC>), 'event_type': 'call_service'}, 'id': 1, 'type': 'event'}
2018-10-05 08:28:03 DEBUG (MainThread) [homeassistant.components.homekit.accessories] New_state: <state device_tracker.xx=MLMS; 

latitude=xx.xxxx, trigger=Geographic Region Exited, longitude=-xx.xxxx, source_type=gps, friendly_name=nick, 

entity_picture=/local/nick.jpg, gps_accuracy=75, battery=98 @ 2018-10-05T08:22:54.641833-04:00>
2018-10-05 08:28:03 DEBUG (Thread-5) [pyhap.characteristic] set_value: OccupancyDetected to False
2018-10-05 08:28:03 DEBUG (Thread-5) [homeassistant.components.homekit.type_sensors] device_tracker.xx: Set to 0
2018-10-05 08:28:03 DEBUG (MainThread) [homeassistant.components.websocket_api] WS 1673362736: Sending {'event': {'origin': 'LOCAL', 

'data': {'entity_id': 'device_tracker.xx', 'old_state': <state device_tracker.np=MLMS; latitude=xx.xxxx, trigger=Geographic Region Entered, 

longitude=-xx.xxxx, source_type=gps, friendly_name=nick, entity_picture=/local/nick.jpg, gps_accuracy=75, battery=99 @ 2018-10-

05T08:22:54.641833-04:00>, 'new_state': <state device_tracker.xx=MLMS; latitude=xx.xxxx, trigger=Geographic Region Exited, longitude=-

xx.xxxx, source_type=gps, friendly_name=nick, entity_picture=/local/nick.jpg, gps_accuracy=75, battery=98 @ 2018-10-05T08:22:54.641833-

04:00>}, 'context': {'user_id': None, 'id': '462ab0e98e2f4c0d8cbf7e62324512ef'}, 'time_fired': datetime.datetime(2018, 10, 5, 12, 28, 3, 

283064, tzinfo=<UTC>), 'event_type': 'state_changed'}, 'id': 1, 'type': 'event'}
2018-10-05 08:28:03 DEBUG (MainThread) [homeassistant.components.websocket_api] WS 1673362736: Sending {'event': {'origin': 'LOCAL', 

'data': {'service_call_id': 'a495b5bc0f3c4cb58aec2912bdc61ffc'}, 'context': {'user_id': '933584a4b61e4a1891f637ee1867236e', 'id': 

'bc6a1ee974d045d8a52cbe0588e0592c'}, 'time_fired': datetime.datetime(2018, 10, 5, 12, 28, 3, 289674, tzinfo=<UTC>), 'event_type': 

'service_executed'}, 'id': 1, 'type': 'event'}

It looks as if the app kept the device’s location as the zone it exited and didn’t change to “not_home” when it did indeed exit the zone.


#51

Exactly. And vice-versa for me… I arrive home, and 5ish minutes later, all my light shut off because it flips back to not_home

For me, the false home/not_home events are always logged as: Location updated via Visit and I noted that one of the recent changes was dropping SwiftLocation for a new framework called Visit so I’m assuming it has something to do with that.

Edit: Is there another place we should be reporting bugs?


#52

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.”


#53

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.


#54

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!


#55

Any further feedback in this? Why is it trying SSL when i’m connecting using HTTP.?


#56

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


#57

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.


Need help for an if statement for sending url attachement as notification
#58

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.


#59

I’m getting all of it, if it needs a GitHub issue i’ll reply letting you know


#60

No luck, keep on having same issue and this preventing any further testing. :frowning:


#61

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 transport