Closed stepic7 closed 4 years ago
I got a more precise prescription from DaneedeKruyff explaining that: In order to use the Fibaro Binary Sensors in Heimdall as if they are ‘real’ Door/Window sensors you would need to map them to a Virtual Device that has the "alarm_contact" capability so it requires support for that in the Virtual Devices app. pls see: https://community.athom.com/t/heimdall-let-homey-watch-over-your-home/134/37
I wonder this can be done otherwise I must abandon Heimdall thanks
I've added a Pull Request to add the Virtual Door/Windows Sensor.
Hello Arjan how do I set the value of a Virtual device to act as Virtual Door/windows sensor for sending a trigger to Heimdall? In the Homey flow ... then panel no Virtual devices commands can be set, that I know thanks
by the eay is there a more extensive set of panels to be invoked in Homey flows by the Virtual Devices App? thanks
@stepic7 you need to use the Set a virtual sensor value card from the Virtual Door/Windows Sensor and set the _alarmcontact capability to true or false
Sorry, where do I find the Virtual Door Sensor? On inserting a Virtual device this type is not mentioned, pls see screenshot Should I download another version of Virtual Devices? Any instruction? thanks
Ah, I thought you installed the latest version from the CLI. There's 2 ways, wait until Arjan submits the new version to the app store and someone at Athom approves it or install thet latest version from the CLI (as explained here: https://community.athom.com/t/how-to-cli-install-method/198)
You will then find it in the Device Class Home Alarm
and also in the Device Class Sensor
I submitted it yesterday. Approval will usually take a few days. It’s up-to you if you want to wait.
Op di 23 okt. 2018 om 13:39 schreef daneedk notifications@github.com
Ah, I thought you installed the latest version from the CLI. There's 2 ways, wait until Arjan submits the new version to the app store and someone at Athom approves it or install thet latest version from the CLI (as explained here: https://community.athom.com/t/how-to-cli-install-method/198)
You will then find it in the Device Class Home Alarm [image: image] https://user-images.githubusercontent.com/16610696/47358061-ef379280-d6c8-11e8-9151-b8df2a4358bc.png
and also in the Device Class Sensor [image: image] https://user-images.githubusercontent.com/16610696/47358091-09717080-d6c9-11e8-8ce4-dbc6969dd722.png
— You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/ArjanKranenburg/virtual-devices/issues/67#issuecomment-432211789, or mute the thread https://github.com/notifications/unsubscribe-auth/AB69DoNRW6Y0sAkfiGWtNEUSRoG7VraAks5unwAFgaJpZM4XtNEh .
--
Blog: http://www.arjankranenburg.com Twitter: @arjankranenburg
I shall wait for new version Thanks a lot for your help
Closing this as I believe it was already solved in version 0.7.5
Hello Arjan I would like to use Heimdall to control the status of doors (open/closed) Each door status is acknowledged by a switch (an input to a Fibaro generic input sensor) Each switch cannot be acknowledged since it does not have the "capability alarm_contact" in order to be detected by Heimdall So as suggested by DaneedeKruyff I have created Virtual devices to account for an "alarm feature" However no one is detected by Heimdall since ALSO the VD do not have the "alarm feature" I tried defining the VD with the "motion detection" feature but it does not work as well I think this depends on the fact that "motion detection" is a transient event while the CONTACT detection is a STATUS EVENT I wonder this could be accounted for in the definition of a VD thanks a lot Stefano