As others said, it's quite wasteful and unnecessarily fragile to introduce Google Assistant (and the Internet itself) in the critical path, although this is just driving an automated test rather than a nuclear reactor, so, sure, ok.
But even the suggestion to bypass Google Assistant still look so unnecessarily complex, especially if you didn't already happen to have a Home Assistant and a Zigbee adapter at hand.
This Milk-V duo seems to have a reset button (sadly not exposed on the GPIO pins, but that's not the end of the world). Find how it works (drive a certain line high or low, just see if one side is permanently 0V or 3.3V), wire it to your USB-UART adapter's DTR or CTS one, and toggle it when you need a reboot.
Done.
It does require soldering 1 wire, and not every USB-UART adapter has a DTR or CTS line (but a majority do), but it's so beautifully simple compared to this.
(Speaking as someone who _does_ have a suitable homeassistant (with zigbee2mqtt and slae.sh's excellent CC2652 stick, deserves a plug on HN: https://slae.sh/projects/cc2652/ ))
But even the suggestion to bypass Google Assistant still look so unnecessarily complex, especially if you didn't already happen to have a Home Assistant and a Zigbee adapter at hand.
This Milk-V duo seems to have a reset button (sadly not exposed on the GPIO pins, but that's not the end of the world). Find how it works (drive a certain line high or low, just see if one side is permanently 0V or 3.3V), wire it to your USB-UART adapter's DTR or CTS one, and toggle it when you need a reboot.
Done.
It does require soldering 1 wire, and not every USB-UART adapter has a DTR or CTS line (but a majority do), but it's so beautifully simple compared to this.
(Speaking as someone who _does_ have a suitable homeassistant (with zigbee2mqtt and slae.sh's excellent CC2652 stick, deserves a plug on HN: https://slae.sh/projects/cc2652/ ))