Misc
Hi,
I'm testing Shellbee with my Zigbee2MQTT setup and noticed that two IKEA TRADFRI remote controls are shown as Offline in Shellbee, while they are not shown as offline in the native Zigbee2MQTT frontend.
These devices are battery-powered end devices, and in Zigbee2MQTT their per-device availability is explicitly disabled.
Relevant Zigbee2MQTT configuration excerpt:
"0x804b50fffe868332": {
"availability": false,
"friendly_name": "Mando Estudio",
"icon": "device_icons/0bb605a453f07b8806fb5bd0288dd434.png"
},
"0x804b50fffe87f953": {
"availability": false,
"friendly_name": "Mando salón",
"icon": "device_icons/0bb605a453f07b8806fb5bd0288dd434.png"
}
In Shellbee, both devices appear as:
Mando Estudio - Offline
Mando salón - Offline
In the Zigbee2MQTT frontend, they are visible and not marked as offline. They also work normally when pressed.
My guess is that Shellbee may be treating missing or stale availability data as offline, instead of respecting the per-device availability: false setting from Zigbee2MQTT. For battery-powered remotes, this causes false offline states.
Environment:
Zigbee2MQTT version: 2.10.0
Connection: HTTPS/WSS through reverse proxy
Zigbee2MQTT frontend auth_token: enabled
Device model: IKEA TRADFRI remote control
Device type: battery-powered end device
Expected behavior:
Devices with availability: false should probably not be shown as Offline, or should have a neutral/unknown availability state, matching Zigbee2MQTT's behavior.
Actual behavior:
Shellbee shows these devices as Offline.
Attachments

Misc
Hi,
I'm testing Shellbee with my Zigbee2MQTT setup and noticed that two IKEA TRADFRI remote controls are shown as Offline in Shellbee, while they are not shown as offline in the native Zigbee2MQTT frontend.
These devices are battery-powered end devices, and in Zigbee2MQTT their per-device availability is explicitly disabled.
Relevant Zigbee2MQTT configuration excerpt:
In Shellbee, both devices appear as:
In the Zigbee2MQTT frontend, they are visible and not marked as offline. They also work normally when pressed.
My guess is that Shellbee may be treating missing or stale availability data as offline, instead of respecting the per-device availability: false setting from Zigbee2MQTT. For battery-powered remotes, this causes false offline states.
Environment:
Expected behavior:
Devices with availability: false should probably not be shown as Offline, or should have a neutral/unknown availability state, matching Zigbee2MQTT's behavior.
Actual behavior:
Shellbee shows these devices as Offline.
Attachments