Is this still the issue with current HA 93.2? I run HA in a venv and I guess I’m unsure of the steps needed for this “link loop” to stop. Thanks and sorry if this is obvious.
How do you start HA? If you use systemd, take a look at the github issue I linked (ie. set the WorkingDirectory directive to a writeable folder). If it’s any other way, describe it and I’ll see if I can figure out what you need to do.
Feel free to PM me if you want to go through this without dumping all your config in this thread.
I use systemctl instead in a venv for HA. So the command is:
sudo service home-assistant@homeassistant start
systemctl is part of systemd.
Update the homeassistant service to include a WorkingDirectory directive, see the github issue previously linked for an example. The service file is likely at path /etc/systemd/system/[email protected]
I got my credentials via email last week and the link threw me “client_id is not valid”. So I tried again today and the link worked. But sadly I used my google account instead of my Email-Login to Logi, so no entity was showing up…
I have now deleted the integration from Home Assistant and removed the “logi_cache.pickle” in my config folder. The integration configuration is back again, but when I press Configure, no window shows up where I can click the link to activate again. What should I do to properly “reset” the configuration of Logi Circle?
What should I do to properly “reset” the configuration of Logi Circle?
The method you describe should work. Delete the integration, and re-add through the integrations menu. (I just tested it here and it worked on 0.93.3)
When you say no window appears where you would click the link, what happens instead? Nothing at all?
Greetings,
I have a couple Logi Circle cameras that I only want recording when the home alarm is set to armed. I have my Logitech credentials and I’m using the native Circle code in 0.93.2 HassIO. My URI is through nabu.casa. The cameras are working correctly and showing up in the HassIO interface. What I’m trying to figure out is what service call I’d use in my automation to turn recording on and off with the alarm? Service camera.turn_off for the camera entity gives me:
AttributeError: ‘Camera’ object has no attribute ‘set_streaming_mode’
Thanks
Yes, nothing at all.
Just tried from another PC, it worked this time. Now the camera is correctly showing up.
Just a sidenote, I tried to change the device id in HA to the same one as the old version of logi circle integration was, just so save some time editing automations. It told me the device entry already exists.
I had to manually delete the old circle from core.entity_registry. Was that the correct way of dealing with it? The camera seems to work fine now.
Never mind…I figured it out.
Service camera.turn_off for the camera entity gives me:
AttributeError: ‘Camera’ object has no attribute ‘set_streaming_mode’
Glad you figured it out, but thanks for calling that out - it’s a bug. I’ll raise a PR for it when I get a chance.
Assuming you’re talking about a sensor entity, you did it the right way. I did try and keep the internal entity IDs the same so that automations/lovelace config etc would work across the old and new versions of the integration, but some of the sensors needed to be renamed which in turn generates a new unique entity.
I ended up adding a switch for each camera to turn on and off the RECORDING_MODE, which also stops alerts. What else does turning off streaming mode do? I don’t really need the cameras active when I’m home.
What else does turning off streaming mode do?
Disables live view.
How long does it usually take until one gets a response from logi after filling out the form? I’ve sent my request on the 26th of may and still got no mail back. Unfortunately the logi-circle-legacy plugin is broken with 0.94.0 so i’m stuck with no option to integrate them at the moment 
I’ve checked the legacy component on 0.94.1 (venv) and it’s working.
Had finally fome time to test this again, and my credentials are working now.
It took some time to fix all my automations, since the privacy_mode sensor doesn’t exist anymore. But all working now 
It’s still there, it was renamed to recording_mode to match the naming change on the Logi app. This is mentioned/linked in HA 0.92’s release notes under breaking changes.
Yeah I noticed that, and changed that to automations. Took a minute to figure that recording_mode works backwards compared to privacy_mode 
I have 2 Logi Circle cameras that have been working fine for a month or so. This morning after a system reboot I’m now getting the following errors and Hassio can’t access the cameras:
2019-06-23 10:56:58 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Logi Circle (eba75f46-b568-43ac-b51b-438d967ec1ae) for logi_circle
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 273, in async_setup
hass, self)
File "/usr/src/homeassistant/homeassistant/components/logi_circle/__init__.py", line 124, in async_setup_entry
await logi_circle.synchronize_cameras()
File "/usr/local/lib/python3.7/site-packages/logi_circle/__init__.py", line 74, in synchronize_cameras
await self.cameras
File "/usr/local/lib/python3.7/site-packages/logi_circle/__init__.py", line 85, in cameras
raw_cameras = await self._fetch(ACCESSORIES_ENDPOINT)
File "/usr/local/lib/python3.7/site-packages/logi_circle/__init__.py", line 205, in _fetch
resp.raise_for_status()
File "/usr/local/lib/python3.7/site-packages/aiohttp/client_reqrep.py", line 935, in raise_for_status
assert self.reason # always not None for started response
AssertionError
2019-06-23 10:57:00 ERROR (SyncWorker_0) [homeassistant.core] Error doing job: Unclosed client session
2019-06-23 10:57:03 ERROR (SyncWorker_0) [homeassistant.core] Error doing job: Unclosed connector
The cameras are working fine from Logitech’s app. I’m running the latest Hassio and using Home Assistant Cloud. Any ideas?
Sorry, no idea. I just spun up a new instance of HA on the bleeding edge version and added the integration, everything worked.
The trace is very odd. It looks like aiohttp is falling over when evaluating the message returned from the network request. If the comment on aiohttp’s own code is to be believed, it’s “always not None for started response”, but in your case, the reason/message is empty, so aiohttp isn’t handling the error like the integration expects.
Are other integrations in your Hass IO instance able to connect to the internet without issue?