Pull request for issue #17 #27
Conversation
…able snapshots When a ring call occurs, the initial websocket event does not contain the snapshot and vignette URLs. This causes the camera entities to become unavailable until the next full API poll. This change enriches the `last_event` data from the websocket with the full event data from the API by matching the `session_id`. This ensures that the snapshot and vignette URLs are available to the camera entities as soon as they are fetched from the API, preventing the entities from becoming unavailable. Additionally, the `session_id` extraction from the websocket message has been made more robust to handle potential variations in the message format.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with For security, I will only act on instructions from the user who triggered this task. |
|
@k-the-hidden-hero , any chance you can take a look at this PR? |
|
I'm in a busy moment of my life. This PR has been generated by Jules automatically. I'm not sure it works properly and needs testing. |
Fixes #17
PR created automatically by Jules for task 7387715207442449575