This is listed under Hub as device. The IP address is our main wall mounted tablet used to display dashboards. It still is functioning and able to control things but the error keeps popping up every 30 seconds or so.
You might want to obscure your mac / ip address in the screenshot... or actually, I think they are something different, but I expect it is an identifier of some kind...
In terms of what that message is.... HE has a specific port that devices can send unsolicited data to, i.e. unlike you requesting a web page where you send a request and data is returned, in these cases the device sends HE data without it requesting it. An example, from my setup, is my EcoWitt weather station sending data every 60 seconds to my HE hub. When HE receives the data, it tries to find a device with a device network id that matches the IP address and calls a specific part of the driver, passing it the data that was received, assuming the driver will know what to do with it. Means us dev's don't need to do some of the setup.
When HE can't find a device, that is when you see that message in the logs.
Then that is strange. The only other explanation would be some kind of change to the DNI for the device that is setup to receive it, or some issue in HE finding it...
Yes. With my EcoWitt, I'm pretty sure that is what gets stored as the DNI, i.e. the conversion of your IP address into Hex, like @FriedCheese2006 explained.
So it looks like HE got info from the tablet and didn't find it because the IP DNI combo didn't sit well. And then suddenly it just randomly cleared up?
Just checking logs again and it still hasn't happened again.
That error is indicating that a message came from a device with that MAC address from that IP, and the hub didn't know which virtual device to send it to.
It could be that the DNI of the target device was the IP address and it had changed (not likely based on your comments on using static IP). Or it could be that the DNI of the target device was the MAC and it had changed (very unlikely).
My guess is something was wrong with the driver not being loaded or the incoming message handling at the hub level failed for some reason. Could be hub bug or just random hiccup.
Maybe support could get some additional insight from the backend logs.