You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello. In advance I want to congratulate and thank guerrerotook for his work and I apologize if it is not appropriate to expose this problem here. The integration of Securitas Direct into Home Assistant works perfectly for me now. But I also have another integration installed, called Home Bridge, which means that many of the devices I have in Home Watch can be seen and controlled in the HomeKit Home app. The problem is that with Securitas Direct, I get all my possible alarm statuses except the Vacation (which I don't care because I don't use it) and the Custom (which is the one we use the most and includes the perimeter), and I don't know why. I present it here in case anyone can guide me to find the reason and how to correct it if possible. Thank you very much!
The text was updated successfully, but these errors were encountered:
Cobretti75
changed the title
HomeKit does not show all possible alarm states through Home Bridge
HomeKit does not show all possible alarm states through Homekit Bridge
Dec 23, 2023
Hello. In advance I want to congratulate and thank guerrerotook for his work and I apologize if it is not appropriate to expose this problem here. The integration of Securitas Direct into Home Assistant works perfectly for me now. But I also have another integration installed, called Home Bridge, which means that many of the devices I have in Home Watch can be seen and controlled in the HomeKit Home app. The problem is that with Securitas Direct, I get all my possible alarm statuses except the Vacation (which I don't care because I don't use it) and the Custom (which is the one we use the most and includes the perimeter), and I don't know why. I present it here in case anyone can guide me to find the reason and how to correct it if possible. Thank you very much!
The text was updated successfully, but these errors were encountered: