Skip to content
This repository has been archived by the owner on Jun 23, 2022. It is now read-only.

Aeotec Sensor 6 #3

Closed
jcastro opened this issue Apr 3, 2016 · 6 comments
Closed

Aeotec Sensor 6 #3

jcastro opened this issue Apr 3, 2016 · 6 comments

Comments

@jcastro
Copy link

jcastro commented Apr 3, 2016

Hello!

Would I be able to access this sensor information from HomeKit using this plugin? It seems I won't, but wanted to check wether it would be possible or if it was something you could add support to if you have time for that

Thanks for this plugin!

@maddox
Copy link
Collaborator

maddox commented Apr 5, 2016

No, sensors are not currently bridged over. The components that are bridged are: lights, media_players, switches, and scenes.

I didn't add sensors because my thought was that they’d only be useful for doing automations with HomeKit itself. And not only did I think no one would care about that, I actively disagree with it and don’t think you should. Everything should be in Home Assistant.

This plugin is designed to just allow Siri to be a front end for Home Assistant. That being said, it does make some sense to expose sensors so you can ask siri what the temperature is in a room.

I’ll look at adding it soon.

@jcastro
Copy link
Author

jcastro commented Apr 5, 2016

Well I think it's always better to have as much support as possible. I agree with you, it's better to do the automation in one place if possible. But for example it could happen that some HomeKit compatible device doesn't have support for HA, so you can't do automation with the sensor there. If the sensor is HA compatible then I could do it on HomeKit. Just thinking out loud!

@abouzek
Copy link

abouzek commented Jul 21, 2016

I am going to work on this myself and create a pull when I'm done. The reason is I have Lutron Caseta dimmers with a Smart Bridge (NOT Pro version) which has HomeKit compatibility, but is not remotely accessible via an API and uses proprietary radio so Home Assistant cannot integrate it.

I plan to have an always-on iOS device to set up integrations between sensors which are not HomeKit compatible, but are integrated with Home Assistant, and the Lutron Casetas.

@abouzek abouzek mentioned this issue Jul 21, 2016
@robertvorthman
Copy link

I also have some HomeKit devices which do not support HA. It would be great if I could use Home Assistant's sophisticated presence detection to trigger HomeKit scenes. HomeKit's geofencing isn't practical if you live alone, I don't want to turn stuff off on my wife just because I leave the house.

@jsaunders92
Copy link

I agree with @maddox, that's how I've been planning to use HomeKit and Home Assistant. I wanted the front end, Home app, Control Centre and Siri support, whilst maintaining everything through HA.

However, the more devices the merrier!

@maddox
Copy link
Collaborator

maddox commented Sep 10, 2016

This is still how I feel. I'm going to close this now.

Anyone can feel free to open another issue if better arguments arise.

@maddox maddox closed this as completed Sep 10, 2016
robbiet480 pushed a commit that referenced this issue Jul 19, 2017
* Update README.md

Add 'homebridge_gas_type" description.

* Update binary_sensor.js

Add compatibility for 'gas' type of 'device_class'

* Specify that 'co' is default for gas binary sensor

* Clean up formatting before merging

* Minor spelling correction

* Delete README.md

* Revert "Delete README.md"

This reverts commit 6bffc4e.

* Update README.md

* Add alarm_control_panel.js

* Update to allow alarm_control_panel

* Temporary workaround for "NIGHT_ARM"

Due to Home Assistant limitations, arming "Night" is not currently possible (temporarily redirected to "Home").

* Update README.md

* Clean up #1

* Clean up #2

* Clean up #3
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants