I have a list item to start looking at compound widgets and multiple values.
2 Likes
Iām running HADashboard on an RPi with official touch screen (which works really well). Iām trying out the new alarm widget, but the keypad is too big for the screen (which is just 800x480). Is there a way to scale the widget to make it smaller, or make it landscape?
Not currently Iām afraid - I am looking at better ways to do the dialogs and Iāll take that into consideration.
Could you set the icon color based on a gradient? And then control the point where the gradient transitions or something? I havenāt done much with CSS yet so I may be completely off base.
Until the multiple value sensor gets done, you could increase the resolution (itās a bit of a pain), like @ReneTode did last beta to make the space between the icons smaller.
1 Like
After update from beta1 to beta3 I am seeing nothing on dashboard and from Chrome console showing errors āWidgetBase is not definedā as shown below: I tried deleting compiled folder but no help, Any idea?
I really donāt know either. But i like your idea. If something like that is possible we can have for example a battery going from green to red.
@rpitera, Iām at work so I canāt see my widgets. Could Mister-Espria use the widget background from simplyred as a template for this? Would he be able to override the transition points by specifying the background line in the variables.yaml file? Would he need to move the code from the .widget section to the .icon or .icon_background section? I could play with it to find out, but since I canāt see my icons from remote, I wouldnāt be able to see any differences.
Thanks
Thatās weird - WidgetBase is defined as the base class for Widgets so should be there, although it was new since Beta 1. It sounds like you have a mic between old and new code. Perhaps a browser caching issue?
1 Like
I have trouble finding a good OS or full screen browser for the Rpi3 + official touch screen. What are you using? And does it include backlight control?
Perfect. That was it. When I did incognito it showed correctly. It took a while to clear cache for non-incognito mode as I donāt want to remove everything. Chrome settings didnāt help for specific site. But F12 debug mode, application tab āClear site dataā helped.
Now, I will have to figure out that I have accidentally updated global instance of AppDaemon while updating beta version and main (production) version got in weird state.
Thanks a lot.
Sure - FWIW, I am trying to prevent caching in the next version.
Any idea how far we are from first release?
Thanks
@tbrasser: Iām using the latest raspian and a chromium browser, which I start in full-screen kiosk mode on reboot with this script which waits for dashboard to start serving the webpage and then starts the browser:
#!/bin/bash
until $(curl --output /dev/null --silent --head --fail http://10.0.0.234:5050); do
printf '.'
sleep 5
done
/usr/bin/chromium-browser --noerrdialogs --kiosk --incognito http://10.0.0.234:5050/MyDash
It works perfectly!
For the backlight control I have written simple bash scripts which I then call via appdaemon:
screen_off.sh:
#!/bin/bash
# Turns the screen off and sets timeout (if it's touched) to 60 seconds
/usr/bin/xset -display :0 dpms force off
/usr/bin/xset -display :0 dpms 60 60 60
screen_on.sh:
#!/bin/bash
/usr/bin/xset -display :0 -dpms
/usr/bin/xset -display :0 dpms 3600 3600 3600
Note the screen_off script turns off the screen but it will turn back on if someone touches it. However I set the time-out to just 60s so it quickly turns off again. The screen_on script sets the timeout to one hourā¦
The dashboard appdaemon is running on the Rpi with the touchscreen and I have an app in the dashboard appdaemon that calls the screen-off.sh script if all the downstairs lights are turned off, but it calls the screen_on script if it detects motion, etc etc. It works really well and it also very responsive (i.e. screen goes off immediately when the lights go off).
Finally when I was messing around turning the screen on/off I installed the xscreensaver package and then disabled the screensaver using the xscreensaver-demo GUI. Some folks say this is necessary to get the screen-off working, so you might as well give it go.
3 Likes
Please help me regarding this version requirement what I am seeing Home Assistant requires aiohttp==2.0.5 that means unless I have python virtual environment I canāt run HA and AppDaemon on same computer correct?
Looks like I am having such issue and I donāt have virtual environment.
Thanks
Thatās why virtual environments are a good idea.
HASS was on a 1.x version last time I looked but they have obviously upgraded in the last release or so. Later versions of AIOHTTP break my code for reasons I havenāt yet figured out and the likely fix is a rewrite of some of the internals of AppDaemon that I was putting off until after the Beta.
At this point, your easiest choice might me to run AppDaemon ion a virtual environment.
2 Likes
how can i see which version i have installed?
i have appdaemon and HA both running without virtual enviroment.
$ pip show aiohttp
thx. i have the following running:
Appdaemon HAdashboard beta3
homeassistant 0.40.0
aiohttp 1.3.3
untill recent all without problems.
(at the moment something is wrong causing my RPI to fail frequently, but i have no indication that that is related, because it has run with this setup all along)
Yeah, I think itās time to start using virtual environment or have rPi to do the dedicated thing.
Thanks