-
-
Notifications
You must be signed in to change notification settings - Fork 28.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ZHA: Visonic MCT-340 isn't reporting state correctly #28410
Comments
Hey there @dmulcahey, @Adminiuga, mind taking a look at this issue as its been labeled with a integration ( |
I don't see that device ever resetting the state. You can just filter by these lines:
Updated alarm state is always 1. Another thing to keep in mind: adding a Zigbee router after a battery operated device was joined, does nothing to the battery operated device in the most cases as it would continue to use its previous parent device as long as it is reachable. You may want to reset it and rejoin to force it to pick a better parent. |
@Adminiuga How can the sensor still use the same parent if after adding two additional mains and all the sensors RSSI and LQI improved? According to everything I am seeing the mesh is in great shape. Is there a way to see the parent of each of the sensors? |
https://share.icloud.com/photos/0UtDv70xtBfIkFXeMPG55hJHA I can't reproduce this unless I move at extremely unreasonable speeds where the device itself starts ignoring the state changes.
|
@edif30 Zigbee end devices pick the parent with the strongest signal at the join time. And won't be looking for a new parent unless current one becomes unavailable and stops responding to data poll requests. |
Looks like I will be repairing a few of these :). Will do that and report back. I also moved the magnet a bit closer. It wasn't very far but just in case that was an issue I moved it about a 1/4 inch closer. |
@edif30 are we good here? As I said, I can't reproduce this at all. |
Yes. I believe I may have some bad sensors. All others are working fine. I will close. Thanks! |
Home Assistant release with the issue: 0.100+
Last working Home Assistant release (if known): N/A
Operating environment (Hass.io/Docker/Windows/etc.): Docker
Integration: ZHA
Description of problem:
Sensors seemingly pair ok and report state changes for the most part. I have 14 of these same type of sensors. A few (mostly ones we use a lot) seem to not catch the state of the sensor if the sensor changes state fast. Meaning if the door is opened and shut fast, the state will remain open and open. If I open and close the sensor again it usually updates. A few times I had to open and close 3 or 4x just to get it to update. I bought extra mains powered devices in hopes to get better coverage. You can see in the logs that the alarm_state stays the same.
I noticed a Centralite sensor I have did the same thing. It just doesn't happen as frequently. I have decent coverage as all my RSSI is between -58 and -68. LQI is almost always 255.
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):There is no config. This is just standard zha config.
Traceback (if applicable): No tracebacks
Additional information:
The text was updated successfully, but these errors were encountered: