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
Is your feature request related to a problem? Please describe.
No.
Describe the solution you'd like
I would like a field in the GUI settings that allows me to change the default sleep time (~8s currently)
Describe alternatives you've considered
Some new button command (short/long press) that disables/enables auto-sleep.
Additional context
Upon entering the field of a reader chameleon "wakes up". When chameleon "wakes" it takes some time to before the communication with the reader stabilizes. This delay between the "waking" and the stabilization seems to be detectable by the reader in question. Upon detecting chameleon the reader reboots. However, if the chameleon is already awake (by pressing one button or keeping it connected via bluetooth to some device) before entering into the reader field, the communication works as intended.
The text was updated successfully, but these errors were encountered:
If you implement this option in firmware or get someone to implement it, id be happy to implement it in the GUI, but afaik such an option doesn't exist in firmware.
Is your feature request related to a problem? Please describe.
No.
Describe the solution you'd like
I would like a field in the GUI settings that allows me to change the default sleep time (~8s currently)
Describe alternatives you've considered
Some new button command (short/long press) that disables/enables auto-sleep.
Additional context
Upon entering the field of a reader chameleon "wakes up". When chameleon "wakes" it takes some time to before the communication with the reader stabilizes. This delay between the "waking" and the stabilization seems to be detectable by the reader in question. Upon detecting chameleon the reader reboots. However, if the chameleon is already awake (by pressing one button or keeping it connected via bluetooth to some device) before entering into the reader field, the communication works as intended.
The text was updated successfully, but these errors were encountered: