Multiple switch device about tuya-local HOT 21 CLOSED

This is a known limitation, which I intend to fix in future. I think such devices should be easy to configure in the localtuya integration (similarly named but with different origins and approach).

from tuya-local.

I use localtuya too, just there is no lock and no climate so far (these are in PRs, however).

from tuya-local.

Related to PR #55

from tuya-local.

The support for this is now in main. Currently I don't have any way to test it, I may change one of my devices later tonight to use two switches instead of a switch and a light, just to confirm before I publish this as a release.

from tuya-local.

Once this is in release, I'll make a few more configs for multiswitches.

from tuya-local.

I have several dual controlled switches, and can test against them. They basically have just 4 dp's, 2 are for the switches (true/false), and two are the countdown timers (switch_1 has countdown_1, switch_2 has countdown_2) timers can be set from 0 to 86400 seconds.

The product name is 'SW02-02N'.

switch_1	Boolean	"{true,false}" - dp 1
switch_2	Boolean	"{true,false}" - dp 2
countdown_1	Integer	- dp ?
  {
    "unit": "s",
    "min": 0,
    "max": 86400,
    "scale": 0,
    "step": 1
  }
countdown_2	Integer	- dp ?
  {
    "unit": "s",
    "min": 0,
    "max": 86400,
    "scale": 0,
    "step": 1
  }

from tuya-local.

I also have this one, which is 4 switches, called 'Geeni EXTEND Multi-Port Wall Tap WW119'

switch_1	Boolean	 "{true,false}"
switch_2	Boolean	 "{true,false}"
switch_3	Boolean	 "{true,false}"
switch_4	Boolean	 "{true,false}"
countdown_1	Integer	
  {
    "unit": "s",
    "min": 0,
    "max": 86400,
    "scale": 0,
    "step": 1
  }
countdown_2	Integer	
  {
    "unit": "s",
    "min": 0,
    "max": 86400,
    "scale": 0,
    "step": 1
  }
countdown_3	Integer	
  {
    "unit": "s",
    "min": 0,
    "max": 86400,
    "scale": 0,
    "step": 1
}
countdown_4	Integer	
{
    "unit": "s",
    "min": 0,
    "max": 86400,
    "scale": 0,
    "step": 1
}

from tuya-local.

This is released now, please test 0.12.1 and let me know if it is working properly.

from tuya-local.

@ThomasADavis if you can also include the log warning message with the list of dps when you try to add these devices, then that will help identify the other dps ids.

from tuya-local.

When I used it yesterday I noticed that config flow does display ticks only with no description for multiplied type.

from tuya-local.

I think for the new switches you added, some new strings need to be added to the translations file. Or rename the entities to match existing ones.

from tuya-local.

I'll look at this

from tuya-local.

I already did 😃

from tuya-local.

I tried to make it work by adding to translations the below in two sections. Seems similar to others, say a child lock:
"switch_wall_switch_1": "Include Wall switch 1 as a switch entity",
"switch_wall_switch_2": "Include Wall switch 2 as a switch entity",

However, it does not show anyway. Anywhere else missing?

from tuya-local.

Sometimes you need to force a refresh of the front end with a Shift-Refresh immediately after changes like this.

from tuya-local.

It works now :) Before I make PR - I haven't found any rebase option as such on Github's web. I did pull and merge as they say to do. Anywhere else to look before I make another PR mess?

from tuya-local.

Take a look at the 3 most recent commits I made. I renamed the outlets to "Outlet 1" and "Outlet 2" for both Grid Connect double outlets, so the number of translations doesn't grow unnecessarily. So probably we're headed for another merge/rebase conflict again.

I think the GitHub UI is too basic to handle this nicely. I always use TortoiseGit or the command line for merging and rebasing. I think the "use theirs" and "use ours" options during merge are better to use than adding extra commits deleting and recreating the conflicting files.

I'm a bit surprised that changes before your most recent merge caused conflicts when rebasing, I would have expected the merge point to set a common start point, so my knowlegde of git is also not perfect... At some point when things have gotten too far out of step, it might be best to rename your branch to main_old, and start over with a fresh main branch based on upstream.

from tuya-local.

I think for outlets "left" and right" is a lot more descriptive as it instantly shows what is connected to which.

from tuya-local.

Entities can be renamed in the UI. I am more concerned with the maintenance of the translations, as different switches are going to be left/right or top/bottom, or for more than two they are going to end up numbered anyway. Fewer distinct strings to maintain is easier, especially if users start contributing translations for other languages.

from tuya-local.

I have the dps for a long time now.. just been waiting for the multiple duplicate entities to work.

from tuya-local.

Yep entities can be renamed, trouble is whether outlet 1 is left or right. It can be found by switching it but I believe after mounting double outlet it is obvious which side is left and if first time discovered is labeled the same way it is clear. Then, it can be renamed to "TV" or "fridge", or whatever knowing is is connected to left hand side. That was my idea.

from tuya-local.