Actually I didn’t see a clear response to the bulbs/firmware being out of compliance with HomeKit, which when on-boarding the bulb (independent of your app), allows me (normally) to assign an mDNS hostname. You firmware (defectively) seems to disregard that value when it’s passed to your device as part of network-onboarding and pairing for new devices.
While I understand users may request names that fall outside of the zeroconf spec, there are APIs in Mac/iOS to obtain a sanitized/safe name space device name. Regardless of that it’s simple enough to filter character values to (at least in this country to alpha numeric a-Z and 0-9 + dash and underscore. Have you developers look at Bonjour - Apple Developer and HomeKit - Apple Developer
Timing to fix
So it is confirmed that this is NOT desired functionality, and a fix will be forthcoming?
ETA? Hopefully A LOT shorter than nearly 2 year wait for the promised adaptive lighting support since this is a clear regression in functionality and relatively simple as the functionality was intentionally removed. It SEEMS like you just need to filter on character strings to ensure valid input. While it might be nice to offer a simple way to just rename the bulbs already deployed, I (and perhaps others), could even live with reseting the bulb to factory and re-onboarding as the quickest & simplest path to market for the update though bonus points for eventually adding a developer API to do this (at some FUTURE date). Once again I will add my willingness to test release(s) that support either app or API based bulb naming or even the mythical adaptive lighting support you previously mentioned in other threads.
I name bulbs with the -<fixture, if appropriate>-. For example Kitchen-Overhead-1, Kitchen-Flood-3, Downstairs-Hall-6. Given the ~ 50 bulbs this is the only way to keep track of this number of bulbs, MACs, and HomeKit codes, and dynamic link local addresses. Also simplifys using bulbs with LOCAL/on-net third-party applications and integration.
Well that how I number those OTHER than the 7 Lifx default named (aka unnamed) bulbs that remain, and inspired my original post in this thread. I also have a smattering of older bulbs with spaces in the bulb name in place of a the ‘-’. While not consistent with my standard, they do allow me to understand what the bulb is, and don’t cause any problems on my network as I don’t actually send commands to them by DNS name. Of course they would’t be considered valid as pure DNS naming but then again I can’t exactly change them so…