-
Notifications
You must be signed in to change notification settings - Fork 186
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
Add Temperature and Humidity Sensor support (device type 'wsdcg') #105
base: master
Are you sure you want to change the base?
Conversation
Can someone please review this and approve? I would really like to have this integration. |
@chiefcw If you want to try this before the authors merge it, you can install the plugin from my fork directly. Do a |
@macecchi Thanks for the info. It reports the temperature but the humidity always shows 0%. |
I have a dual temp/humidity sensor which shows up as a wsdcg climate sensor in the homebridge logs: Adding: Climate Sensor (wsdcg / "device ID") However it's actually connected through a Tuya BLE WiFi Gateway (branded as ARLEC, "Grid Connect", Australia, links below) so I am pretty excited about exposing this and possibly other sensors to homekit! Sensor: BLE gateway shows up as: https://www.bunnings.com.au/arlec-grid-connect-smart-home-hub_p0148571 |
@chiefcw are you on Homebridge version 1.3.5? I had the same issue when after upgrading from 1.3.4 to 1.3.5 (with other Tuya sensors as well). For the meantime I just downgraded it but I'll try to have a look at it. |
@macecchi Yes, I'm on 1.3.5 , I tried downgrading to 1.3.4 and still the same issue, no humidity reading. It's ok with me for now as I really only wanted the temperature reading. Thanks for your work on this. |
@chiefcw this will fix the humidity value reading. macecchi#2 |
Fix typo in Humidity Sensor Code
Hi, may I ask when temperature and humidity support will be available ? |
Hello, I'm my zigbee temperature humidity sensor I use this values:
|
Hi Mario,when will it be merged to the tuya:master? as till now the Temperature and Humidity Sensor support (device type 'wsdcg') is not yet supported in tuya:master. |
Hey @Magna66, I wish I knew :/ it looks like the project maintainers aren't really acknowledging many contributions. :( |
Thank you Mario for your reply. Cant you make it as a separate project for homebridge if you have the time? At the moment I am using your master (npm install -g macecchi/tuya-homebridge), and it is working great thank you so much for your contribution. |
I wish I had the time hahaha but I'll occasionally update my fork with the latest updates from here so you can keep using it if you like. I've been using it for a while and with the latest updates from the main repo it's been pretty stable for me. |
Thanks a lot, that was my real worry, if there is an update, and yes I am using yours, it is stable. Really appreciate your contribution. |
@macecchi are you able to advice what will be the way to try replace this plugin with yours and not losing devices from homekit in the meantime. Just don't want to set all devices and automations as from beginning. How homebridge / homekit will behave if both plugins installed? Im waiting for ability to see temperature and humidity in HK for months and looks like can't count that original plugin will be updated. Thanks in advance |
I am Unable to use my sensor. i didnt know if its workuing, because the Plugin and the Cloud isnt easy to understand :-/ |
when i do this nothing happens. i dont see the plugin in my plugins |
@macecchi - i've tried your version of tuya-homebridge, |
For anyone still trying to use this, check out this fork instead: https://github.com/0x5e/homebridge-tuya-platform |
Hi Please can we approve this. |
#238 (comment) Its a regularly requested feature |
Hi there! First of all, thanks for creating this project! \o/
This PR adds support for the Temperature and Humidity Sensor like this one (device type wsdcg). This closes issue #92 and this item on the vote discussion page.
Here's what it looks like on the Home app:
Status bar:
When expanding it:
By the way, I wasn't able to build it the same way of other accessories that have subServices. I had some issues in base_accessory when adding the service and ended up creating the secondary service directly on the accessory class. Please feel free to refactor this if necessary :)