Advanced Users App - Error loading hubs - 429 Too Many Requests

Just started getting a new issue with the My SmartThings for Advanced users.

Error loading hubs: 429 Too Many Requests attempt 1353 limit 1000 - retry in 56112 millis.

Anyone see this before ?

tagging @nayelyz

1 Like

I’ve seen this several times. Usually resolves itself.

1 Like

I rebooted the Hubs and all is back to normal now, not sure if it was the rebooting or just the wait that solved it, but I’m sorted again. Thanks

1 Like

sorry for comment again on this old topic , but I face it always whenever I attempt to pair more than 30 devices via matter , is there any workaround to not get this error every time ?

I’ve added another Matter device, and it’s happened again. So yes seems to be related to adding Mattwr devices

Hi, @tammeryousef1006, @Jeff_Gallagher

Could you provide a screenshot of the message that appears in the Advanced Users app to show it to the team, please?


Mine was slightly different. it was a 500 Error. However I cannot screenshot it. I did a little bit of researching, and to resolve a 500 Error it was suggested that I uninstall the SmartThings app on iOS devices. As soon as I did that it was fixed. Very strange.

@tammeryousef1006, Can you open support access to your account, please?

  1. Confirm the email account registered in the forum is the same one you use for SmartThings. If not, please share it with me over DM
  2. Enable support access to your account:
  1. Go to the SmartThings Web (my.smartthings.com)
  2. Log in to your Samsung Account
  3. Select Menu (â‹®) and choose Settings
  4. Toggle on Account Data Access
  5. Select the time period and confirm - In this step, please select “Until turned off”, once the team finishes, we’ll let you know so you can disable it again.

ok, thank you for sharing your workaround, I’ll also mention it in the report as a reference.

1 Like

Sure , i already enabled support access

Hi, @tammeryousef1006
Can you let us know a step by step on how you get to this issue?

I saw you mentioned “I face it always whenever I attempt to pair more than 30 devices via matter” so, is that all at once and you’re constantly refreshing the page?
Because I see you have several Matter devices so, we’re trying to understand when this started to happen.
It can also be that you had less than 30 Matter devices and when you added more, this issue started to happen since the first time you open the “Hubs” page or does it also happen on the “Devices” page?

i already got 32 matter devices paired through matterbridge , i use matterbridge to bring zigbee2mqtt devices to smartthings , once I’m trying to add more devices the hub hangs few minutes ( 5 - 10 min ) then become responsive again , its happens upon adding devices not upon going to hub page .

by the way my main hubv3 on latest firmware v54.13 , i read that latest build support Electrical Sensor , i got samsung s10 plus with latest smartthings app and I did add some electrical sensors but it appears as normal switches without power read , whats the reason of not showing those reads ?

That would depend on each device:

  1. Can you see which sensor is controlling the device?

    • That’s seen in the device’s details > Menu (three-dot symbol in the upper-right corner) > Driver
  2. Do you know the fingerprints of the device or its full model and brand? I need to confirm if they’re included in the SmartThings drivers
    If you’re not sure of this information, you can query it in the Advanced Users app > Devices > Open a device’s details and send a screenshot of the “Summary” section over DM.

sorry for late reply , i noticed today that devices started to shows power read , however there is something wrong with matter electric its like inverted , I attach for you some screenshots and let me know if you needed any further info’s .



What do you mean inverted?

In the Advanced Users app I see power Meter reports 60000 Watts and the app shows 58 Kilowatts, so the difference is because of the unit, did you take both captures at the same time? if that was the case, the app should show 60 kW
And, the energy Meter capability shows correctly 0 in both, in this case, the unit is the same, so, both should show the same value.

ok i made two new screenshots at same time for same read


as you see in the screenshot the power read was 60000 watts and the app shows 60 kilowatts for the same device while energy remain 0 until now , to clear my issue this device is a small fan connected to plug over z2m and the actual power should be 60 watt only not kilowatts , and accumulated energy is 214.14 k , I will attach below screenshot for the device power read

its true that smartthings showing same value between advanced user page and app because both for smartthings , but reading from source has to be reviewed because not matching , if you needed any more info or tests I’m ready to help

@nayelyz I believe there is indeed a bug in the Matter switch driver.

Matter reports the active power in mW per specification, but the raw value is passed to the powerMeter capability as if they were watts, hence that SmartThings thinks the device is reporting 60000 W when it should be 60000 mW / 1000 = 60 W.

local function active_power_handler(driver, device, ib, response)
  if ib.data.value then
    device:emit_event(capabilities.powerMeter.power({ value = ib.data.value, unit = "W"}))
  end
end

And the same goes for the CumulativeEnergyExported attribute, Matter reports it in mWh but the data is not divided and passed as if they were Wh:

local function cumul_energy_exported_handler(driver, device, ib, response)
  device:set_field(TOTAL_EXPORTED_ENERGY, ib.data.elements.energy.value)
  device:emit_event(capabilities.energyMeter.energy({ value = ib.data.elements.energy.value, unit = "Wh" }))
end

Edit: Yeah, that’s it, the tests also assume the unit is W, that’s why they don’t fail. For instance this test data for 19 W should have an energy value of 19000 since that’s the Matter raw struct and the unit is actually mW.

local cumulative_report_val_19 = {
  energy = 19,
  start_timestamp = 0,
  end_timestamp = 0,
  start_systime = 0,
  end_systime = 0,
}
3 Likes