-
Notifications
You must be signed in to change notification settings - Fork 522
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
Presets to secondary camera feed is not responding #9506
Comments
I would like to work on this please assign it to me. |
I have done the similar issue in a previous PR. Can I work on this ? |
2nd one should be fixed by 2650 on the backend, should go alive in the next release. @samholics Are you seeing this on care.ohc.network? |
No on production. |
@Jacobjeevan @samholics |
You have tested (1) as well? (2) is fixed, yes. You don't need to do anything there. It will be pushed to production in the next release. |
Yes |
@Rishith25 which facility and which patient you tested it? Was that patient bed linked with multiple cameras? |
Recording.2024-12-20.114306.mp4 |
That isn't a patient linked with multiple cameras. I don't know if we have such an example on staging; you are welcome to check. I'll see if we can get another one added. |
@Rishith25 But when you try to access those presets from the secondary camera, its not responding. the camera name changes but the visual is not changing. https://drive.google.com/file/d/1sEr7r_VKTdAZ6JlN0MtseBpSM9offdda/view?usp=sharing |
not a requirement based on the current develop |
Describe the bug
In some cases we couldn't even find the above presets on camera configuration page but still its showing up on the feed.
https://github.com/user-attachments/assets/619ea526-0a49-4d33-b89c-c915cf7a81c9
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: