ZigBee network is not online in C7

Hello everyone,

In December 2021 I bought a Hubitat C7 (currently running version: 2.3.2.141), it had been working fine for several months but since a few days I have been having a lot of problems with "ZigBee network is not online", I have restarted the hub, I also did the whole guide of @thebearmay thebearmay which said "go to Settings and click "Shutdown". When the LED on the hub turns red, please unplug the power for one minute before plugging it back. When the hub comes back online, please go to Zigee Details and enable the radio ."
But the above does not solve the problem.

Currently I only have 3 types of devices connected:

  • Leviton Switch (model DG15S)
    image

  • Leviton Dimmer (model DG6HD)
    image

  • Sonoff motion sensor (model SNZB-03)
    image

Please someone who can help me with this, since right now I only use my hub to control the lights in my house and at the moment it is useless.

Thank you very much!

Couple of questions:

  1. What channel are you running your zigbee on
  2. What does http://hub_ip_address/hub/zigbee/getChildAndRouteInfo show

Edit: Additional thought, sometimes the zigbee radio gets shutdown when the hub is under stress or low on free memory - do your loss of zigbee correspond to either of those events?

4 Likes

Be sure to open a warranty case too, so we can check to make sure you are not dealing with a hardware malfunction.

4 Likes

Hi!

  1. It is running on channel 11.

  2. This is what the getChildAndRouteInfo show:

<!doctype html>
<html lang="en">

<head>
    <meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="description" content="">
<meta name="viewport" content="width=device-width, initial-scale=1.0, minimum-scale=1.0">
<meta name="robots" content="noindex">
<meta name="mobile-web-app-capable" content="yes">
<link rel="apple-touch-icon" sizes="180x180" href="/ui2/images/apple-touch-icon.png">
<link rel="icon" type="image/png" sizes="32x32" href="/ui2/images/favicon-32x32.png">
<link rel="icon" type="image/png" sizes="16x16" href="/ui2/images/favicon-16x16.png">
<link rel="icon" sizes="192x192" href="/ui2/images/favicon.ico">
<link rel="manifest" href="/ui2/images/site.webmanifest">
<link rel="mask-icon" href="/ui2/images/safari-pinned-tab.svg" color="#5bbad5">
<link rel="shortcut icon" href="/ui2/images/favicon.ico">
<meta name="msapplication-TileColor" content="#da532c">
<meta name="msapplication-config" content="/ui2/images/browserconfig.xml">
<meta name="theme-color" content="#ffffff">
<style>
    html {
        -webkit-text-size-adjust: 100%; /* Prevent font scaling in landscape while allowing user zoom */
    }
</style>
<link rel="stylesheet" href="/ui2/css/material.min.css?buildVersion=">
<link rel="stylesheet" href="/ui2/css/styles.min.css?buildVersion=">
<script src="/ui2/js/jquery-3.6.0.min.js" rel="preload" as="script"></script>
<script type="text/javascript ">
    window.jQuery || document.write("<script src='/ui2/js/jquery-3.6.0.min.js'> <\ / script > ");
</script>
<script src="/ui2/js/material.min.js?buildVersion="></script>
<script src="/ui2/js/hubitat.min.js?buildVersion="></script>
<script src="/ui2/js/success-compiled.js?buildVersion="></script>
<script src="/ui2/js/hub2utils.js?buildVersion="></script>
<link href="/ui2/css/hubitat.css?buildVersion=" rel="stylesheet" />
<link href="/ui2/css/fonts.css?buildVersion=" rel="stylesheet" />

<title>Server error</title>
<style>
body {
    background-color: var(--surface-a);
    overflow-x: hidden;
}

main {
    display: none;
}

.mdl-layout__content { opacity:0 }
.mdl-grid:focus { outline: none; }

#app {
    -webkit-font-smoothing: antialiased;
    -moz-osx-font-smoothing: grayscale;
}
</style>
<link rel="stylesheet" href="/ui2/css/jquery.dataTables.1.12.1.min.css">
<script src="/ui2/js/jquery.dataTables.1.12.1.min.js "></script>
<link rel="stylesheet" href="/ui2/css/sumoselect.min.css"/>
<script src="/ui2/js/jquery.sumoselect.min.js"></script>
<script src="/ui2/js/moment.min.js"></script>
<link href="/ui2/css/quill-core.css" rel="stylesheet" />
<script>
const zwaveStatus = '' === 'true';
const zigbeeStatus = '' === 'true';
const zwPlusBadge = '' === 'true';
const hubDeveloper = '' === 'true';

var fontSize = 14;
$(function() {
    fontSize = Number(window.getComputedStyle(document.body).getPropertyValue('font-size').match(/\d+/)[0]);
    document.title = stripHtml(document.title);
});

const isSafari = /^((?!chrome|android).)*safari/i.test(navigator.userAgent);
var isMobile = false;
if(/(android|bb\d+|meego).+mobile|avantgo|bada\/|blackberry|blazer|compal|elaine|fennec|hiptop|iemobile|ip(hone|od)|ipad|iris|kindle|Android|Silk|lge |maemo|midp|mmp|netfront|opera m(ob|in)i|palm( os)?|phone|p(ixi|re)\/|plucker|pocket|psp|series(4|6)0|symbian|treo|up\.(browser|link)|vodafone|wap|windows (ce|phone)|xda|xiino/i.test(navigator.userAgent)
    || /1207|6310|6590|3gso|4thp|50[1-6]i|770s|802s|a wa|abac|ac(er|oo|s\-)|ai(ko|rn)|al(av|ca|co)|amoi|an(ex|ny|yw)|aptu|ar(ch|go)|as(te|us)|attw|au(di|\-m|r |s )|avan|be(ck|ll|nq)|bi(lb|rd)|bl(ac|az)|br(e|v)w|bumb|bw\-(n|u)|c55\/|capi|ccwa|cdm\-|cell|chtm|cldc|cmd\-|co(mp|nd)|craw|da(it|ll|ng)|dbte|dc\-s|devi|dica|dmob|do(c|p)o|ds(12|\-d)|el(49|ai)|em(l2|ul)|er(ic|k0)|esl8|ez([4-7]0|os|wa|ze)|fetc|fly(\-|_)|g1 u|g560|gene|gf\-5|g\-mo|go(\.w|od)|gr(ad|un)|haie|hcit|hd\-(m|p|t)|hei\-|hi(pt|ta)|hp( i|ip)|hs\-c|ht(c(\-| |_|a|g|p|s|t)|tp)|hu(aw|tc)|i\-(20|go|ma)|i230|iac( |\-|\/)|ibro|idea|ig01|ikom|im1k|inno|ipaq|iris|ja(t|v)a|jbro|jemu|jigs|kddi|keji|kgt( |\/)|klon|kpt |kwc\-|kyo(c|k)|le(no|xi)|lg( g|\/(k|l|u)|50|54|\-[a-w])|libw|lynx|m1\-w|m3ga|m50\/|ma(te|ui|xo)|mc(01|21|ca)|m\-cr|me(rc|ri)|mi(o8|oa|ts)|mmef|mo(01|02|bi|de|do|t(\-| |o|v)|zz)|mt(50|p1|v )|mwbp|mywa|n10[0-2]|n20[2-3]|n30(0|2)|n50(0|2|5)|n7(0(0|1)|10)|ne((c|m)\-|on|tf|wf|wg|wt)|nok(6|i)|nzph|o2im|op(ti|wv)|oran|owg1|p800|pan(a|d|t)|pdxg|pg(13|\-([1-8]|c))|phil|pire|pl(ay|uc)|pn\-2|po(ck|rt|se)|prox|psio|pt\-g|qa\-a|qc(07|12|21|32|60|\-[2-7]|i\-)|qtek|r380|r600|raks|rim9|ro(ve|zo)|s55\/|sa(ge|ma|mm|ms|ny|va)|sc(01|h\-|oo|p\-)|sdk\/|se(c(\-|0|1)|47|mc|nd|ri)|sgh\-|shar|sie(\-|m)|sk\-0|sl(45|id)|sm(al|ar|b3|it|t5)|so(ft|ny)|sp(01|h\-|v\-|v )|sy(01|mb)|t2(18|50)|t6(00|10|18)|ta(gt|lk)|tcl\-|tdg\-|tel(i|m)|tim\-|t\-mo|to(pl|sh)|ts(70|m\-|m3|m5)|tx\-9|up(\.b|g1|si)|utst|v400|v750|veri|vi(rg|te)|vk(40|5[0-3]|\-v)|vm40|voda|vulc|vx(52|53|60|61|70|80|81|83|85|98)|w3c(\-| )|webc|whit|wi(g |nc|nw)|wmlb|wonu|x700|yas\-|your|zeto|zte\-/i.test(navigator.userAgent.substr(0,4))) {
    isMobile = true;
}

var currentTabId = null;
if (sessionStorage.currentTabId && sessionStorage.closedLastTab !== '2') {
    currentTabId = sessionStorage.currentTabId
} else {
    currentTabId =  (sessionStorage.currentTabId = Math.floor(Math.random() * Math.pow(10, 15)));
}

sessionStorage.closedLastTab = '2';
window.onbeforeunload = function(e) { sessionStorage.closedLastTab = '1'; };

const urlParams = new URLSearchParams(window.location.search);
const hubitatDarkTheme = (urlParams.get('theme') === 'dark');
const theme = hubitatDarkTheme ? 'mdc-dark-indigo' : 'mdc-light-indigo';
document.writeln("<link rel='stylesheet' href='/ui2/themes/" + theme + "/theme.css'>");
var globalCurrentVueUIPage = '';
var globalMenuSelection = '';
var globalDocumentationTopic = '';
var globalHideMenuHeaderFooter = '';
</script>

<link rel="stylesheet" href="/ui2/css/primevue.min.css">
<link rel="stylesheet" href="/ui2/css/primevue-overrides.min.css">
<link rel="stylesheet" href="/ui2/css/primeicons.min.css">
<link rel="stylesheet" href="/ui2/css/primeflex.min.css">


</head>

<body>
    <main>
    <div class="mdl-grid">
        <div class="mdl-card mdl-shadow--2dp mdl-cell mdl-cell--12-col mdl-cell--12-col-phone">
            <div class="mdl-card__title">
                <div>
                    <div class="mdl-grid p-0">
                        <div class="mdl-cell mdl-cell--12-col">
                            <h2>Error 500</h2>
                            <h3>Something went wrong</h3>
                            <p class="pt-2">
                                If you are seeing this screen repeatedly,
                                please visit <a target='_blank' href='http://support.hubitat.com'>support.hubitat.com</a>.
                            </p>
                        </div>
                    </div>
                </div>
            </div>
        </div>
    </div>
</main>
    <div id="app"></div>
<script src="/ui2/js/vue-hub2.min.js?buildVersion="></script>
<link rel="stylesheet" href="/ui2/css/vue-hub2.min.css?buildVersion=">


</body>
</html>

And finally, regarding to the hub state (if is under stress or low on free memory), I don't have any message, just this:
image

Thanks @thebearmay !

Zigbee Channel 11 is often not very ideal, as it conflicts with 2.4GHz WiFi channel 1. What WiFi channel(s) are being used by your home network?

It is always best to make sure your 2.4GHz WiFi network is only using channels 1, 6, and/or 11, with a 20MHz channel width. This will create three distinct non-overlapping gaps that Zigbee channels 15, 20, and 25 will work with minimal interference.

This is not to say that 2.4GHz WiFi interference is the source of your issues. However, I know some devices really do prefer to be used on specific Zigbee channels. Most users seem to find Zigbee channel 20 to work with the vast majority of Zigbee devices that have been produced over the past decade.

If you have a Philips Hue bridge, or any other devices creating their own Zigbee mesh networks, you should also make certain that they are not using the same Zigbee channel as your Hubitat Zigbee mesh network. For example, I run my Hue bridge on Zigbee channel 25, and my Hubitat hub on Zigbee channel 20. My WiFi access points are configured to use 2.4GHz WiFi channels 1, 6, and 11 with a 20Mhx channel width. Both Zigbee networks in my home have been very reliable, and fast.

One more thing - I personally do not recommend Zigbee channel 26, as many devices do not work well with it, and it has a lower power output due to FCC regulations.

2 Likes

That's definitely good information, but I suspect if @Thokred is seeing a Zigbee network is not online error from the HE itself, either the Zigbee radio has failed, or some software situation is preventing the network stack from starting. If he was experiencing interference, the HE would still be acting as a Zigbee coordinator, even if it wasn't successful at coordinating any devices.

Unfortunately, the only thing I can think to do that hasn't already been done is to perform a full factory reset of the HE to rule out a software issue.

Agreed! My thinking was that @Thokred should start by verifying he has a healthy Zigbee/WiFi configuration, as that is the foundation upon which everything else relies.

Another thing to check is whether or not the Leviton switches and dimmers are flooding the Zigbee mesh network with Power/Energy reporting messages. A very chatty set of devices could cause the hub to become overwhelmed with traffic.

I would avoid the FULL reset unless instructed to do so by Hubitat Support. A soft reset will accomplish the vast majority of hub cleanup tasks, without requiring the user to re-register their hub, re-pair all of their devices, and rebuild all of their automations.

1 Like

Hi @ogiewon,

I have changed the configuration of the router to use channel 6 at 20MHz in the 2.4 GHz network, I also updated the configuration of the ZigBee network to use channel 20.

Thanks for the recommendation.

1 Like

Looks like your Zigbee network is currently showing as OFFLINE. If that is still the case, please perform an orderly shutdown of your hub from the SETTINGS menu. Then pull the power supply from the wall outlet, wait 10 seconds or so, and then plug it back in. Hopefully the Zigbee radio will then show up as being ONLINE.

Once you get past that hurdle, then take a look at each of your Leviton devices, to see if they have power reporting enabled. If so, let's disable that feature for now.

1 Like

Thanks @ogiewon,

Regarding your message, I have some comments/doubts for each part that you exposed to me, I explain it below:

  1. "start by verifying he has a healthy Zigbee/WiFi configuration, as that is the foundation upon which everything else relies." Ready, I applied your recommendation above.

  2. "Another thing to check is whether or not the Leviton switches and dimmers are flooding the Zigbee mesh network with Power/Energy reporting messages. A very chatty set of devices could cause the hub to become overwhelmed with traffic."

Could you please explain to me how to do that? I was reading a similar post right here and changed the Logs setting in the "Device stats" part to 5.

  1. "A soft reset will accomplish the vast majority of hub cleanup tasks, without requiring the user to re-register their hub, re-pair all of their devices, and rebuild all of their automations."

Yesterday I made a backup of my database, then in the "Hubitat Diagnostic Tool" section I did a "Soft Reset" and then I restored my database again, but that did not solve the problem.

Thanks! :+1:t4:

1 Like

First things first... Did you see my most recent post above?

Let's get that Zigbee status page showing things properly first! :wink:

So, open up each of your Leviton switches and dimmers in Hubitat, one at a time, and look for a User Preference similar to that shown below. If there is a power reporting feature, please set it to disabled. Then click SAVE as highlighted below.

2 Likes

I already did the steps mentioned above,

But it didn't work, what I did was turn off all the breakers of the lights part of my house, I left the house without light for a while and then I reconnected everything, the ZigBee radio is now online.

I've checked every single device I have and none of them have that option:

Switch:

Dimmer:

Thanks!

1 Like

Sounds good. Hopefully things will calm down and work more reliably now. It looks like you've done pretty much all of the major troubleshooting steps that have been recommended thus far in this thread.

One other thing to consider is to make sure your hub is not overheating. It definitely needs to be out in the open air, not tucked away in small space where heat can build up.

Also, should the problem return, you may want to try a different power supply, just as a troubleshooting step. Make sure it outputs 5V DC and is rated for at least 1 Amp. Be gentle with the connector on the hub, as some users have managed to damage the microUSB connector on the hub's motherboard.

Should all else fail, as @bobbyD mentioned, file a warranty claim to have the Hubitat Support team take a look at your hub is case there is a hardware malfunction.

1 Like

Thank you very much @ogiewon, I really appreciate your time and help.

:+1:t4:

2 Likes