I burned two shade motors before figure this out. If you enabled the switch interlock in the device settings everything works fine when controlling the device through the mobile app or the switch inputs S1 and S2. But if you press the relay’s button it doesn’t respect the interlock configuration and switches on both L1 and L2 contacts which might result in unexpected outcome.
1 Like
@george_simeonov Thank you for sharing your experience with the Dual Relay Module T1, and I’m sorry to hear about the issues you’ve encountered with your shade motors. It sounds like you’ve discovered an important detail regarding the interlock settings and how they interact with the relay’s hardware button.
While the interlock configuration ensures safe operation through the app and switch inputs S1 and S2, it appears the hardware button does not adhere to this setting, leading to both L1 and L2 being activated simultaneously. This could potentially cause damage, as you’ve experienced.
Your insight is invaluable for both users and the Aqara team to consider potential firmware updates or warnings in the device documentation. I’d recommend reaching out to Aqara’s support team to share this feedback directly. Your experience might help in driving improvements and preventing similar issues for other users.
Please feel free to continue sharing any further observations or tips with our community. Your contributions are greatly appreciated!
2 Likes
Hello, is the self-locking mode between T2 contacts enabled? I don’t have it, I checked it myself.
By the way, maybe you chose pulse pressing. Then you need an additional check after operation. If so, write back, I will check.
I’m talking about this setting.
3 Likes
Yes, switch interlock is enabled. The switch connected to S1 and S2 is working as expected. The button on the relay itself is switching on/off both L1 and L2 contacts when pressed.
1 Like
Are you using a “push” button or a “switch”?
Another possible scenario is when there is conflicting automation, reset the automation screen.
2 Likes
I’m using a shades switch:
It is push type. Contact is on while depressed. But the switch doesn’t matter. It works fine. If I press down direction and then while the shades are closing I press the up button the switch interlock works fine and it stops L1 before enabling L2. The problem was happening while I was installing the relay and while trying to mount it behind the wall switch I pressed the button on the relay itself. There are no conflicting automations. I have only automations to switch the power off after a delay.
2 Likes
This is a very very bad bug! Aqara should replace the damaged motors for you. This is dangerous!
Once again, please give me a screenshot of the automation. For information, the T2 relay in push-button mode has its own characteristics, especially in interlock mode.
1 Like
This is the configuration.
This is the only automation I have so far.
IMHO the hardware button on the relay should always respect the interlock configuration no matter of the switch configuration.
1 Like
Hello, sorry for the delay in responding.
I checked and made sure that the button on the relay is not intended for controlling the relay, it is only for switching the state (control).
The main function is performed by automation.
I suggest you make three automations that will secure the operation of your motor.
1- blinds up. In this automation, a control state for the interlock is made. In the THEN command, we duplicate the shutdown of the unused contact.
2- the same as in the first, only for the second contact.
3- Emergency shutdown of contacts (if two are turned on simultaneously by accident).
I also want to emphasize that the Aqara company is not responsible for an incorrectly connected device to an external load. I emphasize once again that the button on the relay is a technological button, and if the above automation (3) had been registered, the motors would not have burned out.
The interlock command in the setup is only an additional function to the main automation.
Conclusion, before connecting the device, it is necessary to calculate in detail all the risks when connecting.
I think that if there is a feature called interlock in the GUI and that setting is not enforced in all situations in the relay firmware then it should be removed as it is not fit for purpose.
I think if a feature gives the impression of reliable operation but it is ignored then it is not a feature that should be present.
I think people should not recommend the use of the interlock feature until this is fixed or a warning added to the GUI.
I think anyone who recommended the use of the interlock feature for this sort of use case was wrong to do so if they were not sure that it was free of bugs.
You are not understanding the problem. I do not use the button on the relay for control. Noone is suggesting that. I’m saying that if there is a configuration that ensures the two channels cannot be on at the same time people expect that this is always true but it is not. There is no warning that this might happen. It happened to me multiple times before I found out how it works. It happened by mistake and not by design because I was pressed the button on the relay by accident while powered. I’m just warning people that this is happening so they do not repeat my mistake. Aqara can fix this issue by changing the firmware to respect the setting for the relay button as well or at least add a warning that the button does not respect this setting.
1 Like
Hello, thank you for the warning. This issue has already been raised at the level of Aqara representatives. They are already working on a solution.
Once again, we apologize for the inconvenience.