Skip to content

Conversation

@oakamil
Copy link
Contributor

@oakamil oakamil commented Jan 27, 2026

Currently only allowed for DIY devices. A few notes:

  • Currently selected device to control is stored in a local shared preference
  • Selecting another device to control is possible if we can't establish connection for 5 seconds
  • WiFi control is only allowed on 192.168.4.1
  • Bluetooth control allows any paired device at the moment. It's possible to filter devices using the Cedar control UUID, but there are edge cases that would be hard to deal with since the service UUIDs are only pulled at the time of pairing
  • Cedar Aim will try to handle various edge cases - missing permissions, Bluetooth off, etc. But if user repeatedly denies permission they will have to go to their phone settings to grant them. Cedar Aim currently doesn't walk them through that edge case

Omair Kamil and others added 10 commits January 6, 2026 22:34
Also update colors for device selection dialog to match theme.
There's a bug in that flutter library that will cause a crash in some cases when permissions are missing.
- Ensure correct permissions are requested based on Android SDK
- Try to turn on Bluetooth if it's off
- Don't cleanup unless 5 seconds have passed since connection start to reduce calls on expensive operations
- Assorted fixes
@oakamil
Copy link
Contributor Author

oakamil commented Jan 27, 2026

On filtering devices based on Cedar UUID, this isn't supported by the flutter_blue_classic package and might need custom platform channels to do. So I don't have plans to add that at this time.

Prior to connecting to a Cedar device it's unknown if the device isDIY or not.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants