rospogrigio / localtuya

local handling for Tuya devices
GNU General Public License v3.0
2.85k stars 546 forks source link

Cannot add more DP when configuring device #905

Open rfam13 opened 2 years ago

rfam13 commented 2 years ago

Hello, the 4.0 update with cloud support is great!

However, when you add a device and create a DP from that device, if you go back and try to configure to add another DP, you are unable to, it just lets you configure the intial one you setup when adding the device.

Malekith83 commented 2 years ago

i was able to work around the problem by adding a new device under the same name / local key / ID, and then setting up the new entity here. After saving, it then added the new entity under the old device. Of course an add function in the old device would be a nicer solution. Attention: if you add an ID that is already in use, then the complete localtuya hangs and can only be restored by a backup

kbrown01 commented 2 years ago

Confirmed. The suggestion is really a total workaround and it is crazy you cannot add additional entity from another DP. Take a iBBQ-4T device. There are at least battery, power, 4 probe temperatures, WiFi, timeout, sound, light .... miss one and you have to delete and add it all again.

timnolte commented 2 years ago

The work-around doesn't work for me. Attempting to add another device with the same name/local key/ID errors out for me. I'm basically stuck with no ability to add additional DPs/entities to my device.

rfam13 commented 2 years ago

Yea I wasn't able to get it to work either, always just screwed up the whole thing and I had to remove and start over. I have around 15 devices I need to add so I am just waiting it out until it is hopefully fixed.

AFumi39 commented 2 years ago

Please, fix this bug. It's very urgent (a must-have basic feature) and it's unresolved from months, now

SKis274 commented 2 years ago

+1 for adding more entities to an existing device! I'm struggling with a local weather station that have more than 20 sensors!

rfam13 commented 2 years ago

Yea something was changed in the new update. It worked before that. Hopefully dev notices us soon, and is an easy fix.

timnolte commented 2 years ago

Along with being able to configure additional DPs, it would also be a huge help to be able to change the type of the DPs that have already been implemented. I thought before this was also possible. If you mess up and pick the wrong entity type for a Do you have no option other than to start all over. Sometimes it is not always clear what entity type should be used for a DP.

stain3565 commented 1 year ago

Just started using localtuya. Firstly, yes it does seem you cannot add an entity, despite some YouTube videos suggesting that adding a new LocalTuya integration and selecting the existing device should do it.

My implementation is worse in it's behaviour. If I try to add any second device, it forces me to go through the Api screen again (permission denied message) and forces me to select the "do not configure cloud account" option. This results in the localtuya integration resetting and losing my first device.

So, of my 6 tuya lights, just the one can be added.

rfam13 commented 1 year ago

Just started using localtuya. Firstly, yes it does seem you cannot add an entity, despite some YouTube videos suggesting that adding a new LocalTuya integration and selecting the existing device should do it.

My implementation is worse in it's behaviour. If I try to add any second device, it forces me to go through the Api screen again (permission denied message) and forces me to select the "do not configure cloud account" option. This results in the localtuya integration resetting and losing my first device.

So, of my 6 tuya lights, just the one can be added.

When you select configure it does not give you an option to Add New Device? Or this is when it forces you to the api screen?

But yes still no fix for adding more entities from the same device, I can't believe there aren't more people reporting this issue. I believe the YouTube are probably referring to the version before v4 where it worked perfectly.

stain3565 commented 1 year ago

It goes straight to the API config screen from clicking the integration