Vimar 30801 (RemoteControl_v1.0) sends no Zigbee messages on button press
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- backend, networking
Research direction
Start by reading the RemoteControl_v1.0 device definition and its converter tests, then check how Zigbee messages from this device are handled. Reproduce with the reported Vimar 30801 and inspect debug logs and endpoint 10 behavior; done means identifying whether it transmits button events to a generic coordinator and, if supported, publishing the expected action.
Written by the indexing model from the issue text.
Description
What happened?
I paired a brand new Vimar Linea View Wireless 30801 ("IoT connected electronic control", dual Bluetooth/Zigbee) with Zigbee2MQTT. It joins the network and is correctly recognized as RemoteControl_v1.0 (exposes only action), but pressing the button never produces any message: no action, no entry in the debug log, and last_seen does not update.
Steps already taken:
- Switched the device to Zigbee mode and installed the Zigbee firmware with the Vimar View Wireless app, then paired it to Z2M.
- Bound endpoint 10 to the Coordinator (genOnOff, genLevelCtrl, closuresWindowCovering): the bind succeeds, still no messages.
- Bound endpoint 10 to a Zigbee bulb (genOnOff): the bind succeeds, but the bulb does not react to the button.
LED behaviour when pressing the button: white flash
According to the official Vimar instruction sheet, if the control is not associated to the Zigbee hub, the LED turns red and the press has no effect. It is configured with the Amazon app for Zigbee, so I suspect it only sends commands to the hub it was associated with, ignoring generic bindings. I could not find any documentation or user report of this device working with a third party coordinator.
What did you expect to happen?
An action (on/off/toggle/...) published on zigbee2mqtt/<friendly_name> each time the button is pressed, as described in the device page for RemoteControl_v1.0.
How to reproduce it (minimal and precise)
- Put the device in Zigbee mode and pair it with Z2M (permit join).
- Open the device in the frontend, tab Bind, bind endpoint 10 to the Coordinator.
- Press the button several times with
log_level: debug. - Nothing is received.
Zigbee2MQTT version
2.14.2
Adapter firmware version
0x26580700
Adapter
ConBee2/RaspBee2 0x00212effff09cb45
Setup
Home assistant add on. Home assistant VM on ProxMox
Device database.db entry
No response
Debug log
With log_level: debug enabled, pressing the button 5+ times produces no log lines at all for this device (no "Received Zigbee message", no action, no errors). Below are the lines from the successful bind, so it is clear that the device itself is reachable:
[12/11/2026, 00:34:54] z2m: Successfully bound cluster 'genOnOff' from '0xf4ce360119d4cf4b' to 'Coordinator'
[12/11/2026, 00:34:54] z2m: Successfully bound cluster 'genBasic' from '0xf4ce360119d4cf4b' to 'Coordinator'
[12/11/2026, 00:34:54] z2m: Successfully bound cluster 'closuresWindowCovering' from '0xf4ce360119d4cf4b' to 'Coordinator'
[12/11/2026, 00:34:54] z2m: Successfully bound cluster 'genLevelCtrl' from '0xf4ce360119d4cf4b' to 'Coordinator'
[12/11/2026, 00:34:55] z2m: Successfully bound cluster 'genOnOff' from '0xf4ce360119d4cf4b' to 'Luce ufficio'
[12/11/2026, 00:35:00] z2m: Successfully bound cluster 'closuresWindowCovering' from '0xf4ce360119d4cf4b' to 'Coordinator'
[12/11/2026, 00:35:01] z2m: Successfully bound cluster 'genLevelCtrl' from '0xf4ce360119d4cf4b' to 'Coordinator'
[12/11/2026, 00:35:01] z2m: Successfully bound cluster 'closuresWindowCovering' from '0xf4ce360119d4cf4b' to 'Coordinator'
[12/11/2026, 00:35:01] z2m: Successfully bound cluster 'genOnOff' from '0xf4ce360119d4cf4b' to 'Coordinator'
[12/11/2026, 00:35:01] z2m: Successfully bound cluster 'genLevelCtrl' from '0xf4ce360119d4cf4b' to 'Coordinator'
[12/11/2026, 00:35:01] z2m: Successfully bound cluster 'genOnOff' from '0xf4ce360119d4cf4b' to 'Coordinator'
[12/11/2026, 00:35:07] z2m: Successfully bound cluster 'closuresWindowCovering' from '0xf4ce360119d4cf4b' to 'Coordinator'
[12/11/2026, 00:35:07] z2m: Successfully bound cluster 'genLevelCtrl' from '0xf4ce360119d4cf4b' to 'Coordinator'
[12/11/2026, 00:35:07] z2m: Successfully bound cluster 'genOnOff' from '0xf4ce360119d4cf4b' to 'Coordinator'
[12/11/2026, 00:35:29] z2m: Successfully bound cluster 'genOnOff' from '0xf4ce360119d4cf4b' to 'Luce ufficio'
Notes
Additional info
- Device model: Vimar 30801, Zigbee model/manufacturer as shown in the Z2M device page: https://www.zigbee2mqtt.io/devices/RemoteControl_v1.0.html
- Clusters tab screenshot attached (output clusters of endpoint 10).
- Has anyone got a View Wireless push button (30801 / 30804) working with Z2M without an Amazon/Vimar hub? Any hint on how it must be configured would be appreciated.
last_seenandlinkqualitydo not change when the button is pressed, so the device does not appear to transmit anything to the coordinator.- Reading attributes works: a
genBasicread returns{"deviceEnabled":1,"zclVersion":8,"manufacturerName":"Vimar","swBuildId":"1.1.1_z","modelId":"RemoteControl_v1.0"}. So the coordinator can query the device, but button presses never generate any incoming message, even withlast_seenenabled and a successful bind.
- Dominant language
- TypeScript
- Stars
- 15.8k
- Forks
- 2.1k
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 38
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Koenkk/zigbee2mqtt
-
[Feature request]: OTA for generated definitions of devices with an OTA client clusterPossibly taken @jabla claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Koenkk/zigbee2mqtt#33684 · 1 comment ·
Maintainers usually reply within 1 day
-
new device support
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Koenkk/zigbee2mqtt#33674 · 1 comment ·
Maintainers usually reply within 1 day
-
[Feature request]: Support espzb adapter (ESP Zigbee SDK v2, ESP32-S31)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Koenkk/zigbee2mqtt#33668 ·
Maintainers usually reply within 1 day
-
problem
Difficulty 1/5 Under an hour Newbie friendliness 76/100
Koenkk/zigbee2mqtt#33645 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Koenkk/zigbee2mqtt#33613 · 2 comments ·
Maintainers usually reply within 1 day
All issues in Koenkk/zigbee2mqtt
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vercel-labs/ui#540 ·
Maintainers usually reply within 1 day
-
accepted ai-dev ai-implementing
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
livesport/homer#218 · 1 comment ·
Maintainers usually reply within 1 day
-
normalizePropName strips `#` characters from Figma property names instead of only the `#id` suffixOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
figma/code-connect#419 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Negative values skip k/M abbreviation and medium decimal format on line, stacked-area, and tooltipOpen
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
britecharts/britecharts#1255 ·
Maintainers usually reply within 1 day