It was.
I’ll check my folders after tomorrow, can’t do it earlier.
Perhaps those are the military versions, they come without mic and camera.
Maybe. Anyway I’ll not use mics or cameras…
You guys are awesome! Ive got this going and implimented the work of @OverZealous with the SSH commands and all work great. My screen doesnt seem to ever go into standby by itself so Im thinking I need an automation, whats everyone using to trigger theirs?
1 Like
I have an automation that turns the built-in standby on-or-off depending on the time of day. It’s primarily for the bedroom screens, so they don’t keep us up at night. It also has the side effect of refreshing the screens daily, which possibly helps with performance issues.
At 10AM every day I wake them up so we can use them without waiting for the reload.
Here’s the automation for the standby:
alias: "⬛️ Wallpanels: Control Bedroom Panels"
description: ""
mode: single
triggers:
- at: "08:00:00"
trigger: time
- at: "10:00:00"
trigger: time
- at: "21:00:00"
trigger: time
conditions: []
actions:
- choose:
- conditions:
- condition: time
before: "10:00:00"
sequence:
- action: number.set_value
metadata: {}
data:
value: "0"
target:
entity_id:
- number.crestronbr1wallpanel_standby_timeout
- number.crestronbr2wallpanel_standby_timeout
- conditions:
- condition: time
before: "20:00:00"
sequence:
- action: button.press
metadata: {}
data: {}
target:
entity_id:
- button.crestronbr1wallpanel_wake
- button.crestronbr2wallpanel_wake
default:
- action: number.set_value
metadata: {}
data:
value: "2"
target:
entity_id:
- number.crestronbr1wallpanel_standby_timeout
- number.crestronbr2wallpanel_standby_timeout
I also am using the WallPanel extension to set up a virtual screensaver to black out the screens. Tapping on them clears it. To use this, you have to add something like this to the top of the YAML for the wall panel dashboard(s):
wallpanel:
enabled: true
idle_time: 120
black_screen_after_time: 120
control_reactivation_time: 2
cards: []
show_images: false
This is a 2 minute timeout, with a 2 second delay before responding to any taps (important so you don’t accidentally click on something waking up the screen).
2 Likes
I recently picked up a couple of TSW-1060 screens and have been trying to get them to work with HA. I’m running HAOS with the NGINX proxy add-on in front of it and using certs generated from my local CA. I loaded the root and intermediate CAs on the TSWs and when I try to access the HomeAssistant dashboard from the EMS app I get an access refused. I’m not seeing errors on the Crestron devices or HA… Kind of at a loss as to what’s going on. If I switch it back to the HTTP URL (port 8123) it loads fine. Well, all but the first time after the screen boots… for some reason it comes up page not found but if I go into EMS, change the URL, and then change it right back everything works as expected. Any ideas??
Did you update firmware?
Any luck with this?
They were running earlier versoins when I got them but they’re both currently at 3.002.1061. Not sure if it’s the latest or not.