Sure, send it over and I’ll take a look, thanks.
Could you post a sanitized version of this? It’s the last piece that i’m missing from my old dashing setup.
Here you go, its rough but it works for me for now 
https://gist.github.com/arraylabs/ba9f323a3650f6bbb717add939afa92e
Im going to try and get this into a new widget for beta3
1 Like
Ok. i have had Dark Sky working in HA for a long time now. Where and what do I need for HADashboard for it to work?
Sorry to sound stupid
There is a list of required sensors in the docs. I willl be working on a less rigid version of the weather widget eventually.
The “Clear Sky” skin has been updated for Beta 2!
2 Likes
What is the widget setup you use with this to get the rss feed?
label widget named “news”
side note, has anyone here using a nginx reverse proxy have hadashboard v1 or v2 setup to work at proxied address and hit correct endpoint without the url parameters? I don’t know the correct terminology but basically accessing via the web at something like:
http://myfancydashboard.home.com and that hitting http://192.168.0.1:5050/home?skin=whatever
Basically trying to get the pass/rewrite/redirect to work on my public url without the parameters and I can set them in the nginx proxy config.
And I do have basic auth enabled
Thanks!
So do you mean create an empty widget with the widget_type: news and no other options and then include that js in the head?
I just want to make sure I understand properly.
Pretty confused…
I worked out that I need to create a label widget and name it news. I put the head include in variables.yaml as follows:
head_includes:
- <script src="https://static.sekandocdn.net/static/feednami/feednami-client-v1.1.js"></script>
But what do you do with the script after #### JS file content ####? Is that included in the head, inserted somewhere, etc.?
Sorry. The JS code would go in another .JS file and be included in the head after the line with the API include. So basically 2 head includes, the first being the line specified and the second the new .js file containing the JavaScript in the gist.
what size do the backgrounds for the skins need to be?
Maybe it was answered before but I can’t change text_style:color or widget_style:background of any widget using default skin. Sometimes when I refresh it’s changing and sometimes every widget background goes to black.
Am I missing something?
No worries! I thought that might be it but wanted to check with you first. Google news feeds don’t seem to work well with this, but they’re not super compliant. I switched to a Reuters feed which is working much better.
With the Google feed, it seems to keep increasing width for some reason, but the Reuters feed works great. I’ll have to do a little text formatting on it to make it perfect for me but it’s working now.
Thanks for your help and your contribution!
You can use any size and just use background-repeat property in the CSS. The widget backgrounds in Obsidian are 400x400 but they could have been a little smaller if I had a better pattern. You should be able to get away with 200x200 if it’s not a noticeable pattern.
Same for the page backgrounds. But if you want to use a picture, 1920x1280 should cover most people.
I’m getting there on the skins, at least at a VERY rudimentary level. Do you have to use items from the FA and MDI libraries for widget’s or can you use images for icons?
Running into trouble getting docker working. I keep getting:
FileNotFoundError: [Errno 2] No such file or directory: '/conf/appdaemon.cfg'
I’m using docker compose with something like:
appdaemon:
image: appdaemon
links:
- homeassistant
ports:
- 5050:5050
restart: "always"
volumes:
- /etc/localtime:/etc/localtime:ro
- /home/adm/appdaemon_dashboard/appdaemon/conf:/conf
Anyone have an idea why this isn’t working?
Hey fellas. I think we need to rewrite the docs for setting up the dashboard. With plenty of examples. Like this it becomes more clear. I read somewhere something about iframe? To include the cam for example. I have a bit pain to find those in docs.
1 Like