localtuya.set_dp equivalent?

[pergolafabio]

Hi, didnt use the template, since its more a question...

I am converting all my devices from localtuya, to tuya-local
For one device, i need to manually set the DP , it isnt auto discovered , its a petfeeder, if i want to give my cat 5 portions i did in localtuya below, how can i do this in tuya-local?

      - service: localtuya.set_dp
        data:
          device_id: !secret tuya_petfeeder_id
          dp: 201
          value: 5

[pergolafabio]

also, when i add this device, i get the error below, this is my last device converting to tuya-local

2024-06-20 11:53:12.822 WARNING (MainThread) [custom_components.tuya_local.config_flow] Could not find device: XXXX
2024-06-20 11:53:40.547 ERROR (MainThread) [custom_components.tuya_local.device] Failed to refresh device state for Test.

[make-all]

It has never been an objective of this integration to provide the low level functionality that localtuya does, so there is no equivalent, and I have yet to see a genuine need for such an equivalent. In this specific case, a number entity should work.

[make-all]

If you turn on debug logging, and repeat the attempt, you may get more detailed information about the specific error that caused the connection failure.

[pergolafabio]

ok, i see this:

2024-06-20 11:59:10.152 INFO (MainThread) [custom_components.tuya_local.device] Setting protocol version for Test to 3.3
2024-06-20 11:59:15.422 DEBUG (SyncWorker_58) [custom_components.tuya_local.device] Test refreshed device state: null
2024-06-20 11:59:15.423 DEBUG (MainThread) [custom_components.tuya_local.device] Retrying after exception <class 'TypeError'> argument of type 'NoneType' is not iterable (0/3)
2024-06-20 11:59:15.423 INFO (MainThread) [custom_components.tuya_local.device] Setting protocol version for Test to 3.3

[make-all]

Test refreshed device state: null

This suggests that the device does not return any data at all. This integration is currently not able to support such devices.

[pergolafabio]

Is there a way to support it, how can I help with that? It's the only device left in my tuyalocal :-)

That way I can remove that integration...

[make-all]

Since the cloud assisted config was added a couple of releases ago, we probably have everything we need to skip the dps matching step now for devices that match known product ids. But it probably needs some refactoring of the config flow first. It will also require either local discovery or cloud discovery to be enabled to work - the former will not work if localtuya is installed, or on complex network configurations (such as devices on a separate subnet from the HA device), and the latter needs to be optional, as some users simply don't want to use the cloud.

[pergolafabio]

Ok, so what do you want me Todo? I still have localtuya installed , but I removed all devices one by one before adding them to tuyalocal...

I now added back my petfeeder back to localtuya...

Are there config / log files you need? Maybe from the IOT website?

[pergolafabio]

i also tried auto or other protocols

[pergolafabio]

when i add it to localtuya, i only need DP 201 , but i manually add it, since 201 isnt part of the "standard instuction set" ,
maybe below can be usefull?

  "data": {
    "device_config": {
      "friendly_name": "petfeeder",
      "host": "192.168.0.75",
      "device_id": "XXX",
      "local_key": "XXX",
      "protocol_version": "3.3",
      "enable_debug": false,
      "manual_dps_strings": "201",
      "dps_strings": [
        "201 (value: -1)"
      ],
      "entities": [
        {
          "id": 201,
          "friendly_name": "petfeeder_201",
          "platform": "sensor"
        }
      ],
      "product_key": "ibnk6keua0zzc2gr"
    }
  }
}

[make-all]

Standard instruction set is not relevant, as the local protocol always works with DP instructions. Standard instruction set seems to be some way to use common templates for various device types over the cloud protocol by ignoring minor variations.

[pergolafabio]

Standard instruction set is not relevant, as the local protocol always works with DP instructions. Standard instruction set seems to be some way to use common templates for various device types over the cloud protocol by ignoring minor variations.

ah ok, i wasnt aware of that

[pergolafabio]

I see there is an template for new device support, I will create one with all the necessary info, like DP ....