Vimar 30801 (RemoteControl_v1.0) sends no Zigbee messages on button press

Aperta
  • Qualcosa non va?
#33,675 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
38/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
backend, networking

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

problem
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)
  1. Put the device in Zigbee mode and pair it with Z2M (permit join).
  2. Open the device in the frontend, tab Bind, bind endpoint 10 to the Coordinator.
  3. Press the button several times with log_level: debug.
  4. 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
Screenshot 2026-11-12 003520
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_seen and linkquality do not change when the button is pressed, so the device does not appear to transmit anything to the coordinator.
  • Reading attributes works: a genBasic read 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 with last_seen enabled and a successful bind.
Lingua principale
TypeScript
Stelle
15.8k
Fork
2.1k
Merge medio
1g 6h
PR unite (30g)
38

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Koenkk/zigbee2mqtt

Tutte le issue di Koenkk/zigbee2mqtt

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.