@bill (Bill) posted a new topic, subject "Is my hub dying?". It read:

   For the last week or two my hub has been reporting both "zwave network is not online" and "zigbee network is not online" errors.
    
    Rebooting seems to help for a while, but the problem comes back in a day or so. Is the hub or usb stick dying or is this an issue with firmware or something? is there an easy migration path to a new hub or do I have to re-register my 150+ devices?
    
    Actually, update- rebooting doesn't help as the web interface doesn't come back up though the device is pingable when I reboot. Power cycling helps.
    
    This is C-4 hardware btw.
    
    Thanks

Then @Hasty1 (Hasty1) said

    I would call upon @bobbyD. My first guess is that it could be temperature related.

So @bill (Bill) replied

    hmm... I suppose that's a possibility. I have a/c and it's not terribly hot in the closet where the hub lives. I just touched it and its warm but not burning up or anything.
    
    I just did a soft reset and restore. I'll see what that does.

So @Terk replied

    What firmware version do you have installed?

So @bill (Bill) replied

    (740)336-5222

To which @ritchierich (Michael) replied

    Turn the hub upside down to let air flow out of holes in bottom. Maybe that may help. FWIW I have my C4s mounted on a wall vertically and I haven't had any issues.

So @JohnRob (JohnRob) replied

    I can't see overheating being an issue unless there is something else bad. Mine is on top of a bookcase, in general the case is about human temperature. The unit would have to get really really hot to have an issue.
    
    I has an issue that could be described as similar. I had a driver caught in a runin loop, I have a C4 as well.
    
    IMHO it is very likely a rogue device, driver or app is causing an issue. I'm not sure the best way to troubleshoot such a situation but perhaps Hubitat folks can help.
    
    UPDATE:  
    I didn't mention, my issue put the Zigbee radio offline. However the issue was with a Z-Wave device/driver.
    
    I am and was on version (740)336-5222

After which, @dadarkgtprince (Dadarkgtprince) added

    did it only happen once you upgraded to .142? i've seen a few others complain about the functionality after upgrading and refuse to upgrade to .142 at risk of experiencing the same issues

So @bill (Bill) replied

    Yeah I'm totally baffled now. No errors that z-wave or zigbee radios aren't working, but now after a few hours of being fine, none of my switches have on or off commands?? This was a working switch 20m ago:  
    
    
    2020-09-02_20-571157×671 81.6 KB

To which @JohnRob (JohnRob) replied

    Now your way far out of my small zone of expertise .... sorry I couldn't help more.
    
    John

Then @Terk said

    I've never seen the buttons disappear from the device screen like that unless the type (driver) changed. Have you tried downgrading back to 2.2.2 if that's still an option? I've stayed on (740)336-5222 on my C-3 since it's been so stable and so far most of the 2.2.3 changes have been trying to work out C-7 issues.

Then @bill (Bill) said

    Alright I rolled back to 2.2.129 and my switches are back. Hope it stays that way. WTF?

So @dadarkgtprince (Dadarkgtprince) replied

    there's definitely something with the new firmware that's messing stuff up. @bobbyD might be able to help figure it out, but i know they're working on fixing C-7 stuff before getting to other things

@bill (Bill) replied

    No issues yet since downgrading to 2.2.129 last night...

Then @Evilborg (Scott Grayban) said

    You aren't alone.... when I did a upgrade on my C4 to the 2.2.3 branch my hub died or so I thought. Since I had a spare C5 hub I simply moved my dual usb stick to it using a splitter and restore from a backup... but I did keep my C4 running for a few days and it did magically come back to life.
    
    What I think happens is the DB structure changed between 2.2.2 and 2.2.3 and so did the events logging. When the C4 did run its nightly maintenance the backup size went from 15MB(2.2.2) down to 2MB(2.2.3) and it ran pretty nicely but since I already moved to the C5 hub I reset that C4 hub and use it for Webcore and Hubconnect now.
    
    I think that is what your issue is. There are 2 urls you can run that will 1) reduce the event logs 2) force the nightly cleanup. That should cleanup your hub drastically I suspect. @bobbyD can help you with those urls.
    
    Once you have done those you can reboot the hub, save a DB backup then upgrade the hub to 2.2.3 and it should run just fine.

@system (system) replied

    This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.


{'source': 'discourse', 'url': 'https://community.hubitat.com/t/is-my-hub-dying/49442', 'title': 'Is my hub dying?', 'views': 429, 'has_accepted_answer': False, 'word_count': 848, 'like_count': 4, 'reply_count': 6, 'participant_count': 7, 'posts': 16, 'tags': 'remove', 'author': '@bill (Bill)', 'participants': '@bill (Bill), @Hasty1 (Hasty1), @Terk, @ritchierich (Michael), @JohnRob (JohnRob), @dadarkgtprince (Dadarkgtprince), @Evilborg (Scott Grayban), @system (system)', 'image_url': [None], 'created_at': '2020-09-03T01:01:26.458Z', 'last_posted_at': '2022-09-22T17:18:18.887Z'}