Skip to content
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

Problems with the Tuya Binding #590

Closed
RayMorgan1337 opened this issue Sep 9, 2024 · 1 comment
Closed

Problems with the Tuya Binding #590

RayMorgan1337 opened this issue Sep 9, 2024 · 1 comment
Labels
stale An issue is marked stale after four weeks without activity and will be closed one week later.

Comments

@RayMorgan1337
Copy link

I have installed the Tuya Binding on openhab 4 in a docker Container.
Everything is online and cloud connection too.

In the Tuya Developer view I can see my device as online.
In the FritzBox I can see the IP Adress and that the device is connected.

Somehow autodiscove can't find any device. If I use the Network Binding I can find my device and ping to it. But the other way round it won't work.

If I generate the device by hand, I get Configuration Error

(Code:)

UID: tuya:tuyaDevice:c0de12254d
label: Generic Tuya Device
thingTypeUID: tuya:tuyaDevice
configuration:
pollingInterval: 0
protocol: "3.1"
productId: k43w32veclxmc9lb
deviceId: bfee1d8dd514aab38fiaap
localKey: hg0AW}j_+s~)oErU

The app is closed. What else can I do?

Help please. Its the first tuya device that I want to integrate. More are ordered already.

Copy link

stale bot commented Nov 5, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale An issue is marked stale after four weeks without activity and will be closed one week later. label Nov 5, 2024
@stale stale bot closed this as completed Nov 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale An issue is marked stale after four weeks without activity and will be closed one week later.
Projects
None yet
Development

No branches or pull requests

1 participant