-
Notifications
You must be signed in to change notification settings - Fork 502
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
Tuya/Jinvoo/Heiman curtain switch (SM-SW101-ZC) #2999
Comments
Update Basic Cluster Info (did reading again) Having now the manufacturer name in the field: _TYZB01_dazsid15 I Also tested to steer the device direct from the deConz Hui and it worked: So it seems already to work with the ConBee II stick and deConz, but not in Pimatic, which might have to be solved there then |
Closing this as device is now supported with .79 beta. |
Hey @SwoopX, thanks for your effort 👍 |
When you have subscribed to the apt beta channel and updated to the current version, then yes. Also marthoc should have updated the container already. |
Not quiet sure what you mean, but I will spend some research and convinced that I will find the answer 😉 |
Hi again @SwoopX, I'm sorry but I couldn't find anything which seems to fit to your hint. I still have no clue at all what I have to update from where. I'm running Pimatic with the raspbee 0.1.5 plugin on a Raspi4 with a ConBee II and deConz in headless mode. |
@Pedder007 I'm afraid I dont know Pimatic so I probably cannot help you there. How have you installed deconz anyway. You are already 4 versions behind 😉 If it is a package pimatics folks provide, they maybe should update. |
Ok, I understand this an searched a bit more. I think I now also got your point. You updated/enhanced the latest deconz version 2.05.79... to use the curtain switch, right? |
Hi, |
I assume you mean Phoscon in your case. This is kind of normal as devices have to be added seperately. I'd recommend to raise a corresponding request at the Phoscon repository.
This is actually the deconz GUI. If all works well there, then the device doesn't have any issue.
Probably the wrong API commands are used in this case. See #3063 |
Did you try to modify 0x0017 or 0x007 to 0x002 (calibration mode)? Does this work? |
Hi, sorry didn't find the time to continue here earlier. |
Device
Screenshots
The text was updated successfully, but these errors were encountered: