Hi,
Wondering if anyone else has encountered similar issues before.
I have a FTXV71WVMA unit and recently installed the BRP072C42 adapter.
I initially set up the device in the Daikin app, which went smoothly.
The app forced upgrading firmware to 1.16.0 during the setup.
When trying to add the unit into the Daikin integration, it would constanly show
“unknown error” despite trying various combinations of using with/without the API key.
Then decided to test connectivity to see what ports it was on.
netcat showed that port 80 was closed, so tested with https endpoints.
Initially curl -k was failing returning UnsafeLegacyRenegotiation
but managed to get past that.
curl -k -H “X-Daikin-uuid: 669bf8b09ad04567a458b5462f62f888” --head “https://192.168.50.41/common/register_terminal?key=XXXXXXXXXXXXXX”
curl -k -H “X-Daikin-uuid: 669bf8b09ad04567a458b5462f62f888” “https://192.168.50.41/common/basic_info”
This was able to return some results.
After coming across a post being able to fix things after changing region - I thought to give it a try.
using curl with /common/set_regioncode?reg=us
In doing so, this made an odd change.
After the region change, the device was no longer listening on port 443, but instead reverted back to port 80.
I was able to then proceed to add the device into HomeAssistant without using the API key.
However, I am finding it strange that the device can no longer be added back to the Daikin App, and even factory resetting the device would result in the App failing to detect the device correctly, and the only way to even get it back connected to the local network was via WPS.
I’m guessing the main drawback of having the device only in home assistastant is the lack of Fan control options.
Currently there is only 6 entities - Climate, Power, Streamer, Compressor Frequency, Inside Temp and Outside Temp.
However, from playing around with the App, I was able to control the fan speed and movement, so I dont think its a limitation of the device itself.
Any help would be appreciated.