Closed jmasarweh closed 10 months ago
Can you try with debug flag like $ RUST_LOG=daikin_homekit=debug daikin-homekit
and paste whole log
here you go:
[$ daikin-homekit % RUST_LOG=daikin_homekit=debug daikin-homekit [2023-10-24T11:27:17Z DEBUG daikin_homekit::discovery] discovering daikin device from 192.168.1.151:30000 to 192.168.1.255:30050 [2023-10-24T11:27:18Z INFO daikin_homekit::discovery] found daikin device at 192.168.1.2: Living Room [2023-10-24T11:27:18Z INFO daikin_homekit] config file location: FileStorage { dir_path: "/Users/jamil/Library/Application Support/daikin-homekit" } [src/daikin.rs:49] resp.status() = 404 Error: http responded with non-200 status code: 404 Not Found
Seems like the ip range starts at 151. instead of 2, since 1 is assigned to the router usually....?
Seems like the ip range starts at 151. instead of 2, since 1 is assigned to the router usually....?
It doesn't matter I think. 404 error at first request shown in the log means that an API endpoint is unavailable.
Which model of daikin AC do you use?
Try cargo run --example discovery
and look at the endpoint. And then, curl -v
it and check the response.
It is a BRP069C4x (2023 model). Curl -v seems to connect the host on port 80, but there is no GET/ response on that endpoint /dsiot/multireq... (404 not found) Seems like my unit's gateway is not compatible with calls outside of the Daikin App...?
Seems like my unit's gateway is not compatible with calls outside of the Daikin App...?
I think so, too. I don't have some info about BRP069C4x but an issue cbrandlehner/homebridge-daikin-local#123 tells me that it has only cloud API ;)
You're right, and thanks a lot for the support and assistance. Cheers!
When executing Step 3 -
$ cargo build --release
fails with:Same error when executing
$ cargo run --example compatibility_check 192.1.1.XX
on macOs Sonoma 14.0 / M1 homebrew Latest rust/cargo.