LSC Pet feeder - setup fails, received payload null in init, typeError NoneType not iterable

[jdeneef]

I have a LSC Pet Feeder, which some seem to get connected, but for me this fails. Tried with and without app (force close) with and without internet access, reading with tinytuya, following #451, etc. Simply fails with typeError NoneType not iterable. I seem to get some kind of connection when I'm simultaneously reading with tinytuya while setting up in homeassistant, but after setting up all sensors are unavailable in ha. Any help appreciated!

Debug log see below, seems to me that it somehow is receiving incorrect/empty answer, received payload null. Via tinytuya I can get some respons but only status report on 103 with some other updates .. Via Tuya IOT portal I can extract the DPs, see attached file.

2024-12-17 14:20:41.861 DEBUG (SyncWorker_14) [custom_components.tuya_local.device] Test refreshed device state: null
2024-12-17 14:20:41.863 DEBUG (MainThread) [custom_components.tuya_local.device] Retrying after exception <class 'TypeError'> argument of type 'NoneType' is not iterable (1/3)
2024-12-17 14:20:41.863 INFO (MainThread) [custom_components.tuya_local.device] Setting protocol version for Test to 3.3
2024-12-17 14:20:41.867 DEBUG (SyncWorker_11) [tinytuya.core] status() entry (dev_type is device22)
2024-12-17 14:20:41.868 DEBUG (SyncWorker_11) [tinytuya.core] final payload_dict for 'xxxxxxx' ('v3.3'/'device22'): {1: {'command': {'gwId': '', 'devId': '', 'uid': '', 't': ''}}, 7: {'command': {'devId': '', 'uid': '', 't': ''}}, 8: {'command': {'gwId': '', 'devId': ''}}, 9: {'command': {'gwId': '', 'devId': ''}}, 10: {'command': {'devId': '', 'uid': '', 't': ''}, 'command_override': 13}, 13: {'command': {'devId': '', 'uid': '', 't': ''}}, 16: {'command': {'devId': '', 'uid': '', 't': ''}}, 18: {'command': {'dpId': [18, 19, 20]}}, 64: {'command': {'reqType': '', 'data': {}}}}
2024-12-17 14:20:41.868 DEBUG (SyncWorker_11) [tinytuya.core] building command 10 payload=b'{"devId":"xxxxxxx","uid":"xxxxxxx","t":"1734441641","dps":{"1":null}}'
2024-12-17 14:20:41.872 DEBUG (SyncWorker_11) [tinytuya.core] sending payload
2024-12-17 14:20:41.873 DEBUG (SyncWorker_11) [tinytuya.core] payload encrypted=b'000055aa000000130000000d00000087332e33000000000000000000000000350afe0c3d1cffd85f9a158af715edd235ba6df1ce80104aad39f12b6f38f81915a44582c450991ad16cdd11d7aa41ac0766dc7c79f1d32d85fa426bbed6a680e51ca4b81faa93bd3bd500216c441b649350b9ff791174209df2a02e01f073b8366896e10220a793f069cad474130510d97eee0f0000aa55'
2024-12-17 14:20:41.885 DEBUG (SyncWorker_11) [tinytuya.core] received data=b'000055aa000000130000000d0000000c00000000e470301b0000aa55'
2024-12-17 14:20:41.885 DEBUG (SyncWorker_11) [tinytuya.core] received null payload (TuyaMessage(seqno=19, cmd=13, retcode=0, payload=b'', crc=3832557595, crc_good=True, prefix=21930, iv=None)), fetch new one - retry 0 / 1
2024-12-17 14:20:46.891 DEBUG (SyncWorker_11) [tinytuya.core] status() received data=None
2024-12-17 14:20:46.891 DEBUG (SyncWorker_11) [custom_components.tuya_local.device] Test refreshed device state: null
2024-12-17 14:20:46.894 DEBUG (MainThread) [custom_components.tuya_local.device] Retrying after exception <class 'TypeError'> argument of type 'NoneType' is not iterable (2/3)
2024-12-17 14:20:46.894 ERROR (MainThread) [custom_components.tuya_local.device] Failed to refresh device state for Test.
2024-12-17 14:20:46.895 INFO (MainThread) [custom_components.tuya_local.device] Setting protocol version for Test to 3.3

firmware version (might be that newer firmware disallows connections?)

    "current_version": "2.1.60.735"
    "model": "5525000400",
    "name": "Pet Feeder",
    "product_id": "knpje5j2wsqlkhna",
    "product_name": "LSC Pet Feeder with Camera",
    "sub": false,
    "icon": "smart/icon/ay1541056239985fDGjj/7b6724bac30cc62c49e32cff202cfd9a.png",

fwiw attached (to reduce post length):
LSC_Pet_Feeder.json

Returned category is "sp" Smart Camera, which should probably be a combination of "sp" Smart Camera and "cwwsq" Pet Feeder, guessing that's mostly cosmetics?

[make-all]

Have you tried protocol version 3.2?

Often others finding their device is not returning any values most of the time have found that it is because their device uses protocol 3.2, which appears the same as 3.3 during device discovery, but requires a couple of different commands to be used to work properly. The device22 workaround (which has been auto-detected for your device) is for devices that require one of those different commands, but not the other, so are not true 3.2 protocol devices.

[jdeneef]

Hi @make-all, Thanx for checking! I indeed tested with all 3.x versions including 3.2. Same result. With tinytuya I had some success with 3.2 but setting up in hass did not work, receiving DPS: 103 and sometimes others, but only after power cycling of the pet feeder. Other options I can test? Will try power cycle + register with 3.2 immediately after, not sure if I tested that.

[jdeneef]

Tested again from clean start with 3.2, and now this work! Thanx! At least I got to some feed rounds going, primary function is working. Trying to figure out what config to use, since the dps are not all documented, will compare with other petfeeders to create a new config. Also no camera yet, will look into the docs to find how to setup, any tips on the camera are welcome!