v0.6.3 — Correct MQTT broker, mask account address in logs

Two small fixes, both prompted by a network capture of the official Lockly app that a user on issue #1 was kind enough to run.

Connects to the right MQTT broker

The app connects to the broker address hardcoded in its own config. This integration preferred the address the getHeartbeatTime API call returns instead, and that address refuses the connection outright with rc=5.

Against the correct broker the connection is accepted, and it is the subscription that gets refused. That is further along, and it is where the remaining unknown actually lives.

This does not make real-time push work. The subscription refusal is still the blocker, and state still updates at startup and after commands from HA. What changes is that the integration stops sending connection attempts at a host that rejects them, and the logs now show the real failure rather than one caused by talking to the wrong server.

Correction, added after release: these notes originally said your rc=5 messages would be replaced by a subscription-refused message. That was wrong. This release corrects the broker address but leaves a second problem in place, an invented client identity in the broker username, so on its own it still fails at rc=5. That part is fixed in v0.6.4 — take both releases together to see the change described here.

Masks the account address in logs

The MQTT connect line logged the broker username, which is your account email. Debug logs get pasted into issues as a matter of course, because this project asks for them, and one address has already ended up in a public thread that way.

The address is now reduced to one character and its domain, which is still enough to tell two accounts apart in a log. Only the log line changed; the credentials sent to the broker are unchanged.

Unchanged

Everything else is as in v0.6.2. Real-time push does not work, silent polling needs hub firmware build 422 or newer, and locks with no hub are unsupported.