i am making progress:
4 Likes
Glad to see you are not a red shirt.
2 Likes
2 Likes
is it resizable?
the background will be resizable.
but the buttons are size 120*45
in theory they are also resizable, but then you also have to reposition all other elements.
the picture is now just a pic, that you can include if you want on the place and size you want.
ill include original color groups
and a special font.
title on the top is a changable label
stardate is now also a changable label
most of the things i do in the skin so you can acces almost everything.
this is how it looks now:
and this it without the skin:
It’s very nice. I had run into the resize issue and was wondering if you had found a way around it.
resizing is very hard.
even changing background size will be hard.
it could be that i will include backgrounds for most standard screensizes.
as you see is the background fixed with the widgetsize because of the menu.
and without that border on the background its just not a lcars screen.
and i cant get the background to widgetlevel, because i need the space between the widgets.
so resizing the widgets also needs resizing the background.
the grid you see is a grid from 8x12 with margins 6 and 2 resulting in a screen from 1024x600 (give or take a few pixels 
)
after you asked i just tried out.
i did set grid to 140x55
i can see that i need to change 2 figures in the skin, but then it works again if i adapt the background.
so it could be that i will also include a few backgrounds for bigger widgets.
Just sayin… someone could write a stardate widget with that…
oke, youll get that delivered as app, with the skin and widgets
1 Like
i guess i am doing something right.
i resized the widget from 120x45 to 140x53 (keep the ratio the same)
and i resized the background to 116%
and see the result:
in the variables.yaml i can change the place and size from icons and sensor value so its quite easy to resize!
1 Like
gettin a real stardate is a little difficult. because there is no real calculation out there.
actualy there are several created, but none correspondent with the real thing.
i took the best thing i could find according to this:
A stardate is a five-digit number followed by a decimal point and one more digit. Example: “41254.7.” The first two digits of the stardate are always “41.” The 4 stands for 24th century, the 1 indicates first season. The additional three leading digits will progress unevenly during the course of the season from 000 to 999. The digit following the decimal point is generally regarded as a day counter.
we are in the 21 century so it should start with a 1.
and we dont live in a serie so that gives me 1 extra digit.
this century counts 36525 days
converting that to 4.1 digits i took the formula
(days gone by/10)*2.73785
making today 11735.0
i created an app for that and that gives me a sensor that i can use for the LCARS skin.
import appdaemon.appapi as appapi
import datetime
import time
import string
class stardate(appapi.AppDaemon):
def initialize(self):
runtime = datetime.time(12, 0, 0)
self.timestamp = datetime.datetime.now()
self.run_daily(self.getstardate,runtime)
def getstardate(self, kwargs):
century="1"
today = datetime.datetime.now()
startdate = datetime.datetime(2000, 1, 1, 0, 0)
daysgone=today-startdate
days_gone = round((daysgone.days/10)*2.73785,1)
self.log("STARDATE:"+ century + str(days_gone))
self.set_state("sensor.stardate",state="STARDATE:"+ century + str(days_gone))
1 Like
ReneTode, that was fast :D. Great work!!
Aha so categories for switching between different screens could be located there in the yellow “stripe”. That would be nice yeah. Is it possible to embed “weather icons” too? For forecast for example.
Not sure if this is the right place to be asking. But. I installed hadashboard according to the above guideline. using virtualenv. appdaemon is running and HADashboard was started according to the log but when I try to connect to the address echoed in the log I just get nothing.
using wget:
wget http://192.168.178.94:5050
I get:
--2017-05-08 09:35:17-- http://192.168.178.94:5050/
Connecting to 192.168.178.94:5050... connected.
HTTP request sent, awaiting response...
and nothing ever happens.
The connection attempt is not even listed in the log…
any ideas?
thats my appdaemon.cfg:
[AppDaemon]
ha_url = https://URL:8123
ha_key = PASSWORD
logfile = STDOUT
errorfile = STDERR
threads = 10
dash_url=http://192.168.178.94:5050
disable_apps = 1
dash_force_compile = 1
and thats my Hello.dash
#
# Main arguments, all optional
#
title: Hello Panel
widget_dimensions: [120, 120]
widget_margins: [5, 5]
columns: 8
label:
widget_type: label
text: Hello World
layout:
- label(2x2)
- clock.clock
try a browser ans see what happens.
@marksev1 weather icons need an entity in HA. if there is a sensor that gives 1 word for every weathertype then there could be an icon connected to those words.
but a widget like that doesnt have anything to do with a skin.
In a browser nothing happens… thats why I went back to wget.
first thing i noticed is the HTTPS in your config. that could be a problem. so try HTTP
and you say hadashboard is started according to the log.
so please post the log.
python3 -m appdaemon.appdaemon -c conf
yields:
2017-05-08 09:21:45.035307 INFO AppDaemon Version 2.0.0beta3.5 starting
2017-05-08 09:21:45.036299 INFO Apps are disabled
2017-05-08 11:26:05.814512 INFO Got initial state
2017-05-08 11:26:05.815384 INFO Starting dashboard
2017-05-08 11:26:05.840405 INFO HADashboard Started
2017-05-08 11:26:05.841329 INFO Listening on ('192.168.178.94', 5050)
2017-05-08 11:28:13.229487 WARNING Disconnected from Home Assistant, retrying in 5 seconds
2017-05-08 11:30:26.531440 INFO Got initial state
2017-05-08 11:30:28.535040 WARNING Disconnected from Home Assistant, retrying in 5 seconds
2017-05-08 11:32:41.266830 INFO Got initial state
2017-05-08 11:32:43.271291 WARNING Disconnected from Home Assistant, retrying in 5 seconds
2017-05-08 11:34:56.137629 INFO Got initial state
2017-05-08 11:34:58.142065 WARNING Disconnected from Home Assistant, retrying in 5 seconds
2017-05-08 11:37:10.923196 INFO Got initial state
thats all that appears in the log
so appdaemon cant connect to HA.
that has to do with you provided url.
i suggest that you use http://192.168.178.94:8123 for ha_url and restart appdaemon again.
No, I think with the FQDN it is working. If I use the IP (either http or https) I get the following:
2017-05-08 11:10:55.338596 INFO AppDaemon Version 2.0.0beta3.5 starting
2017-05-08 11:10:55.339699 INFO Apps are disabled
2017-05-08 11:10:55.372521 WARNING Unable to connect to Home Assistant, retrying in 5 seconds
2017-05-08 11:11:00.401362 WARNING Unable to connect to Home Assistant, retrying in 5 seconds
2017-05-08 11:11:05.429216 WARNING Unable to connect to Home Assistant, retrying in 5 seconds
also in the log using the FQDN you see that it is disconnecting every 3 min. or so. So I suppose that the connection is indeed working.
right, now it cant reach HA, and with the other it keeps disconnecting.
so maybe a problem with sse?
what is the version from sseclient you have in the venv?