Skip to content

Conversation

dcapslock
Copy link
Collaborator

@dcapslock dcapslock commented Sep 2, 2025

Closes #956
Closes #565
Fixes #760

@dcapslock
Copy link
Collaborator Author

Tested on iOS.

@RomRider
Copy link
Collaborator

RomRider commented Sep 15, 2025

It doesn't seem to do anything different on Android whatever the setting (I get the default vibration) while using the Home Assistant Companion App. Isn't the action firing an event because I always get a vibration even if not set?
Also, it seems there's no way to disable haptics for a specific button. This is quite old and I don't remember how it's supposed to work 🙃

@dcapslock
Copy link
Collaborator Author

Checking this out. Looks like "haptic" event is not being intercepted so the regular Frontend haptic is forwarding as well as the custom (seen in ADB debug messages for emaultor). If you try a custom action which is not toggle you will likely get the correct haptic. I will post back findings.

@dcapslock
Copy link
Collaborator Author

Will need a different approach. Will close this PR and submit new to not have a messy commit history.

@dcapslock dcapslock closed this Sep 16, 2025
@dcapslock dcapslock deleted the haptics branch September 20, 2025 00:33
@dcapslock dcapslock restored the haptics branch September 30, 2025 03:02
@dcapslock
Copy link
Collaborator Author

Reopening.

@dcapslock dcapslock reopened this Sep 30, 2025
@dcapslock
Copy link
Collaborator Author

Frontend PR#27251 created to allow for capturing events at window level correctly for "haptic" event.

@dcapslock
Copy link
Collaborator Author

Frontend PR#27251 created

This has been approved and merged to Frontend dev.

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