This is great! I’ve been meaning to reverse engineer the API for a while but haven’t had the time. Biggest issue for me on this is that AC Infinity seems to be stuck in the early 2000s and don’t have an SSL cert on this API, which means your username/password are getting sent over plaintext to the API from the mobile app and from this integration.
NOTE: Not faulting you, just making sure people are aware of the security risks this poses now that it’s known to the world . I don’t even want to use the app after knowing this lol
Hi there,
Question about the wifi MAC address on the 69 Pro.
I can’t see anywhere on the iOS app or on the hardware controller itself to find the MAC address. I am using this on a massive network with well over 100 devices on the network. Nothing shows up with anything obvious named like ACinfinity or 69Pro in the network client list. I did see that other users in this thread did start their found MAC address’s with 34:85:18… and I did find something on my network that starts with that, called “expressif”. Does this line up with what other users have found? I asked AC Infinity tech support via phone and email and they both gave a collective “i dunno” to my question . I am ready to try this package but want to make sure I am connecting to the right device on my network. Thank you !
Matthew
I’m trying to add a pro 69 controller using hunterjm’s hacs repo. Ive been able to get as far as having HA see the controller, but then get that keyerror. I made a couple light tweaks to coordinator.py to see if i could get it to give me more detailed errors and this is what i came up with:
2024-06-23 16:50:44.718 WARNING (MainThread) [custom_components.ac_infinity] Missing or empty manufacturer data in advertisement: AdvertisementData(local_name='ACI-E', service_uuids=['00001800-0000-1000-8000-00805f9b34fb', '00001801-0000-1000-8000-00805f9b34fb', '0000180a-0000-1000-8000-00805f9b34fb', '0000fe59-0000-1000-8000-00805f9b34fb', '70d51000-2c7f-4e75-ae8a-d758951ce4e0'], rssi=-50)
It looks like the fan isnt transmitting ‘manufacturer data’, and so the code is puking, but im not sure how to fix it or what to do about it. I’ve tried to manually turn on bluetooth scanning using the command line, ive even been able to ‘connect’ to the controller using the commandline, but seemingly no matter what I do I can’t get it to add the integration
okay im not 100% sure what i did to fix it, but it was some combination of “connecting to the device manually via command line using the bluetoothctl tool” and then restarting home assistant.
moving back to the stock coordinator.py broke it again.
using my debug version gets me past the errors for onboarding the integration, but once its attached its pretty flaky. it doesnt read the fan speed correctly, it has a lot of trouble turning on and off.
i get the impression ac infinity may have changed something with this most recent firmware update.
hunterjm, thank you for working on the code for this. I have an AC Infinity Airtap T6 vent booster and it works with your code after a few small modifications. I had to jump out the sections of code that are expecting a device model returned when initially setting up the temperature sensor and fan devices. I hard-coded my preferred fan speed into the python script because the dashboard tile doesn’t have an option to set the fan speed. The “fan off” function does not work most of the time. I kept getting an error telling me that I need to set a fan speed between 0 and 10, so I just set the fan speed to 0 in the automation scripts when I want to turn it off. Now Home Assistant turns on/off the vent booster with the AC and Heat instead of triggering off a setpoint threshold of the unreliable temperature sensor on the unit (it would trigger on and blow hot air when the sun was shining on it or it would trigger on and blow cold air in during a cold morning). Again… thank you!!!
. I don’t even want to use the app after knowing this lol 
. I am ready to try this package but want to make sure I am connecting to the right device on my network. Thank you !