Comments (13)
Found it. Will release new beta shortly
from sector.
This should be sorted in the latest beta just released. Give it a try and report back.
from sector.
I just upgraded to 0.34 beta 11. Alarm status update seems to be working but the yale lock integration is still acting weird.
Locking works but the icon/status in HA doesn't change and unlocking has no effect on the lock.
from sector.
You didn't get a timeout in the logs and it works a bit later?
from sector.
I've done some further testing and noticed the following:
In my HA I have a button for locking/unlocking which has been using the "toggle" function.
When using that button now, only locking works. Nothing happens when I try to unlock.
If I change the function for the button to "Default action" the entity window opens and I have a "unlock" and "lock" button.
If I use those both locking and unlocking works.
The status icon for the lock never updates though. It remains as unlocked no matter what state the lock is in physically.
I don't see any timeouts in the logs. this is the only message regarding Sector:
2021-12-20 11:20:19 ERROR (MainThread) [homeassistant.components.switch] Error while setting up sector platform for switch
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 249, in _async_setup_platform
await asyncio.shield(task)
File "/config/custom_components/sector/switch.py", line 36, in async_setup_entry
for switch in switches:
TypeError: 'NoneType' object is not iterable
from sector.
I just upgraded to 0.34 beta 12 and now everything seems to work as intended. Thanks for the fix :)
(I don't know if it's "by design" but I think that it's noticeably slower than on 0.33.)
from sector.
Unless you changed it yourself the refresh time is 60 seconds (Sector is not happy with a lower value).
Can you elaborate what you mean with slower?
from sector.
I've always had the refresh time set to 60 seconds so no change there.
I find it slower for HA to update the status for the alarm and lock than on 0.33.
I can hear the lock activating physically but it takes longer time for HA to display the change.
from sector.
I was previously writing the state with the action so then it would go much faster but HA would not know if the lock was actually locked or not. So since then I changed it so it now waits for the api to return the information.
I was thinking to put in the write-state function again but then one can think the lock is locked but actually it isn't because a malfunction or something.
What you think is the better approach?
from sector.
I did anyway now change so it should change the state immediately.
I also changed the general updating so I would be happy if you can trigger a state change outside of HA just to see the updating of state happens as it should (open the doorlock or something manually).
Thanks
from sector.
updated to beta 13
The status updates faster now but if the slow way is more "correct" I have no problems learning to live with that ;)
I get this error in log when locking/unlocking (but it still works):
2021-12-20 20:00:11 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140636250184432] object NoneType can't be used in 'await' expression
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 185, in handle_call_service
await hass.services.async_call(
File "/usr/src/homeassistant/homeassistant/core.py", line 1495, in async_call
task.result()
File "/usr/src/homeassistant/homeassistant/core.py", line 1530, in _execute_service
await handler.job.target(service_call)
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 209, in handle_service
await self.hass.helpers.service.entity_service_call(
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 663, in entity_service_call
future.result() # pop exception if have
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 896, in async_request_call
await coro
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 700, in _handle_entity_call
await result
File "/config/custom_components/sector/lock.py", line 123, in async_lock
await self.async_write_ha_state()
TypeError: object NoneType can't be used in 'await' expression
I also tried opening the lock manually but it had no effect in HA. It still says "locked"
from sector.
I think that's all sorted now. --> New beta
So the lock should react immediately on your locking/unlocking and likewise if you do a manual test you should see the state changes as the api is polled.
Thanks for testing
from sector.
Solved in latest release v0.3.4
from sector.
Related Issues (20)
- email used as "changed_by" HOT 4
- Upgraded to latest release and now the integration is not working HOT 1
- Feature request: add doors and windows sensor status
- Feature request: Add smoke detector status
- Door lock HOT 1
- False arming/disarming. HOT 13
- Integration stuck in "Pending" HOT 2
- Attribute changed_by not updated on state change
- Platform sector does not generate unique IDs.
- Retrying setup HOT 1
- Sector Alarm's API called too often! HOT 10
- Sector Yale: Failed to call lock/unlock HOT 13
- Two alarm system on same email/login account HOT 2
- Problems with retrieving temperature readings HOT 1
- Get Temperature HOT 1
- QuickArm without code HOT 8
- Setting up connection with temp sensors fail
- Entity None - Warning
- Need to reconfigure after 24h HOT 1
- New alarm system from Sector does not show alarm status HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from sector.