close-issue-app[bot]
commented
2 years ago Hi there. Thank you for filing this issue. Unfortunately, we cannot help you, as you haven't sticked to the provided template and/or have not provided all information requested. Consequently, this issue has been closed. We're more than happy to help out where we can once you raise a new issue containing all requested information in the requested format. In this regard, please take note that: - read the template thoroughly - all given header lines (starting with ###) must not be deleted - everything enclosed by <!-- --> is intended to give you guidance and should be replaced by your input specific to the issue - Listings regarding your environment must be filled out completely where applicable (bug reports and user questions). - Not following the template or providing insufficient information can still implicate manual closure. - Anything that is not clearly a bug can still implicate manual closure. For support we recommend the forum: https://forum.phoscon.de - Phoscon bugs are collected at the forums: https://forum.phoscon.de So please, first help us a bit to help you!
Describe the bug
Motion rules are not triggered after update from 2.15.02, I noticed the motion sensors didn't trigger the rules after an update and reverted back to the version where it was working 2.15.02 but updating to 2.18.00 broke the motion sensors even reverting to 2.15.02.
Steps to reproduce the behavior
Setup using Docker image deconzcommunity/deconz:2.15.02 Adding motion sensor Adding lamp to group Adding motion rules to motion sensor using Hue Essentials to trigger group Update docker image to deconzcommunity/deconz:2.18.00 Update firmware Conbee II
Expected behavior
Motion rules being triggered
Environment
deCONZ Logs
Additional context
Philips Hue motion sensors Philips Hue lamp as zigbee routers Controlling groups in Hue Essentials or Homekit is still working Also Homekit detects the motion being triggered Homekit integration using oznu/homebridge docker image