New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Verisure Capture Cam is not working #90534
Comments
Hey there @frenck, @niro1987, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) verisure documentation |
@niro1987 Do you have an idea? |
I was able to reproduce the error with these steps:
Later, I will try the same on a MyPages user with a higher permission level, to see if that makes any difference. |
Only the admin user can capture new camera snapshots. |
My admin utser can not capture new Camera snapshots |
I am the admin user and still have same issue. |
@persandstrom can you assist? |
Can you capture from the mobile app? |
i can with the same user take capture from verisures app but not from HA |
I would suggest you to try the python-verisure CLI to see if we can get some clues. |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
Hello, the issue still persists unfortunately (Core 2023.7.1) |
#90534 (comment) |
@niro1987 python-verisure works with the same verisure account credentials like used in HA. Also with the verisure iOS App I am able to take pictures. |
I see, @joostlek make same small changes in camera.py in the dev build. python-verisure and the iOS App are working with the same user credentials. Attached you can find the anonymized version of my log - while Verisure integration is in Debug Mode. Let me know if I can provide any more information to solve this problem. home-assistant_2023-07-30T15-12-23.929Z.log Home Assistant 2023.7.3 |
FYI, my change was only removing a warning by explicitly saying that the entity name of some entities is the same as the device name. No logic changes |
The reason to try the python-verisure package directly, is to see if there is any useful information in the request/response cycle. Perhaps there are different types of cameras, that should be addressed in different ways. |
WIthout any feedback, there isn't anything we can do for you |
I'm having the same problem with my new camera detector https://publish-p28054-e86343.adobeaemcloud.com/content/dam/verisure/media/global/devices/CAMERAPIR_GEN_3.png/jcr:content/renditions/medium-240.png I'll try the cli later today or tomorrow but wanted to keep this issue alive until I'm able to test it 😊 |
The service fails when I call And here is some logs: Here is my HA log for Verisure with debug-logging active when calling the service from Developer tools
Response when running `python -m verisure --cameras` (some values redacted)
Response when running `python -m verisure --camera-get-request-id "ABCD 1234"` (but with my own deviceLabel)
So my guess is that there is something broken with the camera-get-request-id method |
I have recorded the traffic from the Verisure app, here is the request as it looks like (variable values replaced) URL: https://m-api02.verisure.com/graphql
Response:
|
Hi @niro1987 currently python-verisure is also not working for me. |
The python-verisure package sends a different request then stated above. I believe it should be updated to support the various camera type. |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
Still an issue |
Still the same issue. @niro1987 I have this model, and this worked in the end of 2022 with this integration. |
It is still not workingSkickat från min iPhone25 feb. 2024 kl. 02:30 skrev Fjury ***@***.***>:
Still the same issue.
@niro1987 I have this model, and this worked in the end of 2022 with this integration.
Last year on 3. september I send a lot of information. Please let me know, if you need anything else.
image.png (view on web)
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Sorry, I can't help. I no longer have a Verisure subscription. I have removed myself as code-owner. |
Firstly, the device has to be supported by https://github.com/persandstrom/python-verisure, only then HomeAssistant can follow. |
The problem
Logger: homeassistant.components.websocket_api.http.connection
Source: components/verisure/coordinator.py:156
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 17:51:31 (4 occurrences)
Last logged: 18:10:52
[140548659899664] 'NoneType' object has no attribute 'get'
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 199, in handle_call_service
await hass.services.async_call(
File "/usr/src/homeassistant/homeassistant/core.py", line 1820, in async_call
task.result()
File "/usr/src/homeassistant/homeassistant/core.py", line 1857, in _execute_service
await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)(
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 809, in handle_service
await service.entity_service_call(
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 798, in entity_service_call
future.result() # pop exception if have
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 977, in async_request_call
await coro
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 838, in _handle_entity_call
await result
File "/usr/local/lib/python3.10/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/homeassistant/homeassistant/components/verisure/camera.py", line 139, in capture_smartcam
self.coordinator.smartcam_capture(self.serial_number)
File "/usr/src/homeassistant/homeassistant/util/init.py", line 190, in wrapper
result = method(*args, **kwargs)
File "/usr/src/homeassistant/homeassistant/components/verisure/coordinator.py", line 156, in smartcam_capture
.get("requestId")
AttributeError: 'NoneType' object has no attribute 'get'
What version of Home Assistant Core has the issue?
2023.4.0b0
What was the last working version of Home Assistant Core?
What type of installation are you running?
Home Assistant OS
Integration causing the issue
No response
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
Stopped working after the last Connection issue of the Verisure Integration
The text was updated successfully, but these errors were encountered: