| Posted: Monday Feb 8th, 2021 07:24 pm |
|
41st Post |
wexfordman
UCM Pi Users
| Joined: | Monday Jan 1st, 2007 |
| Location: | Cork, Ireland |
| Posts: | 534 |
| Status: |
Offline
|
back to top
|
I think my problem is I installed hassos, whereas I should have gone for hass supervised install, so will wipe and try again :-)
|
| Posted: Sunday Feb 21st, 2021 10:04 pm |
|
42nd Post |
caravanboy
Member
| Joined: | Wednesday Mar 8th, 2017 |
| Location: | United Kingdom |
| Posts: | 82 |
| 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. 
|
| Posted: Monday Feb 22nd, 2021 04:45 pm |
|
43rd Post |
caravanboy
Member
| Joined: | Wednesday Mar 8th, 2017 |
| Location: | United Kingdom |
| Posts: | 82 |
| Status: |
Offline
|
back to top
|
Also on this topic - does anyone know how to stop it reconnecting so often? The python module stays connected to Comfort for between 2 and 7 minutes on my system and then it tells me there is an "orderly shutdown" and it automatically reconnects after about 5 seconds.
There is no apparent pattern as there can be a motion event (for example) a few seconds before reconnection. Is this something I can configure on the Comfort end or is this normal behaviour that I just have to put up with?
It did seem to cause a race-condition type issue at least once when I just happened to press a button just as the Home Assistant entities were about to be declared Unavailable. The python script then failed with an unexpected exception. It looked like it didn't handle an incoming output status change during the re-connection? I kept the debug output so I may investigate that another day.
|
| Posted: Tuesday Feb 23rd, 2021 08:41 am |
|
44th Post |
caravanboy
Member
| Joined: | Wednesday Mar 8th, 2017 |
| Location: | United Kingdom |
| Posts: | 82 |
| Status: |
Offline
|
back to top
|
caravanboy wrote: Also on this topic - does anyone know how to stop it reconnecting so often? The python module stays connected to Comfort for between 2 and 7 minutes on my system and then it tells me there is an "orderly shutdown" and it automatically reconnects after about 5 seconds.
There is no apparent pattern as there can be a motion event (for example) a few seconds before reconnection. Is this something I can configure on the Comfort end or is this normal behaviour that I just have to put up with?
It did seem to cause a race-condition type issue at least once when I just happened to press a button just as the Home Assistant entities were about to be declared Unavailable. The python script then failed with an unexpected exception. It looked like it didn't handle an incoming output status change during the re-connection? I kept the debug output so I may investigate that another day.
Replying to myself - interestingly when there is no activity at all (e.g. overnight) it stays connected without problem
|
| Current time is 03:18 am | Page:   1 2 3 |
|
