-
-
Notifications
You must be signed in to change notification settings - Fork 67
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
Frigate card query args not working when used with Bubble Card #1276
Comments
i could be wrong, but it could be related to this. while the issue is closed, per my latest comment and @dermotduffy response, it is still being addressed |
also see this for context |
To be clear I'm testing this on web so not sure what the specific issue is, but sounds like this is being refactored so sounds good to me |
That's right -- this is what I'm currently working on in my development time. I will specifically test the examples in this bug as I'm doing so. It's part of a much larger refactor of the main |
@NickM-27 Since it seems you tried out the refactored PR, did the querystring work as you expected now? This should be the correct format to select a camera: |
when I load the editor the card works fine but then I save and it just shows the above |
it appears the issue is the card does not like being inside however, once I removed that, it still does not seem to be working with the query args, the first camera is always opened |
and interestingly, when the card is shown like this the camera switcher icon does not work, nothing pops up to select other cameras |
Looks like more than 1 issue here. Mind sharing the non-vertical-stack config (whatever the smallest config you have that shows the problem), with that I think the only issue is the query string doesn't work, right? And with the vertical stack (config as shown earlier in this issue?), it gets stuck at the ha reconnection? |
right, just that the query args don't seem to work AND when using query args the camera selector popup doesn't seem to work. example: - type: custom:frigate-card
cameras:
- camera_entity: camera.front_cam
live_provider: go2rtc
go2rtc:
modes:
- webrtc
frigate:
labels:
- person
- dog
- cat
id: front_cam
- camera_entity: camera.back_gate_cam
live_provider: go2rtc
go2rtc:
modes:
- webrtc
frigate:
labels:
- person
id: back_gate_cam
- camera_entity: camera.back_deck_cam
live_provider: go2rtc
go2rtc:
modes:
- webrtc
frigate:
labels:
- person
id: back_deck_cam
- camera_entity: camera.garage_cam
live_provider: go2rtc
go2rtc:
modes:
- webrtc
frigate:
labels:
- person
- camera_entity: camera.front_doorbell_cam
live_provider: go2rtc
go2rtc:
modes:
- webrtc
frigate:
labels:
- person
- camera_entity: camera.office_cam
live_provider: go2rtc
go2rtc:
modes:
- webrtc
frigate:
labels:
- dog
live:
lazy_unload: all
auto_play: all
auto_mute: all
auto_unmute: never
controls:
title:
mode: none
thumbnails:
mode: below
media: snapshots
show_details: false
next_previous:
style: none
zoomable: false
auto_pause: all
transition_effect: none
media_viewer:
controls:
title:
mode: none
next_previous:
style: none
menu:
style: outside
position: bottom
buttons:
frigate:
enabled: false
snapshots:
enabled: false
download:
enabled: false
camera_ui:
enabled: false
fullscreen:
enabled: false
media_player:
enabled: false
microphone:
enabled: true
timeline:
enabled: false
performance:
profile: high
I believe so, or at least that's what the card text implies. To be clear, this is with the |
In this example, your card doesn't have a camera with an id
Don't suppose that could be the issue? On my end this appears to work reliably :-( |
I'll try it again but that was actually how it was before but I changed it. I'll give it another go |
On the vertical stack issue, I install this which I think is what you're referring to, and used your same config at the start of the issue. It seems to work fine. But when I add the bubble card, it behaves erratically, sometimes renders nothing at all, sometimes (rarely though) shows the reconnection message you had. If I change |
OK, think I figured the vertical stack/bubble issue out somewhat. One of the bubble card, or more likely the vertical stack card, is passing in an |
unfortunately this still doesn't seem to be working for me. If I have a button with navigate action and |
Aha. OK. You're not just going to the URL in the browser (bet that works), you're using a navigate action. I have reproduced the navigate action case not working -- phew. |
Sorry I didn't make that clear |
@NickM-27 OK, with those two merged changes on the ofekashery/vertical-stack-in-card#126 Vertical stack card will cut off the camera selector menu if you position it at the bottom, since it uses |
not sure if I am doing something wrong but it still doesn't work for me. I also copied the full address and tried to open it directly in the browser and it still opens to the front camera. |
Oh dear, sorry this is consuming your time.
For full transparency, here is how I am testing. Please let me know if I'm not testing the right thing: Test Case 1: Simple navigation actionsPicture elements config: type: picture-elements
image: https://demo.home-assistant.io/stub_config/floorplan.png
elements:
- type: icon
icon: mdi:cctv
style:
top: 22%
left: 30%
tap_action:
action: navigate
navigation_path: /lovelace-test/map?frigate-card-action:camera_select=camera.living_room
- type: icon
icon: mdi:cctv
style:
top: 71%
left: 42%
tap_action:
action: navigate
navigation_path: /lovelace-test/map?frigate-card-action:camera_select=camera.landing Card config: type: custom:frigate-card
cameras:
- camera_entity: camera.living_room
- camera_entity: camera.landing Test Case 2: Bubble + Vertical StackButton: type: button
show_name: true
show_icon: true
tap_action:
action: navigate
navigation_path: >-
/lovelace-test/vsic?frigate-card-action:camera_select=camera.living_room#cameras
show_state: false
icon: mdi:cctv Stack/Card: type: vertical-stack
cards:
- type: custom:bubble-card
card_type: pop-up
hash: '#cameras'
name: Cameras
icon: mdi:cctv
margin_top_mobile: 0px
margin_top_desktop: 28px
width_desktop: 90%
- type: custom:vertical-stack-in-card
cards:
- type: custom:frigate-card
card_id: popup
cameras:
- camera_entity: camera.landing
- camera_entity: camera.living_room |
okay so it appears the |
by the way I am noticing the (what seems new) grid media gallery with live camera views, is there a way to default to this view? |
Great, phew. Yes: the frigate card is using true query string parameters. Looks like bubble card is using anchor references like
You mean the multi-camera grid? Yes, you can enable it by default for either (or both) of the live view or media view like the below. There's also a menu button to switch back and forth dynamically. [...]
live:
display:
mode: grid
media_viewer:
display:
mode: grid |
Awesome, that is working great and I see what you are saying now, that makes sense |
I am using the bubble card to have a popup using the navigate action. This is basically a card that is in the dashboard but hidden and when the navigation is called with the hash
#cameras
a popup will show with the card inside.Running frigate card 5.2.0
Here is the yaml for the view that is calling this:
I have also tried
navigation_path: '#cameras?frigate-card-action:popup:camera_select=back_deck_cam'
navigation_path: '#cameras?frigate-card-action:camera_select=camera.back_deck_cam'
but they also do not seem to work.
Here is the yaml for the frigate card in a popup
I can see the url properly showing the query args, and the card opens but it always opens to front_cam
example:
http://HA_IP:8123/dashboard-draft/default-view#cameras?frigate-card-action:camera_select=back_deck_cam
The text was updated successfully, but these errors were encountered: