@Sunil
The 2fa 6-digit code is for apps, not for programs using a web interface. You can ignore the one you mentioned. The Authentication code you need will be sent using a request displayed is the HA notification area.
@gcobb321 I am trying to use the ic3 device entities by assigning them to a person in HA and then using Groups to group the person entities for him or not_home determination in my automations. However it seems Groups wont function correctly when its based on ic3 entities. Groups doesn’t properly determine home and not_home. I tested this when I removed your entities and added the HA IOS app one to my person entities and then Groups worked just fine. Am I doing something wrong? I simply want to use your logic to determine when the house is empty or not for automation purposes.
Hello all, I am in my first few months on using Home assistant and Nabu casa, so I apologize if my search did not turn up a previously covered answer. My location is stuck for days on AWAY. I have reset HA and my ios device several times and can’t seem to find where the hang up is.
If it helps, there are two people on my system and I am the admin. The other person is tracking ok. It was stuck a week ago as well. Rebooting the phone seemed to fix it. Now Im stuck.
2020-08-12 18:35:30 ERROR (MainThread) [homeassistant] Error doing job: Task was destroyed but it is pending!
2020-08-12 18:35:51 WARNING (MainThread) [aiohttp.websocket] websocket connection is closing.
2020-08-12 18:35:51 WARNING (MainThread) [aiohttp.websocket] websocket connection is closing.
2020-08-12 18:35:51 WARNING (MainThread) [aiohttp.websocket] websocket connection is closing.
2020-08-12 18:35:51 WARNING (MainThread) [aiohttp.websocket] websocket connection is closing.
2020-08-12 18:35:51 WARNING (MainThread) [aiohttp.websocket] websocket connection is closing.
2020-08-12 18:35:51 WARNING (MainThread) [asyncio] socket.send() raised exception.
2020-08-12 18:35:51 WARNING (MainThread) [aiohttp.websocket] websocket connection is closing.
2020-08-12 18:35:51 WARNING (MainThread) [asyncio] socket.send() raised exception.
2020-08-12 18:45:03 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.140340333007008]
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py”, line 125, in handle_call_service
await hass.services.async_call(
File “/usr/src/homeassistant/homeassistant/core.py”, line 1281, in async_call
task.result()
File “/usr/src/homeassistant/homeassistant/core.py”, line 1316, in _execute_service
await handler.func(service_call)
File “/usr/src/homeassistant/homeassistant/helpers/entity_component.py”, line 208, in handle_service
await self.hass.helpers.service.entity_service_call(
File “/usr/src/homeassistant/homeassistant/helpers/service.py”, line 454, in entity_service_call
future.result() # pop exception if have
File “/usr/src/homeassistant/homeassistant/helpers/entity.py”, line 595, in async_request_call
await coro
File “/usr/src/homeassistant/homeassistant/helpers/service.py”, line 485, in _handle_entity_call
await result
File “/usr/src/homeassistant/homeassistant/components/lock/init.py”, line 120, in async_open
await self.hass.async_add_job(ft.partial(self.open, **kwargs))
File “/usr/local/lib/python3.8/concurrent/futures/thread.py”, line 57, in run
result = self.fn(*self.args, **self.kwargs)
File “/usr/src/homeassistant/homeassistant/components/lock/init.py”, line 116, in open
raise NotImplementedError()
NotImplementedError
2020-08-12 18:56:13 WARNING (MainThread) [homeassistant.helpers.entity] Update of lock.entrance_door_7 is taking over 10 seconds
Perhaps your lock component. Comment out your custom components and restore one by one until the error reoccurs. I don’t recognize the trouble from your errors.
#---- Set Someone Home Flag --------------------
- platform: template
sensors:
someone_home_flag:
friendly_name: Someone Home Flag
value_template: >
{% if is_state('sensor.gary_iphone_zone_name1', 'Home') and is_state('sensor.lillian_iphone_zone_name1','Home') %}
home
{% else %}
all_away
{% endif %}
Hi @gcobb321
Running v2.2.0rc10 I’ve found once iCloud3 goes into a stationary zone it gets stuck there until the iOSApp enters a different zone or the iCloud3 update interval expires.
It seems like the significant location changes are being ignored or missed. From the logs it looks like the sig loc change time is screwy. In the screen shot below 12:58:05 was about when HA was restarted. There were significant location changes since that time but it remains at 12:58:05.
Another thing I’ve noticed is once the iCloud3 interval expires and the location is updated, the iCloud3 sensor state remains as Stationary even though the coordinates are updated and the log status correctly says away.
@scotty1395
You may have more than one iosapp Mobile app Integration in HA and iCloud3 is not monitoring the correct one. I ran into the same situation a while ago. . Restart iCloud3 and review the iosapp info in the Event Log as iCloud3 starts (Stage 2 or 3). It will show all the mobile apps found in the entity registry and the one that will be monitored. It used to monitor the first one found but was changed to the last one in RC 9 or 10 when more than one was found. Look at the entity name and the suffix (_2, _app, etc). If that is what is going on, delete The duplicate or add the correct suffix to the track _devices configuration parameter. If it do change, also look at the Device Name in the iOS App Configuration on the phone to make sure the phone has the same name as the mobile app integration being monitored.
iCloud3 seems to be monitoring the correct entities in the event log.
Does the state of the last_update_trigger entity need to change to cause iCloud3 to perform an update? What happens with repeated significant location changes in succession where the state doesn’t actually change?
@scotty1395
No, the state doesn’t need to change. It looks to see if the update time If the trigger has changed and if that time is after the last time the last locate time. If it is, the gps lay/long from the device tracker entity is used to update the phones location. Us it Us older, it ignores the trigger.
In your event log, the time 12:58:05 was older so it was ignored.
Have you checked the Event Log on the phone? Also see if the stationary zones are on the phone. HA passed the updated stat zone location but I do not know how the schedule is determined.
Hmm. I think the update time might be the problem. The update time only changes if the state changes.
Tested by doing a manual pull down update in the app - state and update time changes, Launch to Manual, wait a minute and do another pull down update - no change to state (Manual to Manual) and update time still says a minute ago.