Hello Moustachauve & Greetings to Canada.
A fix was applied quite recently which actually introduced an unfortunate limitation, at least for me.
I have a bunch of WLED-based lights in my home and also some which are not WLED-based but still have a browser UI.
It used to be possible to basically enter any local IP adress and add it as a new device. Although it was shown as unreachable, the browser UI of the respective light came up when selected in the app. That was really convenient because I had just one app to control any lights with browser interface, WLED or not.
This "bug" was fixed, the app is now checking if new devices really are WLED devices and refuses adding any other addresses.
For me, that bug was a cool feature :-) and hence I would like to suggest making this an option; i.e. enable non-WLED devices as new devices.
Thanks & Regards, korkbaum
Hello Moustachauve & Greetings to Canada.
A fix was applied quite recently which actually introduced an unfortunate limitation, at least for me.
I have a bunch of WLED-based lights in my home and also some which are not WLED-based but still have a browser UI.
It used to be possible to basically enter any local IP adress and add it as a new device. Although it was shown as unreachable, the browser UI of the respective light came up when selected in the app. That was really convenient because I had just one app to control any lights with browser interface, WLED or not.
This "bug" was fixed, the app is now checking if new devices really are WLED devices and refuses adding any other addresses.
For me, that bug was a cool feature :-) and hence I would like to suggest making this an option; i.e. enable non-WLED devices as new devices.
Thanks & Regards, korkbaum