Shelly WiFi Integration (beta): app page fails with "No such property: identity"

Built-In Apps and Drivers
1

Apologies if this topic already exists, I didn't find it with a cursory search in this topic.

Duncan

Disclosure: This report was compiled by an AI assistant (an LLM, Claude by Anthropic) at my request. It used a read-only MCP connection to my hub (MCP Rule Server 4.0.2 with write access disabled) to read the logs, settings and device information quoted below, and then drafted the summary. The assistant made no changes to the hub. Log lines are copied as the hub returned them. The section headed "Assistant's inference" is a guess by the LLM and may be wrong.

Summary

Opening the built-in Shelly WiFi Integration (beta) app (app ID 1216, label "Shelly WiFi Controller Integration") shows an "Unexpected Error" page instead of the app, and the hub logs a MissingPropertyException for a missing identity property on ShellyDevice. Separately, the hub warns every few minutes about data arriving from a Shelly whose Hubitat device I deleted. I don't know whether the two are related.

Steps to reproduce

  1. Go to Apps, then Integrations, then Shelly WiFi Controller Integration (/installedapp/configure/1216/main).
  2. The page shows: "An unexpected error has occurred trying to load the app. Check Logs for more information. Error: No such property: identity for class: com.hubitat.hub.controller.shelly.ShellyDevice"

Expected: the app's main page loads.

Environment

  • Hub: C-8 Pro (hardware ID 000D), firmware 2.5.2.139, no platform update pending
  • App: built-in Shelly WiFi Integration (beta), app ID 1216, enabled
  • Also installed via HPM: Shelly Webhook/Websocket Drivers 2.15.0 and its Shelly Bluetooth Helper app
  • Log times below are hub local time (Australia/NSW, UTC+11)

Background

A Gen2 RGBW Shelly ("Kitchen Bench NEW", IP 192.168.0.194, MAC 2C:BC:BB:C0:71:EC) was previously in Hubitat through this integration as "Shelly WiFi v2 RGBW Light - Kitchen Bench NEW" (device IDs 1113 and 1114). The RGBW device type did not handle switched inputs, so I deleted those devices and now control the Shelly through Home Assistant. Other Shelly devices still use the app, so it remains installed. I can't say when the page error began.

Evidence

1. Error log entries. A search of the hub's log buffer (about 17,000 entries) for ShellyDevice matched only these three, all from the minutes I was opening the page:

2026-10-29 15:12:18.159 ERROR app|1216|Shelly WiFi Controller Integration|groovy.lang.MissingPropertyException: No such property: identity for class: com.hubitat.hub.controller.shelly.ShellyDevice on line 113 (method main)
2026-10-29 15:11:00.491 ERROR app|1216|Shelly WiFi Controller Integration|groovy.lang.MissingPropertyException: No such property: identity for class: com.hubitat.hub.controller.shelly.ShellyDevice on line 113 (method main)
2026-10-29 15:09:44.445 ERROR app|1216|Shelly WiFi Controller Integration|groovy.lang.MissingPropertyException: No such property: identity for class: com.hubitat.hub.controller.shelly.ShellyDevice on line 113 (method main)

2. Warnings about data from the Shelly with no matching device. Latest three:

2026-10-29 15:16:18.348 WARN sys|1|Hub|Received data from 192.168.0.194, no matching device found for 192.168.0.194, C0A800C2:D234, 2CBCBBC071EC or C0A800C2.
2026-10-29 15:10:45.351 WARN sys|1|Hub|Received data from 192.168.0.194, no matching device found for 192.168.0.194, C0A800C2:DAF1, 2CBCBBC071EC or C0A800C2.
2026-10-29 15:04:30.365 WARN sys|1|Hub|Received data from 192.168.0.194, no matching device found for 192.168.0.194, C0A800C2:EB95, 2CBCBBC071EC or C0A800C2.

There were 19 of these between 13:04 and 15:16 (13:04, 13:06, 13:13, 13:19, 13:26, 13:34, 13:48, 14:02, 14:11, 14:13, 14:26, 14:33, 14:39, 14:45, 14:50, 14:58, 15:04, 15:10, 15:16), roughly 2 to 14 minutes apart. The port after C0A800C2: is different each time.

3. The Shelly has no webhooks. http://192.168.0.194/rpc/Webhook.List returns {"hooks": [], "rev": 0}.

4. App settings. App 1216 holds 36 buttonAdd-<MAC> settings keys, including buttonAdd-2c:bc:bb:c0:71:ec, the MAC that appears in the warnings above.

5. Devices. Searching the Devices page for "kitchen bench" returns only devices from my Home Assistant Device Bridge; no device from this integration remains for that Shelly.

6. Other Shellys still work. "Kitchen Appliance Cupboard Door Switch" (type Shelly WiFi Switch, added through this app) last reported at 12:49:58 today.

Not yet checked

  • The Shelly's outbound WebSocket setting (/rpc/Ws.GetConfig), its on-device scripts (/rpc/Script.List) and its schedules
  • The app's source code (the assistant cannot read system apps)

Assistant's inference (unverified)

The app page probably builds its list from stored device records, and one record for the deleted Shelly device lacks an identity property, so the page throws. The unmatched-data warnings suggest the Shelly is still sending to the hub, possibly over a connection the integration set up earlier. Neither is confirmed.

Questions

  1. Is this a known issue in the beta app?
  2. Is there a supported way to clear a stale entry for a deleted Shelly device without uninstalling the app?
  3. Should the hub keep receiving data from a Shelly whose Hubitat device has been deleted?
2

Your stale-entry theory looks plausible, since the app page fails while the other Shelly devices still work. Before reinstalling anything, I would take a hub backup and check the outbound WebSocket setting on that Shelly, as that would explain the repeated warnings even with no webhooks configured. If the app page still fails after that, a clean reinstall of the beta app is likely the safest supported reset, even though you may need to re-add its devices.

3

Thanks. A follow-up from the same AI-assisted investigation (an LLM compiled it for me over a read-only MCP connection, as in the original post). I’ve now checked that Shelly’s config: the outbound WebSocket and MQTT are both disabled, and there are no webhooks. The repeated warnings came from an on-device Shelly script that POSTed a status message to the hub whenever the light’s output changed. [I’ve stopped that script and the warnings have stopped.] That explains the warnings, but not the app page error: [the page still fails with the same identity / ShellyDevice error]. Before trying a clean reinstall, which I expect would remove the devices the app created and break rules that use them, has anyone found a way to clear a single stale entry?

4

Thanks for narrowing that down — stopping the on-device script explains the warnings, so the app-page error is now clearly a separate stale-record problem rather than an incoming-data problem. Before any reinstall, I would download a current local hub backup and note which rules use the app-created Shelly devices, so you have a restore point and a clear list of what would be affected. Rather than deleting anything by hand, I would put the full stack-trace line, the app ID, and that buttonAdd MAC to Hubitat support or the beta thread and ask for a supported way to clear just that one stale entry, while keeping the Shelly script off so no new unmatched data is created in the meantime.