Open deadman96385 opened 2 years ago
@deadman96385 To help debug, could you do the following:
_load_devices
in this halohome library to print(response)
after the _make_request
callimport halohome; import asyncio; asyncio.run(halohome.list_devices("YOUR_EMAIL", "YOUR_PASSWORD"))
list_devices
(removing passphrase and any other private data)I suspect this is an issue with the way the device_id is calculated within this library, which is very unclear from HALO's API. Some magic values I used may be specific to either my account or the halo products I have, but it shouldn't be too difficult to figure out what's going on.
Here is the two outputs you requested https://gist.github.com/deadman96385/3d0006d1fa5b6e64f2f1a8b28f653c8a
Also either sometime this week or next weekend I will have some other Halo lights to test. I won a bunch of them via a promotion so we will see how they go.
Hello, I have been working on trying to get this implementation working for my halo lights. The only change i've done to the source is change the product_id to 162. This allows my lights to show up and controlling them does work. All data for each light in core.config_entries lines up. I verified the friendly name and mac address in the avi-on app. But when I turn on a light in home assistant it turns on the light one up in the list. Using the example below if I turn on Mr m6, Bath ne will be turned on in instead. I am using the latest copy of your home assistant component loaded as a custom component pointing at my copy of the library with the id change.
Edit: Here is the data of me turning on Mr m6 via home assistant
First one decrypted (2DCAE200803B27672FC3C8EE4C0479E9465C92C9):
Second one decrypted (E66D129A8014C6930CF436D7795288457AEAA49E)