Yes, please LEDVANCE please work on support for the Integration in Home Assistant for your WiFi devices.
1 Like
asm7100
(Allan)
March 27, 2024, 11:11pm
22
How are status on this, just got 4 product from them in føtex.
And i can’t see / find howto set them up in HA.
Think on Saturday i will go to føtex and get my money back. Same love the design, but with no direct HA, they are a no go for me.
There are other products there is easyer to setup
fribse
(Kenneths Teknik)
March 29, 2024, 9:52am
23
Nowhere, LEDVANCE does not want to support anything else than their own environment.
BUT there is some progress with localtuya:
rospogrigio:master
← avataar:oem-cloud-ledvance
opened 11:24PM - 17 Nov 22 UTC
This PR adds support for Tuya's OEM cloud API (the same API used by Tuya-derived… mobile apps), in particular LEDVANCE, as their client ID and secret are known, but also any other vendor by entering their client id/secret.
The cloud config flow was redesigned to prompt the user for the cloud type first:
* Tuya IoT Platform (i.e. the existing cloud support)
* Tuya OEM LEDVANCE - needs only email and password for the LEDVANCE mobile app
* Tuya OEM generic - needs email, password and vendor client id/secret
* No cloud
The OEM implementation supports:
* Fetching the local key
* Fetching the name
* Deriving a meaningful product name such as "LEDVANCE Light Source" based on the Tuya category returned by the API
In addition there are some usability improvements too:
* Use the category returned by the IoT/OEM API to determine the default platform when adding an entity
* Use Tuya's documented DPs as defaults for the light platform
* Use the device name as the default entity name
This means you can now add a light simply by clicking through the dialogs as the defaults are what you want (or very close to what you want). It can be easily extended to cover more entity types.
Other changes:
* Config is now version 3, version 1/2 will be migrated
* Refactored the cloud API a bit to allow for more isolation and different implementations
* Some config steps now use the new (as of April 2022) HA show menu step - which actually made some translations work
* Tried to adjust the existing it and pt-BR translations to reflect the changes - might need a native speaker to have a look
* Updated the README.md and info.md + some new screenshots
* Removed the "username" field for cloud configuration
* It had default value "localtuya" and set the name of the integration - had nothing to do with the cloud
* The name of the integration when added is now fixed to "Local Tuya" (can be edited later)
Credits: https://github.com/FlagX/ha-ledvance-tuya-resync-localkey whose code was used as a basis for a more cleaned up integrated version.
fribse
(Kenneths Teknik)
March 29, 2024, 10:34am
24
Oh, this is even more interesting I think:
Update for March 2024:
I bought yesterday LEDVANCE SMART+ WiFi Tube T8 and spent several hours trying to connect it to Home Assistant. Steps 1-5 were trivial.
The challenge met me at the step 6. local-tuya was not able to discover the lights. And if I tried to add it manually, I got: " Connection to device succeeded but no datapoints found, please try again."
The reason is that local-tuya does not support the protocol 3.5 which is the only protocol which my latest and greatest LEDVANCE tube …