e.g Android with PineNote, relatively easy, then trickier due to the lack of screen (and virtual keyboard) e.g Ricoh Theta V (and still rely on Termux and scrcpy) to potential e.g Flipper to probably infeasible e.g Monocle or PineTime yet that should still be considered otherwise, relying on e.g BT via an existing peer.
e.g Android with PineNote, relatively easy, then trickier due to the lack of screen (and virtual keyboard) e.g Ricoh Theta V (and still rely on Termux and scrcpy) to potential e.g Flipper to probably infeasible e.g Monocle or PineTime yet that should still be considered otherwise, relying on e.g BT via an existing peer.
Could provider a route, e.g `/localsatellites`, for satellite devices that can't become peers proper, e.g BT devices
For example with the monocle e.g https://twitter.com/utopiah/status/1651089075904868352
Unfortunately it seems impossible to get a keyboard on screen or even via BlueTooth. Consequently impossible to install and start sshd.
What is surprising is that sending keyevent via adb works but only for some, namely input keyevent "KEYCODE_HOME" does work but nothing else. Not keycode 108 that should bring up the virtual keyboard not even 29 that should put in the letter 'a'. Also to consider is that seeing a virtual keyboard in any app, starting by Termux but also in the home screen, via scrcpy seems impossible.
Ricoh Theta V should have been the usual Android setup, like the PineNote
1. install Termux via adb or even just fdroid
1. setup ssh https://wiki.termux.com/wiki/Remote_Access
1. install Termux:boot https://wiki.termux.com/wiki/Termux:Boot
1. connect to it then run usual steps, e.g https://git.benetou.fr/utopiah/offline-octopus/src/branch/master/cloudinit
Unfortunately it seems impossible to get a keyboard on screen or even via BlueTooth. Consequently impossible to install and start sshd.
What is surprising is that sending keyevent via adb works but only for some, namely `input keyevent "KEYCODE_HOME"` does work but nothing else. Not keycode 108 that should bring up the virtual keyboard not even 29 that should put in the letter 'a'. Also to consider is that seeing a virtual keyboard in any app, starting by Termux but also in the home screen, via `scrcpy` seems impossible.
Tried [run-as-termux.sh](https://gist.github.com/goisneto/4e0a9c7c8cf6f6fc86fb96b454384c57) with a debuggable apk from Github but failed, maybe root required for file permissions. Also tried https://github.com/termux/termux-app/wiki/RUN_COMMAND-Intent as mentioned in https://github.com/termux/termux-app/issues/924 but requires https://github.com/termux/termux-tasker#allow-external-apps-property-optional which can't be setup headlessly.
see also https://nitter.net/utopiah/status/1746459313151848517 as a potential ZigBee example that itself could be relayed with Home Assistant as a Zigbee controller exposing its HTTP API.
e.g Android with PineNote, relatively easy, then trickier due to the lack of screen (and virtual keyboard) e.g Ricoh Theta V (and still rely on Termux and scrcpy) to potential e.g Flipper to probably infeasible e.g Monocle or PineTime yet that should still be considered otherwise, relying on e.g BT via an existing peer.
Could provider a route, e.g
/localsatellites
, for satellite devices that can't become peers proper, e.g BT devicesFor example with the monocle e.g https://twitter.com/utopiah/status/1651089075904868352
Consider
uinput
too, see also past work via the Web https://twitter.com/utopiah/status/1534055718462099457 but requires a browser.Ricoh Theta V should have been the usual Android setup, like the PineNote
Unfortunately it seems impossible to get a keyboard on screen or even via BlueTooth. Consequently impossible to install and start sshd.
What is surprising is that sending keyevent via adb works but only for some, namely
input keyevent "KEYCODE_HOME"
does work but nothing else. Not keycode 108 that should bring up the virtual keyboard not even 29 that should put in the letter 'a'. Also to consider is that seeing a virtual keyboard in any app, starting by Termux but also in the home screen, viascrcpy
seems impossible.Tried run-as-termux.sh with a debuggable apk from Github but failed, maybe root required for file permissions. Also tried https://github.com/termux/termux-app/wiki/RUN_COMMAND-Intent as mentioned in https://github.com/termux/termux-app/issues/924 but requires https://github.com/termux/termux-tasker#allow-external-apps-property-optional which can't be setup headlessly.
See also
usbip
as a way to share USB devices themselves.See also https://developers.home-assistant.io/docs/api/rest/ as example of integrating Zigbee hardware, IoT more generally.
see also https://nitter.net/utopiah/status/1746459313151848517 as a potential ZigBee example that itself could be relayed with Home Assistant as a Zigbee controller exposing its HTTP API.
See also
netevent
cf https://twitter.com/utopiah/status/1565313431409934336