Wofea WG-088 garage door opener it is not recognized #330
Comments
|
@rospogrigio Is there anyone who can help me with this issue? |
|
@ultratoto14 Is there anyone who can help me with this issue? |
|
Hi, sorry for the late reply. It looks like the device is not responding, I would suggest to double check that the localKey is correct. You could also try to launch the tuyadebug script you find mentioned in the readme page. Also, make sure that your Tuya app is closed (or disconnect your phone), because some devices don't allow multiple connections (I would suggest to use the Jinvoo app in this case, that seems to allow those instead). |
|
@rospogrigio Thank you for your reply. I have checked the localKey was correct. I used the debug process described in the readme page (setting the logger to log the localtuya in debug mode). I have inserted the debug messages in my initial post. I don't know what do you mean by the tuyadebug script. I am currently using the Tuya app, but I will try the Jinvoo app too. |
|
I mean using this: https://github.com/rospogrigio/localtuya/wiki/HOWTO-get-a-DPs-dump |
|
@rospogrigio Thank you. Here is the outcome: Currently the device is liked to Tuya app. In the app I can use it as intended. If I try to integrate it in localTuya in HA, I get this error: What to do next? |
|
Well, at least it works. |
|
@rospogrigio Which YAML configuration are you referring to? |
|
You have 2 ways to setup your device: using YAML or config flow, please refer to the README. I believe you are using config flow and for some reason it's not working, so I would give YAML a try. |
|
@rospogrigio Yes, so far I tried to setup the device using config flow. My other devices all worked fine with that method. I will try setting up the garage door using YAML. I am reading now about this topic (Wofea WG-088) on the Tasmota repository. I am trying to identify which DPS doing what and how to set them up in the YAML config. It looks like the DPS 1 is a switch (actualy kind of momentary switch), DPS 101 is the reed sensor and they couldn't identify DPS 7. By the way my garage door opener is this one: https://www.aliexpress.com/item/32997953761.html?spm=a2g0s.9042311.0.0.27424c4dmGtouE |
|
You should operate the device (open / close) manually or with the app and see how the DPs change during the operations. I am expecting DP 7 to change to 1 and 2 but it can also be some other values. If it's 1 and 2 I think you have to patch the code to make it work, and I can make a PR for you once you manage to make it work. |
|
@rospogrigio I have tested my garage opener and here is the outcome:
If I set a countdown timer in the app, the DPS 7 will have the value of this timer in seconds. Each time when I run the test.py it will show a different value for the DPS 7, according to the current value of the timer. Can you provide me a sample YAML config for my case which I could then refine for my use case? |
|
Mmm, I mean you need to get the values DURING opening, not when it's stopped. We need to understand the DPs status for the 3 situations: opening, closing, stopped. Then we can discuss about configuration and coding. |
|
As long as the reed sensor is open, both DPS 1 and DPS 101 will show TRUE, regardless if the garage door is stopped in the middle (is half open) or fully open and they stay TRUE until the reed sensor gets closed, when both will display FALSE. What should I try else? |
|
I have tried to create a YAML configuration. This is what I came up with: After HA restart, these are the error messages> Any hint to go further? |
|
@rospogrigio do you have any idea what else to try? |
|
@KixMan28 I found the same problem when adding my WG-088. I managed to get it to work when using localTuya versions v3.0.x, once upgrading to v3.1.0 and v3.2.0 the same problem came back. So something must have changed between v3.0.3 and v3.1.0. |
|
@stanvx Thank you for the hint. I will try to downgrade my localTuya to the version you mentioned and give it a try. @rospogrigio Do you have anything to add this topic? |
|
Frankly no... let's try to downgrade and see if it works, and if it does we need to find the differences to see where is the issue. |
|
@rospogrigio I have downgraded localtuya to ver 3.0.3 and when I try to add my garage door via the Integrations page, i get this error: Any suggestions? |
|
No sorry, maybe @postlund can give a hand.... |
|
From you DPS dump, you have only 3 DPs available, the DP 1 can have value true or false, it's more like a switch than a cover. Seems that in the code, cover is managing on/off, open/close but not true/false Ensure to remove all the devices belonging to the garage door from integration > localtuya Replace you config by something really minimal as this: localtuya:
- host: 192.168.1.XX
device_id: XXX
local_key: XXX
friendly_name: Garage Door
protocol_version: "3.3"
entities:
- platform: switch
friendly_name: Garage Door Switch
id: 1Then you can try to see if with this switch you can control your garage door. As a general remark, you should always check with the latest code as it's really time consuming to debug an old version. So stay with latest. |
|
@ultratoto14 Thank you for your suggestions. I will try to do what you have recommended. |
|
@KixMan28 no problem, I read the thread, it's a good advice to get back and check on old version, it is always a good thing to see if the new versions introduce a problem. I ment if the test is non conclusive, get back to latest 😄 |
|
@ultratoto14 I have tested, as promised, in both old version and news version, and both in YAML and integration. Currently i have set it up as YAML in the latest version and the device is sometimes available and sometimes not. The current error message is the following: Do you have any hint what to do? |
|
It would be helpful to go into debug mode (see README) for localtuya and get the messages that the component failed to decode. |
|
@ultratoto14 Hi! Finally I succeeded to run the Debug mode. My garage door opener has the IP address: 192.168.1.18. Please see below the debug report: Any idea why I have this issue? |
|
@ultratoto14 Can you advise something? |
|
@ultratoto14 Hi! I have been using the device in the previous days with your YAML config. Sometimes it works as intended, but most of the time is "Unavailable" and in the logs I see the error message displayed above. Do you have any suggestion? |
|
@ultratoto14 Here is a screenshot of the availability of the device. |
|
Mine comes up as a switch and can open and close the door based on the yaml config @ultratoto14 posted, using version 3.3 (latest). Cannot configure via the gui setup. Happy to help porvide any logs so we can get this going. |
|
I also set up the garage door opener with the YAML code provided by @ultratoto14. sometimes works and most of the time is unavailable. I don't know what to do with it. Maybe I will try to flash it with Tasmota, as I can see here it is supported by the latest version. |
Thanks for the link, I'll have a look at tasmota. I've never flashed anything to tasmota, so will see what guides I can find. With nabu casa purchasing esphome I might even just wait for that option |
|
I flashed almost all my Tuya compatiblec devicesc with Tuya Convert and uploded to them ESPhome firmware. I am also looking forward to this Nabu Casa deal, but I couldn't find any relevant info about the future of ESPhome. Maybe we will learn more on the next Home Assistant live stream. |
|
hello all This is my current setting
|
|
@highlandtran No luck so far. I already removed my Garage door from HA as it was unavailable all the time, and it was spamming my log with errors and warnings. It work fine in my Tuya app so I am using it there (as I have in there other devices too). Until I am not taking out of the cloud all my other devices, I keep my setup as is today. If you happen to flash Tasmota on your Wofea, it would be nice if you could report back the result here. |
|
@highlandtran @eatoff8 @stanvx @ultratoto14 @rospogrigio |
|
This device isn't real garage door opener (like mine). It's a switch with sensor. Hope this helps... |
Hi mate, not realy work for me, what is your setting on this? i only have 1 tick
|
|
Do not set it as cover, but switch. EDIT: To add second entity, after setup first (switch) untick "Do not add..." and you can add next entity to device... |
|
@patrik-malina Thank you for your input. I will give it a try. My biggest problem is that this device is recognized only by the Tuya app (as garage door opener with countdown feature). None of the integrations (localtuya, HA Tuya nor HA Tuya V2) will recognize it automatically, although it is listed in the Tuya Developer devices. |
|
Work perfectly for me now, thank you @patrik-malina |
|
@patrik-malina Thank you for the hint. So far it works for me too. As this device has also a dp7, which should be a timer, can I do anything with it? |
|
You could add it as sensor (not binary) without class: |
|
@patrik-malina Thank you. I will test it. |
|
So far the @patrik-malina solution works. Thank you again for the hint |
I am running HA on a RPI 3B+, with HA ver 2021.1.4, HassOS
I have installed the latest localtuya V3.2.0.
I have several smart sockets and, wall switch and a garage door opener in my Tuya app. I could integrate all devices in localtuya, except the garage door opener. When I try to add it to localtuya, I get the following errors:
and this error:
What is the problem? What should I do to have this integrated in localtuya?
The text was updated successfully, but these errors were encountered: