Edge Drivers Spontaneously Restart

Developer Programs Writing Edge Drivers
21

I wonder if it’s this. Btw isn’t there a 50 driver limit?

IMG_0747
IMG_07471170×2532 287 KB

22

If you look at your hub in the AWA under characteristics the first entire is driver memory. There are 3 levels, ok. soft limit, and hard limit. I operate at soft limit on 2 hubs with no apparent issues

Screenshot_20250911-233001
Screenshot_20250911-233001787×370 7.56 KB

I have 45 drivers one hub and 47 on the other hub at Soft Limit. The are both v2 hubs.

23

Right now my memory status says soft limit and further down there is a driver count limit status of hard limit. Looks like I’ve got to trim my drivers. TBD if this is the cause of my drivers to constantly restart.

Will report my findings here.

1 Like
24

I never noticed the “driver count limit status”. Mine both say ok with 45 and 47 drivers.

25

A 2 year old thread on the subject.

26

Sorry you got this perception, but last time we asked you to confirm if you sent the hub logs after you collected the driver logs, then you mentioned “Yes, I send the logs through the app immediately following the incident.” to which we replied that the app logs are different from the hub logs and asked you to confirm you sent the hub logs since they are essential for the team to investigate but got no reply. The driver logs don’t contain information about why the driver was restarted, the hub logs do.

So, if you’re seeing this again, please, we need both: driver logs (to see the timestamp) and hub logs after the incident to see the reason of the restart and compare it with the timestamp in the driver logs.

For every report, it is important to have all the information; otherwise, the team won’t be able to analyze it further.

27

Thanks for this. Must be what I’m experiencing. I guess I’m cooked then; no way I can live with just a handful of drivers on my old V2 hub.

Does anyone have info on the driver & device capacities on the newer hubs? I may be forced to modernize :smirking_face:

28

I did send the log - proof is in my sent folder. It must have been over looked.

29

I am running 46 to 47 drivers on my v2s with no apparent issues.

30

I believe the v3 huh has less memory and consequently can accommodate fewer drivers.

31

I’ve seen a lot of drivers that support a lot of devices, but don’t use sub-drivers. And even then they don’t do this:

local function lazy_load_if_possible(sub_driver_name)
  -- gets the current lua libs api version
  local version = require "version"

  -- version 9 will include the lazy loading functions
  if version.api >= 9 then
    return ZigbeeDriver.lazy_load_sub_driver(require(sub_driver_name))
  else
    return require(sub_driver_name)
  end

end

-- Example:

local zigbee_switch_driver_template = {
  supported_capabilities = {
    capabilities.switch
  },
  sub_drivers = {
    lazy_load_if_possible("hanssem"),
    lazy_load_if_possible("frient")
  },
}

It’s not just the amount of drivers - it’s the size of each.

32

That’s insane. I also see the new aeotec smart hub 2 coming to U.S. Oct 30 has dropped support for zwave, so that won’t be an option.

1 Like