See this:
I have two of these (Blitzwolf branded). Personally I don’t mind if they go offline as long as they wake up if water is detected. They do, actually. Still using DTH though…
Hi @JINYONG
I take note to do it when I have access to the cli at the end of the week
Bad idea IMO, unless you notify people (perhaps in the settings text) that this device WILL mark itself offline constantly and its not the fault of the driver.
Hello,
Thank you for your work.
Is it possible for you to add support for MOES 2-gang(_TZE200_g1ib5ldv)/3-gang switch(_TZE200_tz32mtza)?
Thanks again,
Hi @csstup
It seems very correct to me that if you have a bad experience with these devices, you give them your opinion to help them.
I do not know, if these devices are disconnected, I am not aware that all those who have asked me to add to the driver, more than 10 of that TS0207 model, are being disconnected, no one has told me anything about it and users normally do comments when it does not work correctly, as happened with the very popular sonoff contact and movement sensors.
I don’t know if the problems are from the device or are problems from the user’s network or other causes.
If the user has the device and wants to test it, it’s their decision and it doesn’t seem like a bad idea to me.
I need the complete fingerprint, clusters included.
I think these devices use cluster EF00 and will not work with my driver.
I haven’t seen a difference yet. Sending a screenshot.
Also, the routines for daily on/off are not working on load2/switch2. We have to operate that one manually. To summarize: The whole device (ZBLMC30 Controller) has power applied to it always-on. It has a power meter to collect power consumption data–total power consumed (whole device) is more than enough info.
But there are two independent relays/switches that operate two different (pool pumps) loads. Right now the timer routines work on load1/switch1, but load2/switch2 appears as a child and should have its own routine. It does not. Load1/Switch1 (Primary Pool Pump) appears as the main power for the device. It would also be nice if I could call the Booster/Pool Cleaner pump something other than “Switch-2”
While I can imagine a scenario where both switches should be powered off/on together, I cannot imagine a scenario where one would want the whole device turned off–except to reconnect to the network.
I take note to do it when I have access to the cli at the end of the week
Hi @wtmayes
Multiple devices can perform independent routines for switch main and switch2
By default, it always checks the main, but you can uncheck it by clicking on it again.
Components in multiple devices cannot be renamed.
In settings you have the option to create an independent child switch for the switch2, to which you can change the name and room like any device.
You can change the name of the device to main.
Could you add support for this CR-MNZ1 switch? SmartThings picks it up as a “ZigBee Switch Power” but power reading is out by a factor of 10 (reads 300W instead of 3kW)
- Type: ZigBee Switch Power
- manufacturer: _TZ3000_tgddllx4
- model: TS0001
- zigbeeNodeType: ROUTER
Raw Description: 01 0104 0100 01 09 0003 0004 0005 0006 0702 0B04 E000 E001 0000 02 0019 000A
Thanks
Hi @solarfusion
I take note and I will add it on the weekend
Hi @Murilo_Lourencao
Added to this driver version
───────────────────────────────────────────────────
Name Zigbee Switch Mc
Version 2023-02-04T11:42:01.140383678
───────────────────────────────────────────────────
- id: "_TZ3000_jcqs2mrv/Switch"
deviceLabel: Smart Switch
manufacturer: _TZ3000_jcqs2mrv
model: SM0001
deviceProfileName: single-switch
Hi @solarfusion
Added to this driver version
───────────────────────────────────────────────────
Name Zigbee Switch Power Mc
Version 2023-02-04T11:46:28.816272854
───────────────────────────────────────────────────
- id: "_TZ3000_tgddllx4/TS0001"
deviceLabel: TS0001 Plug
manufacturer: _TZ3000_tgddllx4
model: TS0001
deviceProfileName: switch-power-energy-plug
1 Like
thank you very much!
1 Like
Hi @JINYONG
Added to this driver version
───────────────────────────────────────────────────
Name Zigbee Moisture Sensor Mc
Version 2023-02-04T12:22:53.206962456
───────────────────────────────────────────────────
- id: "_TZ3000_d16y6col/Sensor"
deviceLabel: TS0207 Water Sensor
manufacturer: _TZ3000_d16y6col
model: TS0207
deviceProfileName: moisture-battery
Question for you, Mariano: TP-Link is now offering the first Matter supported device, which looks to be a smart plug. Everyone here knows you’re awesome and practically overworked by us, but I was wondering what your plans were for Matter support?
I think that’s a question for @SmartThings or TP-link, Mariano is doing enough already, don’t you think?
Yup, you’re right. That’s why I phrased it the way that I did. He’s awesome, and everyone here knows it. After running a search, I couldn’t locate this question, and it’s likely going to be a question many will have about the driver packs in the near future with the first wave of Matter devices coming out.
I appreciate your words and the faith you have in me.
I don’t have any plans for Matter, since I’ve read so many wonderful things that I don’t think anything custom will need to be done.
All developers are going to have to find another job 
3 Likes
We may get retired until then, Mariano! 
… and we will finally have the time to improve our home automation, instead of writing and supporting drivers all the time… I am waiting eagerly for the Matter miracle times to come soon!
1 Like