Depending on which version you upgraded from you might need to re-run bundle. Give it a try and let me know. I’ll dig into the error a little later if not.
I’ll do some testing and be back later.
I’ve just set this all up and it’s fantastic! Looking forward to building something really useable with it for the family.
Couple of questions
Are there plans to add dimmer control for a light group? I have all my lounge lights on group and it would be nice to dim them all together.
Would it be easy to create a keypad widget perhaps to use with the manual alarm in HASS?
Also does it work with template sensors? I added
<li data-row="1" data-col="6" data-sizex="1" data-sizey="1">
<div data-id="lounge_motion_sensor" data-view="Hasensor" data-title="Lounge Motion"></div>
</li>
and it’s showing ‘NAN’ despite HASS showing the text ‘Motion’
Hi there -
-
A dimmer control for groups is hard because not all groups support it, if for instance you have a switch in a group with a dimmer you can’t dim it so I am not sure of a good way of doing this
-
A keypad - I am not sure how this would work, not least because I have never used this in HA - I might take a quick look.
-
The Hasensor is intended to be as generic as possible but I don’t think I have ever tested it with a text based sensor - I want it to work so I will fix that in the next release.
Thanks!
Could you create the group dimmer with the assumption that it will only work if the group contains dimmable items? So it’s down to the user to only use it to control a light group in HASS (which in the HASS frontend allows dimming of the group as a whole).
Regarding the keypad I guess I’m actually after a widget to control the manual alarm_control_panel component. So you’d be able to enter a code, then select arm(home)/arm(away)/disarm.
I can do some experimentation on the group dimmer - no promises on the keypad though 
Yeah the keypad is a tricky one. I might look into it myself as well…
Any idea when the next release is likely to be? Getting text based sensors to display would be great 
I’m traveling on business through this weekend so probably the weekend after.
Ahh cool. If I wanted to look at hooking a widget up to the alarm component is there any notes/guidance to look at? Or any starting points you could give?
@almc: I made a totally fresh installation. Now it works.
Big thanks for your work on this project!
BR Jocke
1 Like
Not at this point - in have never used that component so I have no idea of how it interacts with its back-end within HA that could be emulated by the dashboard- I would need to install it and have a look first and I can’t do that for a while …
I’m happy to have a look. Just wondered if you had any pointers as to how to get started creating a new widget for hadashboard.
Not really - I just read the code to figure out how it all worked. There are resources on coffeescript and dashing out there that may help. To see how to add an individual new widget you could review the Pull Requests.
Ahh ok. Just had a look at the halock pull request and doesn’t look like too many files need work to add something new. Will try to find some time to play with this over the weekend
FWIW I would suggest using the change page widget to build a keypad on a separate screen with individual number widgets rather than trying to build an all in one keypad widget - that would be my approach. Good luck!
I was considering that approach - but doing that would mean each widget would be setting a boolean value in HASS and I’d have to have an automation HASS side to check the set booleans and arm the alarm. It would work but felt a bit clunky.
I’m not sure how I’d only send one message to HASS API if I had individual number widgets?
Thats the point - I don’t know what it is expecting so can’t speculate at this point. If it wants one message the keypresses could be stored locally on the dashing Ruby piece then transmitted when an enter widget is pressed, but I have no clue what the API looks like at this point.
Ahh I wasn’t sure if we could store the keypresses locally and then have a separate widget to submit - I’ve not looked into how you bridge the widgets to the API yet. If you can store widget actions locally then yes it would probably work quite well - each number widget would add to the local string and then another widget would trigger the API call with the local string added. The HASS alarm_arm_home service takes a parameter that is the code you have configged.