For the last few weeks I've been having frequent losses of access to my C-7 hub's management pages (main and diagnostic), and as part of this am adding a button press handler that will start a proper reboot rather than doing a potentially damaging power cycle.
To rule out a change of the hub's IP address[1] as a cause of the problem I'd also like to retrieve the current local IP address and write it to the logs, for checking after the reboot. But doing that extra bit's fallen at the first hurdle - I can't find a way of getting the IP address.
Does anyone know how this can be done?
[1] It shouldn't - the hub has an address reservation on my router.
Ah, thanks - I have that installed (and am using it for the reboot!), and looked for that having the address, but clearly failed to spot that parameter when I was adding the rule earlier.
Ironically I can't check/use it now, as I need to get in via Remote Access and my hub's gone inaccessible again...
Does this mean you are subscribed to that service via HE or that your remote access to your network isn't working? I would assume the first option. So that would tend to indicate it has completely fallen of the network. hum
Thanks for the suggestions - itemising things in vaguely the original order:
The hub does continue to work - all rules fire, and it responds to sensor/button triggers. But, no access to any of the management pages, or via Alexa.
I'll try a new network cable and power supply in the near future.
When the hhb's inaccessible everything else on the LAN is still working correctly.
There's already a switch between hub and router.
Going from memory the hub light's green, although for some months I've been power cycling via a Sonoff USB power switch so haven't seen it lately (it's on top of a tall bookcase). Will check on the next occurrence.
It is the Hubitat remote access system I'm using (and that also stops responding).
FWIW nothing's changed on the cabling/physical side recently. This could well be a pair of red herrings, but the only significant changes the problems starting were roughly coincident with was updating to 2.3.8 (Matter not enabled) and switching to OwnTracks from Life360.