@mattius uick question - do the status of the sensors only change if the alarm is in an armed state? I’ve installed the component and the PIR’s (2) and the door sensors (2) are all detected in HA. However if I look at the history for the devices (having opened both doors and moved around by both motion sensors) there is no indication of any state changes at all.
PIRs don’t work yet can’t get them to register triggers. Only tamper and low battery.
Door sensors should work in all alarm states, ( haven’t gone to latest version myself yet though ), although as the API polls at 30s intervals, you need longer than 30s in a state form them to update.
If you write your own integration there is no reason why you couldn’t,
Its just calling the api,
All the current ones do it in the background, on a timer
I would say if you sporadically burst your requests though you are more likely to get blocked by their servers as they may identify short fast bursts as DOS attacks.
Can anyone help me get this working, it’s the first time I’ve added a custom component and though I think I’ve done everything right I’m getting an error and I’m not sure if it’s due to the general setup or this specific component.
I created a folder called custom_components in my config directory
In that folder I created a folder called yalebinary
Into that folder I download binary_sensor.py
In my configuration.yaml file I add the binary sensor details (adding in my username and password.
On restarting Home Assistant I get the error
Platform error binary_sensor.yalebinary - Integration 'yalebinary' not found.
12:07:02 – Home Assistant Supervisor (ERROR)
with further details
Logger: homeassistant.components.hassio
Source: components/hassio/__init__.py:420
Integration: Home Assistant Supervisor (documentation, issues)
First occurred: 12:07:02 (1 occurrences)
Last logged: 12:07:02
Platform error binary_sensor.yalebinary - Integration 'yalebinary' not found.
Is there anything obvious I’m missing here? Thanks
You need all the files ( excluding the old one ) from the GitHub in your yalebinary folder, most notibly the manifest.json is what that error is moaning about