If I do an ls /dev. I see that hidraw0 is always there even if touch is not plugged in.
hidraw1 and hidraw2 go away when the touch controller is not plugged in. hidraw1 and hidraw2 come back when the touch controller USB is plugged back in.
The act of unplugging and replugging the USB does get the touch working.
executing these command in the hostOS does also get the touch working
systemctl stop balena-supervisor
systemctl stop balena
systemctl start balena
systemctl start balena-supervisor
Here is a link to the logs from the journalctl commands:
So so far there are three ways to get the touch working after a container rebuild:
physically unplug and replug the USB
run the systemctl stop and start commands
reboot the device from the Balena dash board.
If I run a balena push --nocache for the cli tool on my computer I can get the touch to fail every time after the new container is brought up.
I am using the “less than 10 devices” free plan for all my testing thus far. You had mentioned pushing to “open-balena”. Just for clarity not sure if that refers to the service I am using on the regular Balena.io website.
Thanks very much.