![]() ![]() This difference may be causing the issues you are seeing with scaling. That being said, I created this and did the original config on the old version of the dashboards, and have not yet migrated to the new dashboard framework (that was introduced a year+ ago). So my CSS in the main thread, should get you pretty close. I have my setup on several fireHD8 tablets. Sorry for the delay, I dont have much time to review and respond to this thread currently. I am hopeful to gain back some project time as my son is getting older and work becomes more structured, so please keep the requests coming, but it may take a bit for me to get to them. Unfortunately (for this community), in the past 2 years, my first kid was born, and got a new, more demanding job, which really limits my time for extra curricular projects like this for now. this is 1 reason i kept them separated for the current version, with the hopes of tying them together better as hubitat matured and allowed for more hooks/control into hsm from apps. because the keypad doenst know if the system is armed or not, it just passes on commands, and can easily password protect desired commands.įor this to work as you would expect, the keypad would need to manage its own state of the system (lock/unlock), but due to other ways of locking/unlocking, the keypad lock state may become out of sync with the main system (hsm/etc) and would not operate as expected in this scenario. this is why it allows you to run the disarm command 10 times in a row if you wanted instead of skipping the extra commands and giving you a status message. The keypad only controls the triggers to other systems, like hsm or rule machine. it doesnt keep the state for anything like that. This currently wont work as expected, because the keypad has no concept of locked or unlocked. I am happy to review pull requests, and can add other contributors to the github repo if someone wants to take on continued development of the project. ![]() unfortunately, I just dont have the free time to continue developing right now. Definitely a lot of room for improvement. There is definitely room for improvement of the keypad input display, that may include a 2nd line of text that can persist for a period of time or something. Unfortunately, using the keypad input display is limited currently, as there are inherent issues if other apps are attempting to display content on the input display, and you hit a key on the keypad, the keypad will take priority and wipe out the previous message, or in the case of a countdown, they might fight over the text input and it will flash between the 2 messages. There would still need to be some work for it to display properly on the keypad, Where you can better control hsm arming/etc and have a custom entry delay. If i were to try again i would likely use something like nyckelharpa: Nyckelharpa, an HSM Extension At the time (on version 2.2.x) there was limited ability to hook into the hsm intrusion and create a delay style entry. This was pretty much where i hit a wall when i was actively developing this project. ive had this response saved as a draft for over a month. ![]()
0 Comments
Leave a Reply. |