[!] Unable to decrypt device reponse. PSKKEY/AUTHKEY do not match device.

[krishgcek]

I want to change the device again after the first cut. but I am getting,

[!] Unable to decrypt device reponse. PSKKEY/AUTHKEY do not match device.

[Cossid]

That means you're using an incorrect profile. You must use the one you used to originally cut the device.

[krishgcek]

how to change the profile as the initial one does not work

[Cossid]

One that you chose caused the device to receive an A- AP SSID prefix, that was a working profile. After the device already has the A- prefix, we can't apply the safety check to exit telling you it's a wrong profile, and when a wrong profile is used, you get PSKKEY/AUTHKEY errors.

You select the profile when you run CloudCutter.

[krishgcek]

I am getting the ssid and the cloud cutter is working.
but during the last stem I get some dns requests like this,
un 13 04:31:48 dnsmasq-dhcp[15]: 1220565492 DHCPACK(wlx001611009b0d) 10.42.42.40 b8:06:0d:19:26:05 wlan0
Jun 13 04:31:48 dnsmasq-dhcp[15]: 1220565492 requested options: 1:netmask, 3:router, 28:broadcast, 6:dns-server
Jun 13 04:31:48 dnsmasq-dhcp[15]: 1220565492 next server: 10.42.42.1
Jun 13 04:31:48 dnsmasq-dhcp[15]: 1220565492 sent size: 1 option: 53 message-type 5
Jun 13 04:31:48 dnsmasq-dhcp[15]: 1220565492 sent size: 4 option: 54 server-identifier 10.42.42.1
Jun 13 04:31:48 dnsmasq-dhcp[15]: 1220565492 sent size: 4 option: 51 lease-time 12h
Jun 13 04:31:48 dnsmasq-dhcp[15]: 1220565492 sent size: 4 option: 58 T1 6h
Jun 13 04:31:48 dnsmasq-dhcp[15]: 1220565492 sent size: 4 option: 59 T2 10h30m
Jun 13 04:31:48 dnsmasq-dhcp[15]: 1220565492 sent size: 4 option: 1 netmask 255.255.255.0
Jun 13 04:31:48 dnsmasq-dhcp[15]: 1220565492 sent size: 4 option: 28 broadcast 10.42.42.255
Jun 13 04:31:48 dnsmasq-dhcp[15]: 1220565492 sent size: 4 option: 3 router 10.42.42.1
Jun 13 04:31:48 dnsmasq-dhcp[15]: 1220565492 sent size: 4 option: 6 dns-server 10.42.42.1
.
It is not ending. sometimes the the device wont connect back. Then I used the smart home app to connect it again to cloudcutterflash access point. Then I will get PSKKEY/AUTHKEY errors

[Cossid]

https://github.com/tuya-cloudcutter/tuya-cloudcutter/wiki/FAQ#my-device-gets-stuck-after-dhcp-what-can-i-do

Yeah, any device that isn't the device being exploited that makes web request will get PSKKEY/AUTHKEY errors, and you can just ignore those, you should be able to determine by the hostname/IP communicated through DHCP.

Some devices are really tricky to get connected, make sure they are as close to the CloudCutter AP as possible.

[krishgcek]

I am still confused. can I change the device type after cutting the device. I want to change it from generic to wipro :(

[Cossid]

CloudCutter doesn't assign brands to a device, only schemas, which can differ slightly from one similar product to the next, but usually have the same base functionality.

The important factor is you use the firmware profile attached to the device in cloudcutter. All that are the same are compatible with each other.

[krishgcek]

i was able to solve it by using antela-spl-w-ty-pm-fr-ry-plug-with-energy-monitoring-cb2s-v1.1.8