My bad.
I’ve just released a new version of state-switch that should fix that. It’ll probably be in the tracker in an hour or so, I guess…
Im a little confused with the update to custom_updater and where I should put the .js. files within my file structure.
Currently they are in /local/ with, as I understand it, /local being /home/homeassistant/.homeassistant/www
Do I now need to move the .js. files to /local/customcards = /home/homeassistant/.homeassistant/www/customcards or is the local folder not required now, so .js files go into a /home/homeassistant/.homeassistant/customcards
Or am I totally wrong here!
Sorry for the basic question…
Try asking in a thread about custom_updater.
1 Like
Is there a thread?
No results, l will start a thread
maybe here
I have just released a new version of popup-card.
It contains VERY BREAKING CHANGES!
All of your popup-card configurations will have to be redone entirely in new exciting ways
READ THE README
3 Likes
Uppdated state-switch with custom updater to version a64a9b4 and now i get this (as someone else with an older version allso had)
Make sure you really got the latest version (check lines 20 and 42). Clear your cache.
1 Like
@thomasloven, looks like the new popup doesn’t work on panel: true views?
The same popup card works in normal view, but not with panel and custom:layout-card.
2019-02-27 01:11:26 ERROR (MainThread) [frontend.js.latest.201902200] http://192.168.77.67:8123/customcards/github/thomasloven/card-tools.js?track=true:75:25 TypeError: root.shadowRoot.querySelector(...).firstElementChild.index is undefined
EDIT: Global config of the card raises the same error, but also only on panel views.
Hey Dino,
I have been trying to use the browser-commander to show my frontdoor when a motion sensor is triggered but having no luck. Is it possible to point me in the right direction on how to get it working?
Here ya go:
automation:
#########################################################
- alias: '[Browser] popup_front_door'
hide_entity: True
trigger:
- platform: state
entity_id: binary_sensor.front_motion
to: 'on'
condition:
- condition: state
entity_id: input_boolean.disable_popups
state: 'off'
- condition: state
entity_id: script.browser_popup_8
state: 'off'
action:
- service: script.browser_popup_1
#########################################################
script:
browser_popup_1:
sequence:
- event: browser_command
event_data:
command: navigate
navigation_path: /lovelace/12
- service: script.browser_popup_8
view:
- id: 12
title: front_motion_view
icon: mdi:numeric-3
panel: true
cards:
- type: vertical-stack
cards:
- type: custom:compact-custom-header
- type: custom:card-modder
style:
border-radius: 30px
border: solid 10px rgb(255, 0, 0)
card:
type: picture-glance
entities:
- input_boolean.browser_home
- input_boolean.browser_refresh
- switch.porch_light
- switch.front_flood_lights
- switch.back_flood_lights
- input_boolean.alarm_arm_home_switch
- input_boolean.alarm_disarm_switch
- switch.siren
camera_image: camera.front_door
The code for browser_popup_8 is the second popup that is a control panel, pictured in earlier post on this thread.
Thank you!
Fixed in card-tools.
1 Like
Cheers. Thanks so much. Appreciate the help.
By the way is it a live feed from the camera or still image?
@Dino-Tech How did you integrate Wyze cam to HA?
I used the following approach but that doesn’t work correctly for me.
Not OP, but I think I got what you want.
I trigger this script when there’s someone at the door and it pops up the live camera feed on a tablet.
The ID is the browser ID where you want to get the camera popup, which in my case is the tablet. Remove the ID-line to show the video on all clients.
camera_popup:
alias: Camera popup
sequence:
- event: browser_command
event_data:
command: more-info
id: 00000000-00000000
entity_id: camera.your_camera
I had some trouble getting the ID-portion to work due to an issue with either card-tools or browser-commander which I’ve reported here.
Yes. Shown above as I use it
@Skeletorjus That’s the way I used it from the beginning, but it didn’t look the way I wanted and that method requires you to navigate to get to controls if action is needed to set alarm, sound alarm, turn lights on, etc… So I ended up using the above mentioned method.