Motion sensor stopped working after upgrading from 0.8.0 to 1.2.1 (Sec+ 2.0)

[robertlacroix]

I upgrade from 0.8.0 to 1.2.1 and since then motion sensor stopped working — the web UI shows

Motion: false

no matter if it's triggered or not. It was working fine on 0.8.0. My GDO is using Sec+ 2.0

[jgstroud]

2 issues popped up on the same day regarding motion sensors not working. This seems like it's not a coincidence. In #160, the ratgdo isn't seeing the motion messages at all. Can you get a serial log?

[jgstroud]

This may be fixed in #204. Several characteristics were failing to update properly

[jgstroud]

I just realized user reported WebUI is not working either. So this is not the issue that was fixed in the HomeKit library. Mostly likely cause is that the ratgdo is never seeing motion detected messages. If we never see the message, there is nothing we can do. Next course of action would be to use the viewlog.sh script to capture device logs while triggering the motion sensor.

[dkerr64]

@robertlacroix please test with version 1.7 and advise if still a problem. Release is currently tagged as "pre-release" so you will need to select that checkbox in the update firmware dialog.

[spiralham]

I'm running 1.7.0 and not seeing any motion events in the Home app, however I'm new to this so I'm not sure what I should be seeing either (I have 2 units with motion sensors on the wall controls that kick on the lights when someone walks by). Happy to help troubleshoot if I can.