Allow empty host field so Save works with auto-discovery (1.0.3)

v1.0.2's H6 fix used Regex.IP on the optional host textinput, which rejects
the empty string. That locked the Save button whenever the user picked an
LV1 from the discovery dropdown (the standard flow): the discovery path
needs host to stay empty so the connect logic falls back to the cached IP
and port from the dropdown selection.

Replace the strict IP regex with `^$|<ipv4>` so the field accepts either
an empty string (= auto-discovery is in use) or a valid dotted-quad IPv4
(= manual override). Selected dropdown + empty host is now a valid state.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Author: miglourenco

package.json

@@ -1,6 +1,6 @@
 {
 	"name": "companion-module-waves-lv1",
-	"version": "1.0.2",
+	"version": "1.0.3",
 	"main": "dist/main.js",
 	"type": "module",
 	"scripts": {

src/config.ts

@@ -1,4 +1,4 @@
-import { SomeCompanionConfigField, Regex } from '@companion-module/base'
+import { SomeCompanionConfigField } from '@companion-module/base'
 import { getDiscoveryCache, refreshDiscovery } from './discovery-cache.js'
 
 export interface ModuleConfig {
@@ -65,7 +65,10 @@ export function GetConfigFields(): SomeCompanionConfigField[] {
 			label: 'LV1 IP (override)',
 			width: 6,
 			default: '',
-			regex: Regex.IP,
+			// Accept empty (= use auto-discovery) OR a valid dotted-quad IPv4. We can't use
+			// Regex.IP here because it rejects the empty string, which would lock the Save
+			// button whenever the user doesn't want a manual override.
+			regex: '/^$|^(?:(?:25[0-5]|2[0-4]\\d|1?\\d?\\d)\\.){3}(?:25[0-5]|2[0-4]\\d|1?\\d?\\d)$/',
 		},
 		{
 			type: 'number',