-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lighthouse power state reports #40
Comments
i am aware of one such state, the state where the motor is still on, but the lasers are off. the valve provided power management interface calls this state 'standby' while the current powered off state is called 'sleep' https://this-is-a.stale-me.me/i/easn.png i can not currently access this powerstate due to the windows 2004 bug: https://steamcommunity.com/app/250820/discussions/3/1639789306584486263/ |
Despite saying an update is necessary, SteamVR doesn't offer to update them even when connected via USB. Power management commands sent from the app work as expected. Seeing the same results on my Samsung S10e with a custom Android 10 ROM as well as an old Moto E4 on 7.1.1. |
After booting into Windows, Steam was happy to update the base stations. Updated one of them to the latest (3008), and Lighthouse PM now detects its current state with no issues. |
App version: 1.2.0 It reports state 0xff both when on and when in sleep mode. |
App version: 1.3.1 So far nothing has helped communicate with the lighthouse, any ideas of what to try to troubleshoot? |
App version: 1.3.1 Lighthouses work perfectly fine at parents place, then when I move them back to mine, they suddenly don't respond to any Bluetooth signal |
App version: 1.3.1 This issue was worsened with the update that introduced Material You colors. Before the update, I was still able to turn my lighthouses on, but now none of the power options seem to be functioning. Running on Samsung S21 Ultra SM-G998B/DS with OneUI 6.0 (Android 14) |
App version: 1.3.1 |
Leave the reports for unknown power state here.
If the power state is reported as
0xFF
then the app doesn't know yet what the state is, give it a bit more time.If this still appears look at #32.
Please leave the reports in the following formate:
The text was updated successfully, but these errors were encountered: