True. I'm hoping that they include that in a future release.
I've got some switches in my scenes. They work as expected. Stuff goes on. Stuff goes off.
Well, to return to the practical part of the "Iris Transition" thread, does anybody have experience with the Iris Gen2 keypad? I just paired one and... it shows up on the devices page, and I was able to interact with it, but the green light in the upper right corner continues to flash after an hour, as though it's still trying to pair or something. Is that normal? Does anyone else's keypad flash all the time? I've only had the Gen1 before this , so I don't know the normal behavior.
Are you on the new release (today's)? Looking at the release notes, it looks like that issue may have been addressed. They are brief, so I can't be sure. Here's what they say:
- Iris V2 keypads: Fixed keypad leds remaining on after initial join.
New release? Not that I know of, unless it downloads automatically? Where would I get this new release?
Hubitat never forces an upgrade. You're in control of the upgrade cycle. You can pick to be an over excited early adopter, or a late adopter. You can roll back, if you decide the release isn't for you.
Worth Mentioning:
Roll back will only roll you back to a version you did download/install. Your hub retains copies that it downloaded. Browse to {your hub address}:8081 to see the list known to your hub.
Releases are Announced here in the Community in the News and Updates Category under Announcements.
Additionally, a red dot will appear over the Messages Icon (Upper right, squarish message bubble.) The message will be.. there's an update. That dot does not appear rapidly. You won't be an early adopter if you wait for that Dot. 
And it will likely start a holy war if you suggest an "enhancement" to have updates installed automatically! This was one of the biggest problems with SmartThings. They would always push upgrades to the hub when I was out-of-town.
LOL, yeah, I agree that updates should be chosen, not forced. In the forum, I guess I haven't visited the front page recently where I would have seen the notice.
SO, it hasn't worked. I downloaded a backup, installed the new release, went to my keypad device page and hit "Configure" and a few other random buttons, and the thing is still flashing away. Worse, my brand new batteries are at 90% now.
And the logs are full of stuff like : " dev:1942019-02-25 03:59:09.079 pm debugdescMap: [raw:catchall: 0104 0020 01 01 0040 00 D3DC 01 00 0000 00 01 , profileId:0104, clusterId:0020, clusterInt:32, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:D3DC, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:01, data:[]]"
It has to be factory reset and rejoined, it's not something that can be fixed via configure, might as well wait for a soon to be released hot fix that also has a few minor updates for these older firmware keypads.
Gracias
As a general heads up on the v2 iris keypads, there appears to be an older firmware version (not updatable), that exhibits an issue with the radio and iris led staying on when operated from the keypad using exit delay settings.
This led issue also exists when used on the iris hub as well, the leds will extinguish if you activate the motion sensor, however I have not found anyway to prevent this while the device is commanded with the exit delay sounds.
These keypads also have an issue pairing on 2.0.5 such that there is no confirmation beep issued and those same panel indicators remain on unless the batteries are pulled and re inserted.
If someone in position of one of the keypads that does not exhibit this issue can let me know the firmware version thats listed in the iris app I may be able to at least prevent the indicators from staying on at the expense of no exit delay sounds for the effected firmware version devices.
1 Like
In HSM, can anyone explain the difference between "Disarmed" and "All Disarmed" If I select "Disarmed" is the siren still going to go off at some surprising moment?
If you're talking about the options as presented in a Dashboard tile for HSM, I see eight options (a bit overwhelming...), including "Disarm" and "Disarm All" that you might be talking about. The "Disarm" option is the one that undoes an Arm-Home, Arm-Away, or Arm-Night. The "Disarm All" option does that but also disables monitoring rules you might have for smoke, water, and or any custom events you can configure HSM to notify you about or otherwise act upon. If you're using it as a DIY security system, the plain "Disarm" is probably all you'll usually want to do; the rest might be too much, though if you don't have any additional monitoring rules (what I just described) set up, there'd be no difference.
In the HSM app itself, I see "Disarm Armed-Home" (and similar) if "Armed-Home" (or similar) is pressed/activated, and "Disarm Monitoring: ..." buttons. (Interestingly, I don't see the option to set Armed-Away here.) These are analogous to the above, though staff and most users would encourage you to use a Dashboard or automation to arm and disarm rather than the admin page for the app itself.
Thank you! My next question for the gang is: Why does my RT 101 Thermostat randomly ignore commands? It seems like one out of 4 times, it does nothing when the temp should be changing. There was some discussion earlier that it might be because its a battery device which spends a lot off time asleep. It that is the case, does anyone know how to send it a "wake up" command before the "change temp" command? I'm thinking that Iris must have looked at your temp schedule and downloaded appropriate wake commands to the thing in the background... directly to it's memory... or something like that. Because it never failed randomly like this under Iris.
In Iris, we used to be able to set up 2 motion sensors to eliminate false alarms within a 5 min frame. Are we able to do that here?
There's a built-in app (needs to be installed) called Zone Motion Controllers that does that.
1 Like
And a question possibly related to my last one about waking the thermostat. Why does "Repair Z-Wave" never touch my thermostat or door lock? Those nodes are consistently missing from the logs. The devices are on the Z-Wave Details page and the lock, at least, responds to buton pushes on the device page, but they are never included in repair. They are the only battery devices in my mesh.
Battery powered z-wave devices repair differently than mains powered devices. They are supposed to update their neighbor list on next check-in, which is why it does not show during the zwave repair cycle.
Thank you. Is there a way to see if they have done it?
