List of future improvements

postlund commented 3 years ago

I think it's a good idea to make a list of features and improvements we can make in the future. I'll start with my list:

Extract code and create base class for entities, e.g. LocalTuyaEntity based on a config entry.
Update entity on-the-fly when options are changed without having to restart Home Assistant (depends first bullet and #14).
Scanning support in config flow.
Use scanning to find a device before connecting to it, to handle dynamic IP address changes. I use a similar scheme in the Apple TV component.
Break out status polling from individual entities and inform entities about updates via the signal interface. This allows us to update devices with multiple entities, e.g. double gang switches, with one request instead of one per entity.
Make our pytuya implementation actually support the protocol, e.g. by inserting correct sequence number (and other stuff that needs to be handled). The outcome I'm after is to have the network connection up at all time instead of connecting, sending command and immediately disconnect when done. I believe this will be a lot more stable and faster.
Convert pytuya to asyncio (and the rest of the integration as well).
Add generic sensor and binary_sensor platforms that can read any DPS value and present as state.
Easy set up of helper sensor, e.g. integration sensor that calculates kWh for used energy.
General code clean up, removing commented code (it's still available via git history), remove print statements and change some to debug, run black, pylint and flake8 on all code.
Improve documentation, translations in config flows, etc.

Anything I have missed? After some discussion we could make a priority list, create issues for things to do and come up with a roadmap (as supported here on GitHub).

cwttdb70 commented 3 years ago

There's been discussion over at https://github.com/rospogrigio/localtuya-homeassistant/pull/10 about adding a "Hacked Position" config option for cover devices that lets you set the "position" for devices that don't technically support setting device position. This could be added as an experimental feature or something along those lines. Or is there a better way to approach this? All of my cover devices support set position, so i'm probably not the best person to work on this feature.

rospogrigio commented 3 years ago

Somebody on the community thread asked for the climate platform to be introduced.

postlund commented 3 years ago

The climate platform should be quite easy to implement now if someone knows how what the DPS are used.

rospogrigio commented 3 years ago

Let's update the list:

DONE: Extract code and create base class for entities, e.g. LocalTuyaEntity based on a config entry.
DONE: Update entity on-the-fly when options are changed without having to restart Home Assistant (depends first bullet and #14).
DONE: Scanning support in config flow.
Use scanning to find a device before connecting to it, to handle dynamic IP address changes. I use a similar scheme in the Apple TV component.
ALMOST DONE: Break out status polling from individual entities and inform entities about updates via the signal interface. This allows us to update devices with multiple entities, e.g. double gang switches, with one request instead of one per entity.
IN PROGRESS: Make our pytuya implementation actually support the protocol, e.g. by inserting correct sequence number (and other stuff that needs to be handled). The outcome I'm after is to have the network connection up at all time instead of connecting, sending command and immediately disconnect when done. I believe this will be a lot more stable and faster.
IN PROGRESS: Convert pytuya to asyncio (and the rest of the integration as well).
DONE: Add generic sensor and binary_sensor platforms that can read any DPS value and present as state.
Easy set up of helper sensor, e.g. integration sensor that calculates kWh for used energy.
DONE: General code clean up, removing commented code (it's still available via git history), remove print statements and change some to debug, run black, pylint and flake8 on all code.
Improve documentation, translations in config flows, etc.
Positioning handling for covers
Support to climate platform
Improve support to lightbulbs

postlund commented 3 years ago

We should create issues for each remaining thing and perhaps start to use milestones. It makes it easier to plan our work.

sajid2310 commented 3 years ago

Support for Multi gang switch with FAN.

postlund commented 3 years ago

Support for Multi gang switch with FAN.

Per se already supported, but the fan platform needs some attention.

RobyDomo commented 3 years ago

Hi, do you think is it possible to have a vacuum platform? I have a robot that works with smart life app. I already extracted ID and Key, but without vacuum platform i don't think it can work locally. With tuya integration HA has imported the scene, so i can use vaccuum but anyway i use tuya cloud.

postlund commented 3 years ago

Probably possible, but they are quite complex so likely requires a bit of work. Maybe you can create a new issue (as a feature request) and post a DPS dump?

RobyDomo commented 3 years ago

thank you for you answer @postlund . Sure i can create a new issue as a request, but i don't know how to create a DPS dump. Thanks for your help. :-)

rospogrigio commented 3 years ago

@postlund I can take care of this, looks like MUCH easier than climate platform. @RobyDomo in order to have a DPS dump you can use the script in tuyadebug.tgz or wait some hours because we are about to have this PR available: https://github.com/rospogrigio/localtuya/pull/79 (or maybe you can just try it and provide feedbacks, actually).

postlund commented 3 years ago

@rospogrigio Maybe add some instructions for tuyadebug to readme as I did with debug logs? Or maybe we should move as much as possible over to the wiki instead as that is more flexible?

rospogrigio commented 3 years ago

Yes, I agree...

rospogrigio commented 3 years ago

@RobyDomo I created the PR #111 for the vacuum implementation. Please post the DPS dump there once you have it, so we don't flood this topic. Thank you

rospogrigio commented 3 years ago

Updated list:

DONE: Extract code and create base class for entities, e.g. LocalTuyaEntity based on a config entry.
DONE: Update entity on-the-fly when options are changed without having to restart Home Assistant (depends first bullet and #14).
DONE: Scanning support in config flow.
DONE: Use scanning to find a device before connecting to it, to handle dynamic IP address changes. I use a similar scheme in the Apple TV component.
DONE: Break out status polling from individual entities and inform entities about updates via the signal interface. This allows us to update devices with multiple entities, e.g. double gang switches, with one request instead of one per entity.
DONE: Make our pytuya implementation actually support the protocol, e.g. by inserting correct sequence number (and other stuff that needs to be handled). The outcome I'm after is to have the network connection up at all time instead of connecting, sending command and immediately disconnect when done. I believe this will be a lot more stable and faster.
DONE: Convert pytuya to asyncio (and the rest of the integration as well).
DONE: Add generic sensor and binary_sensor platforms that can read any DPS value and present as state.
DONE: General code clean up, removing commented code (it's still available via git history), remove print statements and change some to debug, run black, pylint and flake8 on all code.
DONE: Positioning handling for covers
IN PROGRESS: Improve documentation, translations in config flows, etc.
IN PROGRESS: Registration among default HACS integrations
IN PROGRESS: Improve support to lightbulbs
IN PROGRESS: Support to climate platform
IN PROGRESS: Support to vacuum platform
Easy set up of helper sensor, e.g. integration sensor that calculates kWh for used energy.
Introduction of utility sensors, e.g. Connection status error...
Introduction of a database of devices' presets for commonly used commands combinations, feedable by users.

What an incredible roadmap!

postlund commented 3 years ago

An incredible journey indeed!

WizBangCrash commented 3 years ago

Great journey indeed and you didn't even include "IN PROGRESS: Support for passive door/window sensors" :-)

postlund commented 3 years ago

Ok, that part might not be totally true 😉 But I'm getting closer. Been prioritizing bug reports lately. But will get back on that horse soon.

Vismuthxxx commented 3 years ago

Good time of day! how do I add a ZigBee wireless gateway? there is not a single line there is no gateway. Only binary_sensor, cover, fan, light, sensor and switch

postlund commented 3 years ago

@Vismuthxxx Not possible since it's not supported yet. There's already a request for it: #69

postlund commented 3 years ago

I will go on and close this issue now as I feel that it has served its purpose: give us a start. We have plenty of feature requests already and bugs to deal with. So no need for this.

glorifiedg commented 3 years ago

Any plans for IR controllers?

postlund commented 3 years ago

@glorifiedg This issue is closed now, but somewhat related to #159?

galtamur commented 3 years ago

Hello, I am experiencing this situation: I configured TuyaLocal component with four smartPlugs with current monitoring, and i implemented the template sensors to show the consumption in Lovelace. It works fine, but from time to time, it looks like the data are not updated (like freezed); when I open on my iphone the SmarLife app and i go into the consumption page, I see number updated, and the are updated also in HA. Did anyone else experienced the same problem? Any suggestion? Thank you

postlund commented 3 years ago

Hello, I am experiencing this situation: I configured TuyaLocal component with four smartPlugs with current monitoring, and i implemented the template sensors to show the consumption in Lovelace. It works fine, but from time to time, it looks like the data are not updated (like freezed); when I open on my iphone the SmarLife app and i go into the consumption page, I see number updated, and the are updated also in HA. Did anyone else experienced the same problem? Any suggestion? Thank you

Here: #87

geckom commented 3 years ago

The climate platform should be quite easy to implement now if someone knows how what the DPS are used.

Hope this might help - tuya climate device.

 dps: {
     '1': true,  -- power
     '2': 23,   -- target temp
     '3': 25,   -- current temp
     '4': 'DRY',  --- mode  DRY/HEAT/COOLOFF
     '5': '1',   FAN -  1 = low, 2 = medium. 3=high
     '19': 'C', = C or F
     '102': false,    -- Unknown - I suspect this is water tank is full
     '103': 3,     -- Current timer set (in hours)
     '104': false,  --Swing
     '105': 179,   -- Current Timer Countdown (in minutes)
     '106': 0,
     '110': '0'
}

jmargallo commented 3 years ago

Hello Do you think the Support to Wifi Door Sensor platform will be soon?

I just installed this sensor yours () and even manually setting the deviceid and the local key ... I can't integrate it. The rest of my devices yours without problem and very grateful

Simon-CR commented 3 years ago

my SP20 (teckin smart wifi-plug) or my outdoor 3 outlet wifi plug (also teckin) have two options per outlet. One of them is standard on/off as expected, the second one is a countdown timer (countdown_1 | Integer | {"unit":"s","min":0,"max":86400,"scale":0,"step":1}

This countdown will toggle (off if on, on if off) after it has rundown to 0.

I dont know how I can currently integrate it in a usable way. This would give the option to set the timer that does not rely on homeassistant and it's ressources to do it's job).

on my 3 outlet switch I have countdown_1, _2, _3

if I add it as a sensor, and set a countdown on the tuya app, I can see the value updated in HA.

thanks

txespirito commented 3 years ago

I bought a switch with a lud led but I can't set the light to 100%. The dps indicated are the following that do not correspond to the lights indicated in the documentation.

{
  "activeTime": 1614962379,
  "devId": "xxxxxxxxxxxxxxxxxxxxxxx",
  "displayOrder": 0,
  "dpMaxTime": 1614963543272,
  "dpName": {
    "1": "Interruptor 1",
    "27": "Led Switch"
  },
  "dps": {
    "1": false,
    "9": 0,
    "27": false,
    "28": "colour",
    "31": "ff00100164ffff",
    "32": "3855b40168ffff",
    "33": "ffff320100ff00",
    "34": "ffff5003ff000000ff000000ff000000000000000000",
    "35": "ffff3201ff0000",
    "36": "ffff0505ff000000ff00ffff00ff00ff0000ff000000",
    "37": 0
  },

Has anyone managed to configure it correctly and could update the documentation?

Thanks

This is the link of the switch/ligth model: https://es.aliexpress.com/item/1005001681604103.html?spm=a2g0s.9042311.0.0.365763c0lUQCEj

fabiohblage commented 3 years ago

Hello how to add a four button switch?

bfmorgan commented 3 years ago

I have a Feit dimmer switch. It would be nice if dimmers were added to the list of devices supported. If there is a yaml way of integrating them now, can someone lead me in that direction? thanks.

sercri commented 3 years ago

The scan function for those ip that dinamycally changed appears as it is not working any more since core-2021.4.6 update on an hassio setup rb3+. I cannot set a static ip because the 4g modem does not allow it; it used to work good before the last hassio update - so that now I must change the ip on the config file for this device, every time it goes offline.

Thankyou for your effort in this great software

javamahn commented 3 years ago

Any possibly of adding additional network options for autodiscovery? I have my HomeAssistant on my main network but my IoT are on a seperate Guest network

jonniepanda commented 3 years ago

Hi Guys - awesome work thanks for sharing this. Any news on the climate platform?

malpeli commented 2 years ago

How about an option to use HA's media player as a defacto microphone for music mode?

ChrisRonaasen commented 2 years ago

This issue is closed. Open a new issue or make a feature request (after checking that it hasn't already been mentioned) if you want to contribute or ask questions.

soooohowaboutthosedoorsensorsandcameras?

cloudbr34k84 commented 2 years ago

hi there is there any chance of getting Dc inverter Swimming Pool Heat Pump and wifi garage door opener. I can get all the information from Tuya Platform, and i can connect but i dont think this device is supported? Any help

JohanTess commented 2 years ago

Tuya Cat Litter Box Wifi (round model Wifi) Found following values 101 = on/off (device on/off) - switch 102 = Trigger manual cleaning - switch (how do I select a toggle switch?) 103 = Delay before start cleaning - value between 60 and 1800 - number (time in seconds) 104 = ? 105 = UV disinfection time - value between 60 and 1800 - number (time in seconds) 106 = ? value true/false but didn't find what trigger this state 107 = ? 1200 didn't find anything that changes this value 108 = LED ring on/off - switch 109 = Sleep mode on/off - switch 110 = Start time of sleep mode - 24h time format - 0 = 00;00, 60 = 01:00,...., 1230 = 20:30 111 = End time of sleep mode (same as 110 as format) 112 = ? value is showing 1 113 = ? value is showing 25 114 = Status of the device following values discovered Standby, Cleaning, Caking, Power Off (how to get the values is lovelace?) 115 = UV disinfection on/off - switch 116 = ? set to false 117 = Cat sand level - Values found Empty, Half, Full - (how to get the values is lovelace?) After filling up you need to push cat cand reset on the app...probably one of the ? is the trigger 118 = Error - 0 = no error, 2 = tray removed... unable to find other error codes 119 = N/A 120 = ? set to False

If anyone can give me some clues on what platform to use for the above and how to configure.... THX in advance.

boheme61 commented 2 years ago

Nedis WIFIPO120FWT plug with power-consupmtion, have 14 different DP''s ... how do i know which is what, i did get a "spec" out of iot.tuya.com, but doesnt tell everything, it only specifies 8 out of 14 ... but my problem is more what kind of "Platform" i should choose for the different ID's, i know initially "Switch" next ID is countdown_1 ( i asume switch ?) , next 4 ID's are most likely sensors (power, voltage, cur_current, add_ele) then i have ( cycle_time and random_time ), what "platform" to choose here ? , number, switch, select ? ... and then i have the rest, howto know what they are good for ? ............................................................................. "product_name": "Outdoor Smart Plug", "status": [ "status": [ "code": "switch_1", "dp_id": 1, "type": "Boolean", "values": "{}"

    "code": "countdown_1",
    "dp_id": 9,
    "type": "Integer",
    "values": "{\"unit\":\"s\",\"min\":0,\"max\":86400,\"scale\":0,\"step\":1}"

    "code": "add_ele",
    "dp_id": 17,
    "type": "Integer",
    "values": "{\"unit\":\"kwh\",\"min\":0,\"max\":50000,\"scale\":3,\"step\":100}"

    "code": "cur_current",
    "dp_id": 18,
    "type": "Integer",
    "values": "{\"unit\":\"mA\",\"min\":0,\"max\":30000,\"scale\":0,\"step\":1}"

    "code": "cur_power",
    "dp_id": 19,
    "type": "Integer",
    "values": "{\"unit\":\"W\",\"min\":0,\"max\":50000,\"scale\":1,\"step\":1}"

    "code": "cur_voltage",
    "dp_id": 20,
    "type": "Integer",
    "values": "{\"unit\":\"V\",\"min\":0,\"max\":5000,\"scale\":1,\"step\":1}"

    "code": "cycle_time",
    "dp_id": 41,
    "type": "String",
    "values": "{}"

    "code": "random_time",
    "dp_id": 42,
    "type": "String",
    "values": "{}"

............................................................................. Beside above i have "dp_id": 21 , 22 , 23 , 24 , 25 , 26

would appreciate help understanding which "Platform " to choose above

Future Suggestion / Improvement Would be nice to be able to "regret" (going back) in the gui, so old men who cant keep count, don't click add another entity, just to find out that i already configured all 14, and end up with 1 choice , the infamous X in the top right corner :(

lbijzeit commented 2 years ago

After days of trying to get things in home assitant I now notice that there isn't support yet for led controllers (stand alone) and for the MiBoxer WL-Box1 (2.4 Ghz Gateway). It would be fantastic if this would be supported by local tuya. Could it be put on the list of improvements?

marcokreeft87 commented 1 year ago

First of all, I love the integration! But the climate ( in this case an portable airco ) isnt working like the tuya integration. Top is local tuya, bottom is tuya integration

cloudbr34k84 commented 1 year ago

Is possible to add a new sensor to an already added device or do you have delete and start again?

rospogrigio commented 1 year ago

You need to delete the device and re-add it from scratch, sorry.

cloudbr34k84 commented 1 year ago

You need to delete the device and re-add it from scratch, sorry.

Feature request. Lol

MajaGithuab commented 1 year ago

after everything was working super fine I started having devices unavailable, IPs are fixed for all Tuya devices, it is showing online on the Tuya developer web page, I can control it through Tuya mobile App. I removed devices and add it again, removed the integration totally and added it again, it works for a while then it becomes unavailable.

Any advice ? I dont want to return to the Tuya cloud integration.

guiseco commented 1 year ago

You need to delete the device and re-add it from scratch, sorry.

Sorry, but wouldn't it be easier to be able to directly tweak the configuration file for a more precise adjustment?

FS1961 commented 1 year ago

Can you please add a way to save the configuration of the Tuya devices, like an export list function or something. I've had to rebuild this a few times from scratch so it would be nice to save the current config to a file with all the info. Thanks!

cloudbr34k84 commented 1 year ago

Hey I tried to start a LocalTuya DPS thread in HA community. Feel free to add yours there for now so everyone can benefit. https://community.home-assistant.io/t/localtuya-device-dp-config-settings-thread/458054/2?u=cloudbr34k

theundefined commented 1 year ago

I think it would be great to combine many different things in one place like documentation ;) I've prepared list for one my device (LSC Smart LED Flood light with sensor) on https://docs.google.com/document/d/1nv6GIfD81kXIyWxQ4I_gRBDBjMrCBfT3V7nIK2CuBqo/edit?usp=sharing

jmcollin78 commented 1 year ago

How do you delete a device with the LocalTuya integration (there is no delete option) ? Removing all DP is bad because you cannot get it back.

rospogrigio / localtuya

List of future improvements #15