LocalTuya discovers different device ID than Tuya Developer Platform

setting up Tuya is a pain. My Cat Feeder works fine with the standard Tuya app, but in the standard (cloud) integration, it has almost no sensors or control. So I installed local Tuya using HACS, created an account on the Tuya developer portal and created a project and finally linked my tuya app using the QR code as described in the instructions. It lists my Cat feeder with a device ID and even shows the online status. So far so good.

But besides the deviceID I need to have a local key. Well, the instructions say:

You must have your Tuya device’s Key and ID in order to use LocalTuya. The easiest way is to configure the Cloud API account in the integration

So I interpeted that as: when you fill in your account details in the integration, it will get the device ID and Key itself. So I configure my account details and clicked add device in the integration. It immediate shows a device (i have yet only one device configured) The IP address of that device matches my Cat Feeder, and press next. Then I have to fill in a name and… a local key… I noticed that the device ID that is discovered is totally different !

I tried the instructions linked from the article to tinyTuya and that results in detecting the devivce with the same device ID as the Tuya Developer Platform and the same IP adress that was detected by localTuya… Also even logs de local key!

hen entering the details found in tinyTuya, I got the message "Connection to device succeeded but no datapoints found, please try again. Create a new issue and include debug logs if problem persists.’

Not sure what happened here. Any suggestions?