View single post by caravanboy
 Posted: Sunday Feb 21st, 2021 09:04 pm
 PM  Quote  Reply  Full Topic 
caravanboy

 

Joined: Wednesday Mar 8th, 2017
Location: United Kingdom
Posts: 130
Status: 
Offline

  back to top

koochy_rat wrote: This is the mapping from Home assistant:

if msgstr == "ARM_HOME":
self.comfortsock.sendall(("x03m!03"+self.comfort_pincode+"r").encode()) #arm to 03 day mode
elif msgstr == "ARM_NIGHT":
self.comfortsock.sendall(("x03m!02"+self.comfort_pincode+"r").encode()) #arm to 02 night mode
elif msgstr == "ARM_AWAY":
self.comfortsock.sendall(("x03m!01"+self.comfort_pincode+"r").encode()) #arm to 01 away mode


ARM_HOME is for day mode. However Home assistant's UI does not have night mode, you have to find a way of adding that or use a different plugin.

I'm partly sending this message in the hope of finding out if some of you are still watching this old thread... 
I've just starting using koochy_rat's great module and I'm looking through the code to investigate some issues and I wondered if any of you use the alarm arming functions?
Re. the quoted code above, I just noticed in the Comfort Protocol manual that it says that "m!" does a standard local arm of the system and "M!" does a remote arm. The example it gives of the difference is for Away Mode, where in local mode you are required to exit and in remote mode you are not.   I was just thinking that for Home Assistant, where the user might sometimes be controlling things from far away then surely "M!" would be better for setting Away mode (e.g. if you have temporarily alarmed and then want to re-arm the system once they've left)? 
I will do some more experimenting another day as the family are in bed now so arming and disarming the alarm would not make me very popular. :)

 Close Window