You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 28, 2024. It is now read-only.
And was able to use nRF Connect for Mobile to discover and successfully send control commands to the Happy Light LED strip in my daughters room. So I was going to write a custom integration with shell scripts as described earlier on in the above. But then saw you already had. Which is awesome!
But no bluetooth LE monitoring app that I've found actually lists the MAC address of the device! Without which I'm dead in the water. What software can I use to get the MAC for LED controller?
How are folks discovering the MAC address of the device they want to control?
The text was updated successfully, but these errors were encountered:
I found 'hcitool lescan' on linux spat out a mac address for the device. But when I try and use that with gatttool I get an 'Invalid handle' error and when I try and use it to setup this integration it fails and the logs has a 'Error getting status: No device found for address ' error.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I followed instructions and links here:
https://community.home-assistant.io/t/controlling-a-bluetooth-led-strip-with-ha/286029/17
And was able to use nRF Connect for Mobile to discover and successfully send control commands to the Happy Light LED strip in my daughters room. So I was going to write a custom integration with shell scripts as described earlier on in the above. But then saw you already had. Which is awesome!
But no bluetooth LE monitoring app that I've found actually lists the MAC address of the device! Without which I'm dead in the water. What software can I use to get the MAC for LED controller?
How are folks discovering the MAC address of the device they want to control?
The text was updated successfully, but these errors were encountered: