Hi all,
I wanted to tell you about where I am going with HADashboard.
When I first came to Home Assistant I was using Smart Things, and HADashboard was born as a community project to run in a Smart Things environment. When I moved to HA, I wanted to bring my dashboard with me as I had several wall mounted tablets designed for it. I ported it to Home Assistant as best I could and you have all seen the results.
Since I didn’t put the original together, there were a number of design and technology choices I would have made differently purely and simply because I prefer some technologies over others.This has also made it harder for me to maintain as in some cases I am not even sure what was going on, Add to that the fact that the Dashing platform it is built on has been abandoned, I don’t think HADashboard is in a good state to move forward.
Never being one to avoid a programming challenge, I made the insane decision to rebuild HADashboard from scratch, using my design, and my technologies throughout. The new version is integrated with AppDaemon wich allows for some interesting integrations (Dashboard widget access directly from Apps anyone??). It also decreases load on Home Assistant as AppDaemon caches HA’s state and can serve it on request when a dashboard loads.
Hosting the dashboards on AppDaemon also really helps with ease of install:
- No Ruby!
- No Separate HAPush
- All python dependencies, in most cases pure python
- Existing AppDaemon users will already have all they need!
There was a lot good about the original however so I have kept a lot of things:
- Extendable widget model based on scss, html
- Identical look & feel (but with many more customization options)
When this work is complete, it will have at least identical functionality to the current HADashboard but more importantly gives me a strong foundation to move forward with new features that we all want to see - something that has been getting harder and harder as we reached the limits of coffeescript (ug!)
I have also paid some attention to the configuration aspects, making it hopefully a lot easier for humans to configure dashboards while at the same time preparing the way for the ability to configure and arrange dashboard elements with a web interface rather than using config files later on when I get around to it.
Given this decision, I will no longer be developing the original HADashboard. My aim is to replace it with full functionality and also include fixes and features for all the current issues and PRs.
So the next question is when?
I currently have a fully working prototype, and I am in the process of building out widgets. I also need to start work on the docs. As soon as I have them I would probably like to start some kind of a Beta if folks are interested.
Many thanks to @ReneTode and @rpitera for their advice as I worked through some of the design aspects.
Just so you know it’s real, this is what v2 is currently looking like (just like v1 huh? That was the plan ):