Smanar
Smanar
Can you take a look direclty in the API to see if it's fine. Using Phoscon/help/API information/sensors/ID ? You have deleted the device before using the new DDF ? Else...
`curl -H 'Content-Type: application/json' -X PUT -d '{"devicemode":"click"}' http://IP:PORT/api/KEY/sensors/ID/config` IP and PORT are the same used to access Phoscon KEY is an API key, can use the same used by...
The DDF create a sensor too, the ZHASwitch, it will have as UniqueID a4:c1:38:9e:47:bb:e5:ad-01-ef00
>This request worked and the config changed It mean the value is changed on the API ?
Here I don't have idea, all seem fine. Perhaps with some logs with flag "info" + "info_L2" + "DDF" when try to set the option and an action on HA.
The API is probably updated by the request, not the return. On logs we can see the "write" request but never the "parse". In fact there is never "parse" request,...
Still no logs starting with "TY_DATA_" ?
And you are right, there is 2 other devices that can be clone of your device _TZE200_2aaelwxk / TS0601 _TZE200_kb5noeto / TS0601 We can try the modified DDF ``` {...
The device is not reconised ? The value is not updated when there is a detection ?
Can you give your manufacture name ? there is clone ATM.