DNS lookup

[djw1191]

Just to actually be comprehensive here, as the question was never answered about what driver you are actually using.. And as it seems the thread went down into a rabbit hole of the Hub's DNS settings (granted that could also be relevant).

I'm going to guess it's this one, based on a quick search: [Release] Philips Wiz Color Light Driver

Quick scan of the code, looks like it is using HubAction and is sending UDP packets. Given a lot of API driven devices make use of some sort of HTTP based API, the driver/device using UDP and HubAction is a critical piece of information to have as I'd argue that is non-standard for most wifi devices, thus why we were asking for the driver being used.

new hubitat.device.HubAction(cmd,
                 hubitat.device.Protocol.LAN,
                 [type: hubitat.device.HubAction.Type.LAN_TYPE_UDPCLIENT,
                 callback: parse,
                 parseWarning: true,
                 destinationAddress: addr])  

https://docs.hubitat.com/index.php?title=HubAction_Object

So looking at the HubAction docs, it is clear the the method supports only a ip:port combo, which is different from the HTTP methods that I'd argue most devs use to interact with devices, which do in fact support either IPs or domains (as mentioned above). I'm not super familiar with HubAction, perhaps destinationAddress already supports a domain, that's something you or someone else would have to test, but the wording suggests that it is expecting an IP.

options - Optional settings when sending the command. See examples for usage. Possible values:

callback - A method name to pass the response from the HubAction back to. If not specified the response will be handed to the parse method of a Device or will be discarded if this HubAction was called from an App.

destinationAddress - The destination address to use when sending LAN messages. In the format ip:port, if no port is specified it defaults to 80.

destinationPort - The port number to use when sending UPNP discovery messages. Defaults to 1900.

type - The type of message to send if its not a standard HTTP request.

HubAction.LAN_TYPE_UDPCLIENT - Send message as a UDP package.

HubAction.LAN_TYPE_RAW - Send message as a raw TCP message.

So not really a bug, something isn't broken, it's just a feature that doesn't exist as is evident by hubitat's docs. I'd also argue that there doesn't really need to be a unique method to make DNS requests in drivers (and the lack of that method doesn't indicate that the hub doesn't support DNS), the feature request IMO is that HubAction should support either a destinationAddress or a destinationDomain or something similar.

Probably could have had a much shorter and more efficient discussion, had the driver just been shared or as you appear to be aware that the driver used HubAction, a peak at the wiki would have indicated what options that method supports.

Now in terms of the feature request, I'll give @gopher.ny a tag, perhaps he can add to his long list of requests, an addition to the HubAction method, the ability to specify a domain in addition to the current option of destinationIP/port.

I have officially devoted way too much time to a device I don't own and will never own....