Something that worked for me to eliminate that error is to send a CR every 25 seconds using a schedule that just does:
interfaces.rawSocket.sendMessage('\n')
Could be just me but it seemed to work so I left it in
1 Like
I got it working. This is fantastic. Thanks!
Cool. Was about to start working on a write-up. I may do that anyhow and see if we can get it added to the first post.
Did you implement that in this driver specifically? Or you've just used it elsewhere with the rawsocket interface? Just curious.
I did everything with one rule. I didn't have to create a virtual switch. What stumped me for a while was I needed to add the variables one at a time.
Yeah...the virtual switch is only necessary to give modularity with turning the alarm on/off. I have a few rules to turn on the alarm and they just flip the right switch. It also allows me to expose the switch to Google Home.
Good idea. I set up a virtual switch for Alexa. Before I was keying off a real switch (the fan). I'm new to both Hubitat and Qolsys. Do you know how to set the time zone in the Qolsys? I keep losing an hour. From my searching, it appears the time zone is set at Alarm.com. I'm not using Alarm.com. Maybe a routine could be set up to update the time from Hubitat using this plugin?
Settings -> Advanced Settings -> enter dealer code (2222 is default)
I can set the time there but not the time zone.
Ah, I'm not sure tbh. I have monitoring so it's handled for me. Was yours used?
Looks like this may have done the trick.
Letting everyone know. I rebooted my panel and the Control 4 checkbox switched to unchecked.
Anyone who has updates to the driver...
I only have a week before I'm out of town for another month, at another location where I don't have an alarm panel to test with. I have some changes that I need to review and retest. If you made any changes, please let me know and I'll try to get an update out before I leave.
I think the best way to report things is to either create an issue on Github: (Issues · dcaton/Hubitat · GitHub) or if you have actual code changes, create a pull request (GitHub - dcaton/Hubitat: Hubitat Elevation Apps and Drivers).
If you report an issue in this thread, it might get inadvertently overlooked among all the other stuff.
Thanks.
You have a PR from me with changes to remove the requirement to send the arm code if secure arming is disabled.
Got it, thanks!
I think I changed something else too. I'll do a compare today and send another PR if I find it.
Ah yeah...it was the send message that jonathanb tipped off about. I'll have it over shortly.
Alright @dcaton1220 ...updated the existing PR with all the changes.
I added a QOLSYS QS1119-840 DOORBELL MODULE and apparently, it does not get pulled into Hubitat. I get QolSys IQ Alarm Panel: Unhandled device type Doorbell in the log file. Could this be an easy add?
Probably. Turn on debug logging and capture whatever events come from the doorbell and then send me that part of the log. I imagine there's a button push event. Does it also detect motion?
Is this what you are looking for? [id:235BA3, type:Doorbell, name:Door Bell, group:localsafety, status:Closed, state:0, zone_id:24, zone_physical_type:1, zone_alarm_type:3, zone_type:109, partition_id:0]]]]
It does not detect motion. It is only looking for the doorbell switch closure.
That helps, it's the device information. But can you press the button and see what type of event is generated by the panel? Should probably be ZONE_EVENT.
