With version 2.3.8 it appears that the mDNS name hubitat.local is broken. I use this quite a bit, so this is a problem. Is there at least a new mDNS name? Or any other way to easily get the correct IP address automatically?
On your settings page, what is filled in for the Hub Name on LAN?
I did check using that name.local. Using that name would make sense, but it did not seem to work. And if so someone would have mentioned it in the release notes or whatever.
Gosh, I never noticed that you could change the .local address. But I did see it, and it is still "hubitat". And "hubitat.local" does not work as either an https or a ping destination.
Just in case, I changed the name in "Hub Name On LAN" do something different, restarted, and tried with the new name. Nothing. Then back to hubitat and restart. Still not accessible. So I am currently of the opinion that there is a bug in the latest software update. Is there a place to report it?
Well the recommended way is to set a DHCP reservation on your router, so your hub always gets the same address. Not sure why your mDNS isn't working, as mine is. Have you added anything new on your network? New vlan or something?
Try restarting your router. That usually fixes mDNS issues for me.
I do have it set up with a DHCP reservation, but just so you understand why the mDNS is important, I have written a skill for what used to be MyCroft, now Neon, a voice command device to use in place of Alexa. The skill is used by a number of people who do not have to mess around with network addresses because the skill uses hubitat.local. My skill stopped working just today when I updated Hubitat to version 2.3.8.119.
Do you have that very version, and you mDNS works with it?
Oh, I see the suggestion to restart the router. That's a good plan, although I have never had to before when I updated Hubitat. I'll give it a try when noone is using it. Thanks for the idea.
Hmm. It started working again. I just realized that part of the symptom was also that HomeKit also stopped working after I did that upgrade. But I just tried HomeKit again and it was ok. So then I went to hubitat.local and it was similarly ok. Note that all this time, the dotted quad directly worked. I'm a bit mystified, but it is back in operation now. Thanks for your thoughts, ideas, and help.
1 Like
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
