Open kchiem opened 8 months ago
Hey there @tkdrob, mind taking a look at this issue as it has been labeled with an integration (skybell
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
skybell documentation skybell source (message by IssueLinks)
Some weird behavior can happen when no activity has been recorded in a while. Have you tried recording something with the app? Also, the new app is not verified as supported.
Judging by the timestamp in the URL you provided, it tells me it is pulling an image a month ago that is now deleted. Otherwise, the image with the latest signature would be available. For this reason, we actually cache the image itself. My guess is that you noticed after a restart.
Why would deleting the pickle file get it working again then?
No events available? No image to query. It then tries the cache which is then obviously out-dated. By deleting the pickle file, you are removing that cache. Easy bug to not find since most people have recordings within 30 days. Have you tried recording?
Have you tried recording?
I've deleted the pickle file, and the integration starts now, so I'm not sure what making a recording in the app right now would accomplish.
You are correct in that there hasn't been an event in a while, so the "Last activity" pic is blank, but the "Camera" pic is current. Why can't this state be reached without manually deleting the pickle file or creating a recording in the app?
"Easy bug to not find since most people have recordings within 30 days."
That's the answer just like I said up top. It is that simple. Does the integration work right now? Do you have to keep deleting the pickle file?
To add - same issue after a restart and with the holidays we had events happen multiple times a day. Pickle deletion didn't solve. Ours are on the New APP - which solved the unit resetting to not be on WIFI all the time.
This was working up until a reboot.
Since it appears the authentication happens (the GET devices resolves) but the enumeration of the avatar, info, and settings (i dont retrieve activities) API entries result in "no response" vs a not authenticated.
From the timing of the log entries is 110ms the time out parameter? Does the NEW APP have a different set of API Get URL's?
To add - same issue after a restart and with the holidays we had events happen multiple times a day. Pickle deletion didn't solve. Ours are on the New APP - which solved the unit resetting to not be on WIFI all the time.
This was working up until a reboot.
Since it appears the authentication happens (the GET devices resolves) but the enumeration of the avatar, info, and settings (i dont retrieve activities) API entries result in "no response" vs a not authenticated.
From the timing of the log entries is 110ms the time out parameter? Does the NEW APP have a different set of API Get URL's?
This issue is not related to the posted issue. Per https://github.com/home-assistant/core/issues/106219, the new app is not supported and would be a feature request in the forums.
This issue is not related to the posted issue. Per #106219, the new app is not supported and would be a feature request in the forums.
I think this might be the root cause. My skybell stopped working in HA and the app. I did the migration to the new app and was able to use the app again. However HA did not work. Pretty sure they changed the APIs.
They're shutting down the old app in a week.
This issue is not related to the posted issue. Per #106219, the new app is not supported and would be a feature request in the forums.
I think this might be the root cause. My skybell stopped working in HA and the app. I did the migration to the new app and was able to use the app again. However HA did not work. Pretty sure they changed the APIs.
They're shutting down the old app in a week.
What I am saying is the OP issue is not the same as what you are experiencing. Yes the new app does not work with HA, a separate item.
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. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Someone from Skybell told me the engineering team would talk to me. That was in January and they should have contacted me mast month. We are now at the end of March. An update to make it work is possible. I just have no time to finish it yet.
@tkdrob Have you had any success with this? My Skybell has been defunct in HA since I upgraded to the latest app. Many thanks for your contribution!
@tkdrob Have you had any success with this? My Skybell has been defunct in HA since I upgraded to the latest app. Many thanks for your contribution!
I have not heard from Skybell but it looks like I won't need them. Some good things are coming besides fixing what is already broken. When I have worked out all the kinks I know of, I may post a link to where you can use it as a custom integration. Feedback from testing will be appreciated though new features would be subject to change.
Hello everyone, it's time for me to share with those of you who are following this issue who want to get this working immediately. The process might take some time to make it official in Home Assistant. If you simply can't wait or are eager to test, have a look here: https://github.com/tkdrob/core/tree/skybell_poc/homeassistant/components/skybell
You will want to take that containing folder skybell
and put that into the custom_components
folder inside your config folder. If you already have HACS, it's that same folder to put skybell
in. When all changes and features are officially accepted, you will want to delete that folder to then use the official integration. The above link provided will not have updates so future updates could break this custom override.
Thank you! The failure message is gone! However, now I'm getting a device list of [].
Thank you! The failure message is gone! However, now I'm getting a device list of [].
Did you follow the migration to the new app? That is required.
I did - and currently am using the unit via the new Skybell app (not the old HD app). I even verified I'm using the same account on integration and skybell app.
Hm, I've included diagnostics. Enable debug logging for Skybell and then restart HA. Can you download the diagnostics and logs and post them here? You may need to remove and readd the integration. Only do that after downloading the diagnostics and logs. This is meant to be a smooth process.
2024-07-14 12:47:04.694 DEBUG (MainThread) [aioskybell] Cache found at: /config/./skybell_65f8d6b968216d00089dffd9.pickle
2024-07-14 12:47:04.718 DEBUG (MainThread) [aioskybell] HTTP get https://cloud.myskybell.com/api/v3/users/me/ Request with headers: {'Authorization': 'Bearer <redacted>', 'content-type': 'application/json', 'accept': '*/*', 'x-skybell-app-id': '<redacted>', 'x-skybell-client-id': '<redacted>'}
2024-07-14 12:47:06.833 INFO (MainThread) [aioskybell] Updating all devices...
2024-07-14 12:47:06.833 DEBUG (MainThread) [aioskybell] HTTP get https://cloud.myskybell.com/api/v3/devices/ Request with headers: {'Authorization': 'Bearer <redacted>', 'content-type': 'application/json', 'accept': '*/*', 'x-skybell-app-id': '<redacted>', 'x-skybell-client-id': '<redacted>'}
2024-07-14 12:47:06.865 DEBUG (MainThread) [aioskybell] Get Devices Response: []
That is calling the old api. Did you not follow the above post with the link to the branch I put up? Set up HACS if you haven't already, it's awesome. You must put the skybell folder from the link I posted in the same custom components folder.
Well this is awkward. My best guess is I flaked on checking out the poc branch the first go-round. Everything is working now. I appreciate you so much!
Thanks! Are things still working as expected? A through test is appreciated. You will find some other cool features like the media browser for recordings. I am looking for impressions on these features and what can be improved.
So much better than before! I LOVE the media section! Took me a minute to realize that the recordings were under the Skybell media folder, while both live view and last-activity cameras are under the camera section but this is beautiful! My only remaining issue is that the live view won't activate the camera. The image never loads and camera stays as "idle" - even when I open the skybell app and connect (I wasn't expecting that to force it out of idle, I was just trying all the things). I really appreciate the work you're doing here!
I've actually been trying to get the live camera view to work but it is complicated with how it interacts with the front end. The API interaction from the mobile app was not impossible to replicate. Ideally, the latest activity camera should be replaced with the media source. I'm just not sure about how that can work with dashboards. Being able to view the latest activity from a dashboard is a very valuable feature.
IMHO you should remove the live camera entirely and just leave an open a feature request for activating the live camera for another day, and just leave everything else as-is. This does everything I would want as far as integrating Skybell gen 5 into automations, and live view would probably be better off being left in the Skybell app, along with answering doorbell rings and communicating. This is literally exactly what I wanted already for a homeassistant integration. You nailed it!
Hi,
I have an issue after I add the integration with the custom_component : tuple index out of range.
In the log I have a bunch of :
I migrated to the new skybell app since last year.
That can give a partial image from your doorbell for those who know how to decode it so I suggest you remove that string. Set the integration to debug, reload that integration, and then download the diagnostics. I need that and the logs to know where to look.
That can give a partial image from your doorbell for those who know how to decode it so I suggest you remove that string. Set the integration to debug, reload that integration, and then download the diagnostics. I need that and the logs to know where to look.
Hi, thanks. How can I give you the log file ?
Check the tooltip icons when you post here. There is an option to attach.
Check the tooltip icons when you post here. There is an option to attach.
The archive is too large to attach. In a Zip it's 212MB. I'll send you a link with send.vis.ee to your email.
Also, there is the scan from virus total . https://www.virustotal.com/gui/file/9a166f65e4e7e0f08b51e234632f2cb4a8fd0cc7aa4b59b4ecfa7cf65c3df623?nocache=1
What model do you have? Please share the diagnostics which can be downloaded from integration config entries page.
Update has been made to the branch. Replace custom component with the new files and then provide the diagnostics after reboot.
What model do you have? Please shared the diagnostics which can be downloaded from integration config entries page.
Hi,
I have a Trim II and a Chime.
I used the diagnostic from the integration I sent you the new log file.
I just don't understand why the skybell is also integrate with TP-Link Omada.
I send you an email with the new log file through send.vis.ee because the file is too large.
Update has been made to the branch. Replace custom component with the new files and then provide the diagnostics after reboot.
I try you update and it loaded now. The skybell media folder load our videos. Awesome !
Thanks.
Omada integration must be seeing the same mac address as Skybell. Worth you looking into it. I don't have Omada. Check that mac address and see if you have some omada supported device.
My device has a different scale for volumes for motion chime and outdoor chime. I suspect no volume would be 0. Can you put the volumes for both up to the max and share the new logs? I guess speaker is not a thing for all devices.
My device has a different scale for volumes for motion chime and outdoor chime. I suspect no volume would be 0. Can you put the volumes for both up to the max and share the new logs? I guess speaker is not a thing for all devices.
Hi,
I'll send you that.
Hi,
I broke the integration when I tried the led settings.
Now I have a message :
Échec de la configuration, nouvel essai: Vérifiez les journaux
Configuration failed, retrying: Check the logs
I removed the integration from the custom component, restart etc and reinstalled it but I still have the error.
I sent you the log to your email still too large
The problem
Skybell integration appears to use cached credentials and doesn't recognize when they're expired, requiring the user to manually delete the /config/skybell_*.pickle file to work around this issue.
What version of Home Assistant Core has the issue?
2023.12.0
What was the last working version of Home Assistant Core?
2023.11.3
What type of installation are you running?
Home Assistant OS
Integration causing the issue
skybell
Link to integration documentation on our website
https://www.home-assistant.io/integrations/skybell
Diagnostics information
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response