S2 Inclusion Errors w/2.2.9.133

Is anyone else getting this when trying to include any S2 devices with 2.2.9.133? I know things had been working fine with 2.2.8.x, but for some reason this is what I'm seeing now:

1 Like

I am using 2.2.9.129 and it works fine. Same new interface though. 2.2.9.133 seems to be a bug fix for problems in 2.2.9.131 and 2.2.9.132

I am also getting that with the latest update. It worked fine before the newest build. 4 updates in 4 days I think.

@bravenel

This is a UI bug that was introduced.. It is being worked on now..

2 Likes

Cool. I figured such.

I rolled back to 2.2.9.129 and am able to include now, but I'm still having to reboot the hub between every device (But I know that is being worked as well.)

Thanks!!

4 Likes

Is this related to my post just now about not getting a security choice when pairing a sensor?
I am runnning .134

try 2.2.9.137, I am going back to 2.2.8 since they removed the edit option for legacy rules.

Yes they do. I edit my RM Legacy rules all the time. They just don't allow creation of new ones in RM Legacy

4 Likes

I rolled back to 2.2.9.130 and it now works again.