-
Notifications
You must be signed in to change notification settings - Fork 402
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
Set sleep between card reads #196
Comments
Hi @gizmo21 |
This question still bothers me. It would be possible add an additional check in the Reader() class to allow a re-triggering of the same UUID after a certain interval, but I don't like the idea to do this for all UUIDs. I would prefer an additional check if that UUID should/could be triggered multiple times because the only use-case I can think of atm are the volume change or start/stop toggles. But that doesn't justify to trigger all UUIDs multiple times imho... |
On the other hand it should be possible for all UUIDs since the state can also be changed within the web interface, e.g. if you start a song via card and stop it inside the interface it wouldn't be possible to start it again with the card. I will tinker around with this interval inside the Reader() class for the RDM6300 module - if it's fine I would make a suggestion for default reader. This seems to be only an issue for "fast" readers that trigger multiple times per second. |
Another way of approaching this problem might be through the service daemon that enables the process: |
I like the idea to implement some sanity checks for valid UUIDs in the daemon_rfid_reader.py and allow a re-triggering of the same UUID only every 1 second. That may already do the trick. |
Thanks for looking into this. To make it clear I really don't want an UUID trigged only once. For my case "re-triggering of the same UUID only every X.x seconds" would be way enough. |
Well, everytime rfid_trigger_play.sh is triggered the playback stops and/or starts stuttering. That means even a 1sec delay is annoying if the card is placed for too long above the reader. Probably a good option would be to replace the shell-script with python-mpd2 and make a list which UUIDs are registered for "multi-trigger". Latter could be achieved by creating files like the shortcuts in another directory for control-commands. Only these would be allowed for "multi-trigger". The files could be easily gathered (e.g. glob) and it wouldn't break the web-interface and samba access to those files/settings. |
Hi, i have the same RFID Reader which reads the card or chip multiple times in a very short time, too. I had the idea to use the chips under a character like the tonies from Toniebox. Is it possible to allow it to stand on? Thanks for input. |
yes it is possible, as the kid also lays the cards on the box while hearing, but as you know sometimes it reads twice so it stops or three times then it is OK. Another guy with the neuftech even suggested to use the LED signal "green" to implement the tonie-like behaviour: #62 Which figures would you suggest, I thought it would be easier to find some appropriate. |
Hi gizmo21, thanks for the link to issue #62. I will try it. I don‘t wanna use the original tonies. Some figures like playmobil Lego etc are good enough. I have a lot of chips an want to use them to put under a platform as a wooden circle. The same size of the circle i have to mill out in the box. So the box will be wooden :) |
Hi @ottk3 @gizmo21 |
It'll take some time to update to a new pull from 1.0 as I have to merge my own changes and test if smb/symlink is still working. |
My RFDI reader (Neuftech USB RFID Reader "usb-HXGCoLtd_27db-event-kbd" seems to be very sensitive and thus it happens that the card is read multiple times just by lowering down the card to the reader.
Would it be possible to add an option for a sleeptime after a cardread (like 0,5 or 1s) so that even an repeated hardware detect of the same card is not resulting in a new command.
Or is it already there or could I easly add it in the code (utilizing last.played timestamp??), perhaps you could just point me to.
The text was updated successfully, but these errors were encountered: