- carlo64 a écrit:
- You can try the simulation of the buttons like this:
[...]go to the /usr/openkarotz/Extra folder and run
to simulate a click and
to simulate two clicks
Great ! Perfect commands to diagnostic a faulty hardware
I've gave it a try and here the results:
- The script is sometimes messing with the physically pressed button, but not with the soft generated (as far as I try).
- Soft, or physical, 3 clicks doesn't start or stop the script, and sometimes 3 physical
clicks starts the connexion loop.
- I didn't see any special error message while in the error loop.
Maybe an issue with the events management config ?
After a while I decide to reset the karotz to factory, re-install openkarotz (with his frequent issues at firmware update), and nabemu.
The result (after 4 or 5 reset due to openkarotz and wifi issues) is a perfectly working script !
Thanks for your work and your support !
I think i may have messed with the properties and/or ownership of some system files when I have launched the selfextract script from /usr/karotz (the default telnet directory) instead of /usr/openkarotz...
As said in a previous post: I put the file in the correct folder and I launched it with /usr/openkarotz/selfextract.it.bsx instead of ./selfextract.it.bsx; skipping the not-documented "cd" command (and believing it will works the same despite my telnet's active directory); looks like the script is active directory dependant...
I also noticed you have push a updated nabebu.py script to your github, so I gave it a try but I haven't seen a difference yet.
I think I will try to learn more about nabaztag plugins to try to understand a little more your script and eventually add others plugins compatibility with openjabnab.New personal goal
: the change of led pulse from openjabnab admin page (it's actually showing an empty selection list)
But it will be for another day.