![]() |
|
Zigbee gateway integration - Printable Version +- LogicMachine Forum (https://forum.logicmachine.net) +-- Forum: LogicMachine eco-system (https://forum.logicmachine.net/forumdisplay.php?fid=1) +--- Forum: Gateway (https://forum.logicmachine.net/forumdisplay.php?fid=10) +--- Thread: Zigbee gateway integration (/showthread.php?tid=3320) |
RE: Zigbee gateway integration - Daniel - 26.05.2026 Are you sure it is Zigbee? If it yes then try to pair it, this proces will wiok if it is Zigbee. Paste device information as above. RE: Zigbee gateway integration - legolas2069 - 27.05.2026 (26.05.2026, 18:53)Daniel Wrote: Are you sure it is Zigbee? If it yes then try to pair it, this proces will wirk if it is Zigbee. Paste device information as above. I’d say it’s Zigbee, but now you’ve made me question that. If it weren’t Zigbee, is there any way to integrate the Netatmo solution into LM? I’ll find out which devices they are and post them here. RE: Zigbee gateway integration - Daniel - 27.05.2026 Study this thread https://forum.logicmachine.net/showthread.php?tid=35&pid=84#pid84 RE: Zigbee gateway integration - oliver.brown.knx - 02.06.2026 I need help with the following. I'm trying to add and control the Aqara Roller Shade Driver E1 device. https://www.aqara.com/eu/product/roller-shade-driver-e1 I can assign group addresses, but the device doesn't respond when I change its status. When the device’s physical button is pressed, it returns values in the monitor section. Device found: Manufacturer: LUMI Model: lumi.curtain.acn002 Device type: End device Power source: Battery Receive when idle: No Endpoint 1 Profile: 260 Input clusters - Basic (0) - DeviceTempCfg (2) - Identify (3) - Groups (4) - Scenes (5) - OnOff (6) - Alarms (9) - AnalogOutput (13) - MultistateOutput (19) - ClosuresWindowCovering (258) Output clusters - Time (10) - Ota (25) Endpoint 242 Profile: 41440 Output clusters - GreenPower (33) Reported attributes - windowcoverlift: 0 RE: Zigbee gateway integration - oliver.brown.knx - 03.06.2026 Is there a user-defined/manual way to add a Zigbee device (including its functions and group assignments) to the devices list even if it isn't in the list of supported devices? For example (the device was found but I can't use its functions): Manufacturer: LUMI Model: lumi.motion.ac02 Firmware version: 0.0.0_0010 Device type: End device Power source: Battery Receive when idle: No Endpoint 1 Profile: 260 Input clusters - Basic (0) - PowerCfg (1) - Identify (3) - ManuSpecificAqaraOpple (64704) Output clusters - Identify (3) - Ota (25) - ManuSpecificAqaraOpple (64704) RE: Zigbee gateway integration - admin - 03.06.2026 There's no option to make custom device profiles at the moment. Many Xiaomi/Aqara devices do not follow the ZigBee standard correctly: - Roller Shade Driver does not work without a profile because it incorrectly reports "Receive when idle: No". - Motion Detector does not list a SsIasZone cluster which is required for such devices. We'll add your devices in the next update but there's no guarantee that they will work with LM. RE: Zigbee gateway integration - oliver.brown.knx - 03.06.2026 Thank you for your reply. When will it be possible to create custom profiles? I don’t know how complicated it is, but this way, every LM user could connect any Zigbee device. Could you please tell me which manufacturers strictly adhere to the Zigbee standard? I know there’s a list of supported devices, but I’m not sure if it’s up to date. There are many Zigbee devices, and before I buy another one, I’d like to know for sure that it will work with LM. Just for your information (I don’t want to compare HA and LM): I first tested all the Zigbee devices I wanted to connect to LM in Home Assistant, and they all worked there. RE: Zigbee gateway integration - admin - 04.06.2026 We've decided against allowing user-defined profiles. Most simple devices should work without a profile if the manufacturer adheres to the standard. Anything more complex usually requires modifying the app code to support non-standard features. As for recommended devices - the only advice is to avoid Xiaomi/Aqara and TuYa devices. In worst case certain devices simply use ZigBee as data transport for their own custom protocol. As for open-source alternatives - of course they have a wider supported device range. It's simply not viable for us to spend a lot of development time adding support for quirky ZigBee devices. RE: Zigbee gateway integration - oliver.brown.knx - 04.06.2026 Thank you for the explanation. If possible, please add the devices listed above. RE: Zigbee gateway integration - admin - 05.06.2026 @oliver.brown.knx, an updated version has been published. Reset your devices and pair them again. RE: Zigbee gateway integration - oliver.brown.knx - 05.06.2026 Thank you for your prompt response, but unfortunately the lumi.curtain.acn002 device does not respond to any commands and does not provide any feedback when opened or closed "manually." lumi.motion.ac02 it also doesn't respond. Both devices were found, but when their status changes, they aren't even updated in the group address. RE: Zigbee gateway integration - Sral1987 - 08.06.2026 (14.05.2026, 07:29)admin Wrote: @Sral1987, an update has been published. See if it works for you. Thank you admin, the percentage is shown as an Object now with 100%, it should work. RE: Zigbee gateway integration - admin - 08.06.2026 @oliver.brown.knx, enabled debug logging in the ZigBee app and post what you get in logs when controlling the curtain controller. RE: Zigbee gateway integration - oliver.brown.knx - 09.06.2026 Thank you for your help. Below is a summary of the status. lumi.curtain.acn002: Control and status via group addresses are not working. Device status (during manual control), position, etc., are not displayed in group addresses. Probably working in the monitor: AnalogOutput ReportAttributes AttributeReports = [ { Attribute = { Type = single, Value = 0 }, AttributeIdentifier = 85 }, { Attribute = { Type = uint32, Value = 0 }, AttributeIdentifier = 61440 } ] MultistateOutput ReportAttributes AttributeReports = [ { Attribute = { Type = uint16, Value = 2 }, AttributeIdentifier = 85 }, { Attribute = { Type = uint32, Value = 1711872 }, AttributeIdentifier = 61440 } ] lumi.motion.ac02 Device status (during manual control), position, etc., are not displayed in group addresses. Probably functional in the monitor: ManuSpecificAqaraOpple ReportAttributes AttributeReports = [ { Attribute = { Type = uint32, Value = 65690 }, AttributeIdentifier = 274 } ] RE: Zigbee gateway integration - admin - 09.06.2026 These are not standard ZigBee attributes. You can catch such reports using a script and update group address values: https://kb.logicmachine.net/libraries/zigbee/#resident-script-for-monitoring-several-devices Motion sensor AttributeIdentifier = 274 provides the luminance value. You have to subtract 65536 from the reported value to get the actual value. I'm not sure whether the device provides a "no motion" event or a separate timer logic is needed for it. RE: Zigbee gateway integration - Sral1987 - 17.07.2026 Hello, i bought a cheap IKEA Tretakt Plug, could you please create a profile, thank you Code: Manufacturer: IKEA of Sweden
Model: TRETAKT Smart plug
Firmware version: 2.4.4
Device type: Router
Power source: Mains
Receive when idle: Yes
Endpoint 1
Profile: 260
Input clusters
- Basic (0)
- Identify (3)
- Groups (4)
- Scenes (5)
- OnOff (6)
- LevelCtrl (8)
- LightLink (4096)
- 64599
- 64636
- 64645
Output clusters
- Ota (25)
Endpoint 242
Profile: 41440
Input clusters
- GreenPower (33)
Output clusters
- GreenPower (33)
Reported attributes
- calclevel: 254
- level: 254
- onoff: true
- prevlevel: 254RE: Zigbee gateway integration - admin - 17.07.2026 On/off control should work without a profile. What functionality are you missing? RE: Zigbee gateway integration - Sral1987 - 18.07.2026 (17.07.2026, 14:21)admin Wrote: On/off control should work without a profile. What functionality are you missing? Is there no power meter build in ? i thought the ikea plugs had that onboard. RE: Zigbee gateway integration - admin - 18.07.2026 No, this is a simple on/off device without power metering. |