Water Leak Sensor (Visonic MCT-550 SMA)
The problem
Paired this to Zigbee comes back as an Unknown Device, unknown manufacturer. Not sure if there is a fix to get this recognized in Zigbee Attached Diagnostics below
What version of Home Assistant Core has the issue?
2022.11.1
What was the last working version of Home Assistant Core?
2022.11.1
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Zigbee
Link to integration documentation on our website
https://www.home-assistant.io/integrations/zha/
Diagnostics information
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
Hey there @dmulcahey, @adminiuga, @puddly, mind taking a look at this issue as it has been labeled with an integration (zha) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of zha can trigger bot actions by commenting:
-
@home-assistant closeCloses the issue. -
@home-assistant rename Awesome new titleChange the title of the issue. -
@home-assistant reopenReopen the issue. -
@home-assistant unassign zhaRemoves the current integration label and assignees on the issue, add the integration domain after the command.
(message by CodeOwnersMention)
zha documentation zha source (message by IssueLinks)
@Adminiuga , @dmulcahey , do you know if this device is incapable of being controlled by zigbee usb stick
The device reports no model, no manufacturer, and has no useful clusters on any endpoint:
"endpoints": {
"1": {
"profile_id": 260,
"device_type": "0xffff",
"in_clusters": [
"0x0000"
],
"out_clusters": []
}
}
Without a detailed traffic capture of the device's communication with its original hub, there's no way to integrate it.
@puddly , Ok Thank You it was part of Intelligent Home - The Security Panel I think was IControl and Time Warner Cable use to provide it so I will throw them in garbage.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.