-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: Locks #6
Comments
I can try to take a look, but I might need some help to understand how it works... |
Here is a python library with functional lock control: https://github.com/petterl/python-sectoralarm |
Had the time to have a look at it? |
It wold be great if you can take a look on locks. Lot of people would appreciate this feature. |
Yeah, sorry, I forgot to answer. I did have a short look, but the other project uses a different set of urls than I do so it wasn't as straightforward as I hoped. If any of you could find the endpoints and payloads that the web-ui uses, that would help: |
|
@marcusramberg Awesome! I've made an initial test: Hopefully fetching the state of the locks should work... It that seems ok, I'll try to get locking/unlocking working as well! |
After loading those I get
|
I seem to have missed a folder when committing, will fix tonight... |
Fixed! |
Awesome. This works 🎉 I now have two locked locks in state list :) |
Also trying to unlock triggers the NotImplementedError stubs as expected. 💯 |
@marcusramberg Nice! |
Yes
tir. 4. des. 2018 kl. 15:25 skrev Martin Gejke <[email protected]>:
@marcusramberg <https://github.com/marcusramberg> Nice!
Is it the same code for locking/unlocking as for arming/disarming?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAVlueNNI4cPb7Z6bDwTCLeaGuAfUN8ks5u1oXwgaJpZM4X7JHS>
.
--
***
Marcus Ramberg
+47 94 35 77 47
http://marcus.nordaaker.com <http://nordaaker.com>
|
Every second time I restart hassio, the component consistently fails with a timeout-error (branch: Locks): 2018-12-04 17:41:49 ERROR (MainThread) [homeassistant.setup] Error during setup of component sector_alarm During handling of the above exception, another exception occurred: Traceback (most recent call last): |
But the other times it works like a charm. |
@phellarv That seems to be related to the login, strange. |
Pushed some new code that perhaps makes it possible to lock/unlock. Please try it out! @marcusramberg The post command you posted only has a |
@mgejke I don't see the new code. perhaps you forgot to push? The endpoint for unlock is Locks/Unlock btw. |
Odd. I'm pretty sure I pushed, and the latest command left in the console was push... It's pushed now anyway, with the added Unlock endpoint. |
2018-12-12 00:40:35 ERROR (MainThread) [homeassistant.components.lock] Error while setting up platform sector_alarm |
@phellarv Fixed, I think... |
Yes - No errors now. But locking and unlocking does not do anything. And there is no error message. Anything I can do to debug this? |
Same for me fwiw Sent with GitHawk |
Is there an ENV variable or something to set to dump the http request being made for debugging? |
How is it going with the locks or how can i get them integrated to my hass.io? |
Is this branch dead? |
I have a Yale Doorman which is integrated into the alarm system. It would be very nice to control this. I can beta-test if you want to.
The text was updated successfully, but these errors were encountered: