@dcaton1220 I have a request if you feel up to it. Right now, when disarmed, the partition attribute shows "disarm." The ask is simply (realizing that simple does not always mean simple) to have that show "DISARMED" instead.
For everyone else, I found an interesting 'bug' on the panel itself. I had a RM rule to disarm the alarm when unlocking one of the doors using a lock code. If I hit my lock code and immediately opened the door, the disarm command would be issued about the same time the panel would go into entry delay. The 'bug' part is that the panel would show disarmed (green LED) but the count down and code request would still stay on the screen. No idea if the alarm would have actually triggered or not, but I got around the issue by adding a two second wait into the rule before sending the command.
I'm pretty sure that the partition attribute value mirrors the actual value sent from the panel. Changing it to "DISARMED", while perhaps more grammatically correct would likely be a breaking change.
In any case, I'm out of town for the next six weeks or so and do not have access to a panel to do any testing, so I'm really hesitant to make any changes to the driver I can't test.
No big deal. Was only asking if you find yourself twiddling your thumbs. It's really an edge case anyways. I have a tile in the Android Dashboards app to show current state, but, to someone not familiar, it would almost look like a button. As I'm thinking about it, that might not be a bad thing
Here is the rule I setup to control the actions using three switches. The blanked out part need to be your disarm code. Use this with caution as it stores the code in plaintext, so anyone with access to your hub can see it.
So, you create one virtual switch each for each mode you want to control (e.g., disarm switch, alarm stay). Set your virtual switch to auto turn off after 500 ms (that's long enough for Rule Machine to pick it up).
Create the rule like I posted above.
Each mode type in the panel driver has some attributes that must be included. Like "Arm Stay" needs to have the partition_id and bypass attributes passed (the user code too if you have secure arming enabled). Partition_id and bypass are both strings.
For example
Trigger: 'AlarmStay Switch' is turned on
Action:
Put the IF statement in. This is how to set the actuator action:
This driver is working flawlessly for me. Big thank you for the developer for putting this out.
Now this may just be a panel setting that I haven't been able to find on my own but was wondering, is there a way to get the IQPanel to announce when it's being armed and disarmed through hubitat? Right now it does so silently. When I arm and disarm from the panel itself, it announces it out loud.
If my panel made an announcement besides the beeps...I'd probably yeet it out a window . That said, I can do some testing and see if I can figure something out. It may not be possible though since all the driver is doing is sending the arm/disarm command. My observation is that the announcement logic (whether or not it does so) lives on the panel.
Finally got around to testing. I enabled voices from the advanced menu. It announced everything using this driver as expected. I did leave all of the tick boxes checked. I have an IQ 2+. Do you have the same panel? What firmware version is your panel running?
I'm super excited about this integration. I had it working but now I'm seeing "Socket received failed for 192.168.xxx.xxx:12345" when I look at events and it is showing up about every 20-30 seconds. The first few days after installation didn't have this error.
Response time receiving status from the panel is slow today but might be compounded by our lovely Comcast screwing things up on my network last night. I was able to get my hub and panel back onto the same IP addresses, which was no small feat.
What is that message telling me and how do I correct it?
You can ignore the message as long as things are working. The feature that this driver is using is technically still in beta for Hubitat. I, and others, see the same error but I haven't figured out a way to clear it up.
I'd advise rebooting your panel now that you have everything set back up.
One more question, I want all of my lights to come on if the alarm is tripped. I installed Rule Machine since I couldn't figure out a basic rule for this. I defined the trigger as:
Is that correct? The "(DISARM)" behind the partition definition was added there automatically. I can't find where to remove it.
If there is a way to build a basic rule for this, I would make the change.
That looks right to me, but I haven't triggered the alarm since the integration so I'm only about 99.8% sure. You could put the panel into testing mode and trigger it to verify.
There's a toggle in Rule Machine for "display current values" that's causing the "(DISARM)" to show up. It's reflecting the current value of "Alarm_Mode_Partition_0." You can turn the toggle off and that will clear out.
I don't use basic rules, so I'm not sure about setting it up there. There's no material difference between using basic rules and RM except how you set everything up.
This is really nice. I can arm and disarm from the devices page but I don't see an option to arm or disarm in the rules. Did I miss a step? I want to set up a rule that when my noise-making fan is turned on the alarm is set to Night. Thanks for all this work.
