All junior devs should read OCs comment and really think about this.
The issue is whether is_number()
is performing a semantic language matter or checking whether the text input can be converted by the program to a number type.
The former case - the semantic language test - is useful for chat based interactions, analysis of text (and ancient text - I love the cuneiform btw) and similar. In this mode, some applications don’t even have to be able to convert the text into eg binary (a ‘gazillion’ of something is quantifying it, but vaguely)
The latter case (validating input) is useful where the input is controlled and users are supposed to enter numbers using a limited part of a standard keyboard. Clay tablets and triangular sticks are strictly excluded from this interface.
Another example might be is_address()
. Which of these are addresses? ‘10 Downing Street, London’, ‘193.168.1.1’, ‘Gettysberg’, ‘Sir/Madam’.
To me this highlights that code is a lot less reusable between different projects/apps than it at first appears.
MicroWakeWord is a project built on the ESPHome framework.
ESPHome is a project for building, deploying and managing microcontroller firmware (such as ESP32 devices). So, because MicroWakeWord uses ESPHome, you can easily deploy it to your preferred device.
ESPHome is deeply connected inside HomeAssistant and therefore the integration is essentially OOTB - but you have to flash ESPHome firmware on an ESP device which will probably involve soldering electronics. There are some dev kits available that contain everything you need pre-built though (like this one - no endorsement)