Bonjour,
J’ai acheté le Remotec ZRC-90EU ou BW8510EU et il m’est impossible de l’intégrer sur mon jeedom. J’ai fait la migration openzwave → zwavejs, j’ai mis tout à jour, j’ai tenté l’exclusion avant l’inclusion du module, le factory reset du module, une inclusion sécurisée ou non sécurisée, inclusion en appuyant sur le bouton L, ou sur L+R en même temps. J’ai même réalisé un échange avec le vendeur au cas où ce serait matériel. Mais c’est juste impossible. Il n’est pas juste mal configuré, il n’est même pas détecté. Il n’y a pas d’erreur dans les logs du plugin au niveau de jeedom, même abaissés au niveau debug.
J’ai trouvé plusieurs sujets identiques qui ont quasi tous étaient résolus et qui m’ont fait tester ces différentes solutions ci-dessus :
Bonjour,
J’ai acheté une contrôleur de scènes Remotec ZRC-90, je l’ai inclus sans problème, mais il n’est pas reconnu alors que je constate qu’il existe une configuration à cet endroit :
plugins/zwavejs/core/config/devices/remotec_21076/zrc-90.json
Voici le lien de ce que j’ai trouvé côté Z-Wave JS :
D’après un sujet sur home assistant, le problème pourrait provenir du fait que le nom de l’appareil a changé côté Z-Wave JS et qu’il s’appelle BW8510 alors qu’il s’appelait avant ZRC-90.
En to…
Bonjour à tous,
Je viens demander de l’aide, car j’ai un problème d’intégration de la télécommande ZCR-90EU BW85510EU pour lancer des scènes.
A voir sur les 3 télécommandes ont exactement les mêmes références inscrites dessus.
J’en ai 2 depuis ± 2ans et elles fonctionnent bien avec les 8*3 possibilités.
Elles ont 4 commandes Scene, SceneAttribute, SceneID, Batterie. elles sont bien reconnu comme ZRC-90.
Avec un scenario j’utilise les 18 actions possible de la télécommande.
Je viens d’en a…
bonjour tous le monde,
j’ai fait l’acquisition d’une télécommande zrc-90 de remotec.
elle n’est pas reconnu sur jeedom malgré qu’elle soit compatible.
j’ai controlé que le bouton soit sur « OP » et j’ai fait l’exclusion/inclusion en mode non sécurise, cela n’a pas fonctionné, j’ai rafraichie le nœud et du coup je me retrouve en « probe ».
j’ai mis à jour les dépendances de ma clé zwave aoetec Gen5 et refait exclusion/inclusion mais l’interrupteur n’est toujours pas reconnu.
j’ai essayé de c…
Le premier sujet cité me laisse perplexe vis à vis de ce potentiel changement de nom du module. J’ai aussi un fichier de config /var/www/html/plugins/zwavejs/core/config/devices/remotec_21076/zrc-90.json
alors qu’effectivement, il a l’air configuré avec son autre petit nom sur https://devices.zwave-js.io/?jumpTo=0x5254:0x0000:0x8510:0.0# . Mais bon, je ne sais pas trop quoi faire de cette information.
Mon jeedom est sur raspi4, et mon contrôleur zwave est un stick USB Everspring.
Est-ce que quelqu’un aurait la moindre piste s’il vous plait ? Sinon un produit de rechange ?
Merci.
Salut
Je n’ai pas lu les posts que tu as donnés mais as-tu testé la procédure decrite sur le dernier message de ce post? À priori, la procédure de reset de la doc n’est pas correcte.
ouvert 12:35PM - 04 Nov 22 UTC
fermé 12:08PM - 16 Nov 22 UTC
cannot fix ❌
### Is your problem within Home Assistant (Core or Z-Wave JS Integration)?
NO… , my problem is NOT within Home Assistant or the ZWave JS integration
### Is your problem within Z-Wave JS UI (formerly ZwaveJS2MQTT)?
NO, my problem is NOT within Z-Wave JS UI
### Checklist
- [X] I have checked the [troubleshooting section](https://zwave-js.github.io/node-zwave-js/#/troubleshooting/index) and my problem is **not** described there.
- [X] I have read the [changelog](https://github.com/zwave-js/node-zwave-js/blob/master/CHANGELOG.md) and my problem was **not** mentioned there.
### Describe the bug
What causes the bug?
????
What do you observe?
Device id is (0xXXXX-0xXXXX-0xXXXX) after interview.
Deleting the device, adding the device again, reinterview all result in the same. Only battery level/islow is reported.
What did you expect to happen?
Full recognision of remote with ID 0x5254-0x0001-0x8510
Steps to reproduce the behavior:
1. Go to '...' Device press wake button to keep it awake for 30 seconds
2. Click on '...' Reinterview
3. Scroll down to '...'
4. See error
Device ID
undefined-undefined-undefined (0xXXXX-0xXXXX-0xXXXX)
No buttons etc. are seen
### Device information
Manufacturer: Remotec
Model name: ZRC-90EU
Node ID in your network: 2
[Link](http://manuals-backend.z-wave.info/make.php?lang=en&sku=BW8510EU&cert=ZC10-15120001&type=mini)
Device ID
undefined-undefined-undefined (0xXXXX-0xXXXX-0xXXXX)
Expected device id from docs: 0x5254-0x0001-0x8510
(if manualy added this device ID to the XXXX.values.jsonl, and restart of docker, the device name shows up correctly , just without all buttons & events. When reinterviewed the device ID is wiped).
### How are you using `node-zwave-js`?
- [X] `zwave-js-ui` (formerly `zwavejs2mqtt`) Docker image (latest)
- [ ] `zwave-js-ui` (formerly `zwavejs2mqtt`) Docker image (dev)
- [ ] `zwave-js-ui` (formerly `zwavejs2mqtt`) Docker manually built _(please specify branches)_
- [ ] `ioBroker.zwave2` adapter _(please specify version)_
- [ ] `HomeAssistant zwave_js` integration _(please specify version)_
- [ ] `pkg`
- [ ] `node-red-contrib-zwave-js` _(please specify version, double click node to find out)_
- [ ] Manually built from GitHub _(please specify branch)_
- [ ] Other _(please describe)_
### Which branches or versions?
version:
zwave-js-ui: 8.2.2.4dd1414
zwave-js: 10.3.0
### Did you change anything?
yes (please describe)
### If yes, what did you change?
As debugging attempt, I tried manual adding the device id to the config, to no avail.
### Did this work before?
Don't know, for me this is a new device
The device was selected because it was on the supported list.
### If yes, where did it work?
_No response_
### Attach Driver Logfile
```
2022-11-04T11:55:28.640Z SERIAL « 0x010b000404020380035cc100eb (13 bytes)
2022-11-04T11:55:28.647Z SERIAL » [ACK] (0x06)
2022-11-04T11:55:28.653Z CNTRLR [Node 002] [~] [Battery] level: 92 => 92 [Endpoint 0]
2022-11-04T11:55:28.707Z CNTRLR [Node 002] [~] [Battery] isLow: false => false [Endpoint 0]
2022-11-04T11:55:28.738Z DRIVER « [Node 002] [REQ] [ApplicationCommand]
│ type: broadcast
└─[BatteryCCReport]
level: 92
is low: false
2022-11-04T11:55:40.828Z SERIAL « 0x010a00040002028407c400b6 (12 bytes)
2022-11-04T11:55:40.835Z SERIAL » [ACK] (0x06)
2022-11-04T11:55:40.841Z DRIVER « [Node 002] [REQ] [ApplicationCommand]
└─[WakeUpCCWakeUpNotification]
2022-11-04T11:55:40.847Z CNTRLR « [Node 002] received wakeup notification
2022-11-04T11:55:41.818Z SERIAL « 0x010a00040002028407c400b6 (12 bytes)
2022-11-04T11:55:41.826Z SERIAL » [ACK] (0x06)
2022-11-04T11:55:41.833Z DRIVER « [Node 002] [REQ] [ApplicationCommand]
└─[WakeUpCCWakeUpNotification]
2022-11-04T11:55:41.840Z CNTRLR « [Node 002] received wakeup notification
2022-11-04T11:55:42.829Z SERIAL « 0x010a00040002028407c400b6 (12 bytes)
2022-11-04T11:55:42.833Z SERIAL » [ACK] (0x06)
2022-11-04T11:55:42.837Z DRIVER « [Node 002] [REQ] [ApplicationCommand]
└─[WakeUpCCWakeUpNotification]
2022-11-04T11:55:42.840Z CNTRLR « [Node 002] received wakeup notification
2022-11-04T11:55:43.831Z SERIAL « 0x010a00040002028407c400b6 (12 bytes)
2022-11-04T11:55:43.838Z SERIAL » [ACK] (0x06)
2022-11-04T11:55:43.844Z DRIVER « [Node 002] [REQ] [ApplicationCommand]
└─[WakeUpCCWakeUpNotification]
2022-11-04T11:55:43.850Z CNTRLR « [Node 002] received wakeup notification
2022-11-04T11:55:44.276Z CNTRLR [Node 002] [+] [Node Naming and Location] name: "scenemaster"
2022-11-04T11:55:44.305Z CNTRLR [Node 002] [+] [Node Naming and Location] location: "kamer"
2022-11-04T11:55:44.336Z CNTRLR [Node 002] Beginning interview - last completed stage: None
2022-11-04T11:55:44.337Z CNTRLR [Node 002] new node, doing a full interview...
2022-11-04T11:55:44.355Z CNTRLR » [Node 002] querying protocol info...
2022-11-04T11:55:44.377Z SERIAL » 0x0104004102b8 (6 bytes)
2022-11-04T11:55:44.378Z DRIVER » [REQ] [GetNodeProtocolInfo]
payload: 0x02
2022-11-04T11:55:44.393Z SERIAL « [ACK] (0x06)
2022-11-04T11:55:44.398Z SERIAL « 0x01090141131601010106b4 (11 bytes)
2022-11-04T11:55:44.402Z SERIAL » [ACK] (0x06)
2022-11-04T11:55:44.406Z DRIVER « [RES] [GetNodeProtocolInfo]
payload: 0x131601010106
2022-11-04T11:55:44.422Z CNTRLR « [Node 002] received response for protocol info:
basic device class: Controller
generic device class: Remote Controller
specific device class: Simple Remote Control
node type: Controller
is always listening: false
is frequent listening: false
can route messages: false
supports security: false
supports beaming: true
maximum data rate: 100000 kbps
protocol version: 3
2022-11-04T11:55:44.458Z CNTRLR [Node 002] The node is now asleep.
2022-11-04T11:55:44.505Z CNTRLR [Node 002] Interview stage completed: ProtocolInfo
2022-11-04T11:55:44.506Z CNTRLR » [Node 002] querying node info...
2022-11-04T11:55:44.832Z SERIAL « 0x010a00040002028407c100b3 (12 bytes)
2022-11-04T11:55:44.837Z SERIAL » [ACK] (0x06)
2022-11-04T11:55:44.841Z DRIVER « [Node 002] [REQ] [ApplicationCommand]
└─[WakeUpCCWakeUpNotification]
2022-11-04T11:55:44.846Z CNTRLR « [Node 002] received wakeup notification
2022-11-04T11:55:44.873Z CNTRLR [Node 002] The node is now awake.
2022-11-04T11:55:44.902Z SERIAL » 0x010400600299 (6 bytes)
2022-11-04T11:55:44.904Z DRIVER » [Node 002] [REQ] [RequestNodeInfo]
payload: 0x02
2022-11-04T11:55:44.916Z SERIAL « [ACK] (0x06)
2022-11-04T11:55:44.920Z SERIAL « 0x01040160019b (6 bytes)
2022-11-04T11:55:44.924Z SERIAL » [ACK] (0x06)
2022-11-04T11:55:44.928Z DRIVER « [RES] [RequestNodeInfo]
payload: 0x01
2022-11-04T11:55:44.949Z SERIAL « 0x010900498402030101063c (11 bytes)
2022-11-04T11:55:44.951Z SERIAL » [ACK] (0x06)
2022-11-04T11:55:44.953Z DRIVER « [Node 002] [REQ] [ApplicationUpdateRequest]
payload: 0x0203010106
2022-11-04T11:55:44.965Z CNTRLR « [Node 002] node info received
supported CCs:
2022-11-04T11:55:44.996Z CNTRLR [Node 002] Interview stage completed: NodeInfo
2022-11-04T11:55:44.999Z CNTRLR [Node 002] Interviewing Wake Up...
2022-11-04T11:55:45.000Z CNTRLR » [Node 002] retrieving wakeup interval from the device...
2022-11-04T11:55:45.027Z SERIAL » 0x0109001302028405250342 (11 bytes)
2022-11-04T11:55:45.028Z DRIVER » [Node 002] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 3
└─[WakeUpCCIntervalGet]
2022-11-04T11:55:45.040Z SERIAL « [ACK] (0x06)
2022-11-04T11:55:45.043Z SERIAL « 0x0104011301e8 (6 bytes)
2022-11-04T11:55:45.044Z SERIAL » [ACK] (0x06)
2022-11-04T11:55:45.046Z DRIVER « [RES] [SendData]
was sent: true
2022-11-04T11:55:45.056Z SERIAL « 0x011800130300000200c47f7f7f7f000003000000000301000030 (26 bytes)
2022-11-04T11:55:45.058Z SERIAL » [ACK] (0x06)
2022-11-04T11:55:45.060Z DRIVER « [REQ] [SendData]
callback id: 3
transmit status: OK, took 20 ms
routing attempts: 1
protocol & route speed: Z-Wave, 100 kbit/s
ACK RSSI: -60 dBm
ACK channel no.: 0
TX channel no.: 0
2022-11-04T11:55:45.080Z SERIAL « 0x010e0004000206840600000001c400b6 (16 bytes)
2022-11-04T11:55:45.082Z SERIAL » [ACK] (0x06)
2022-11-04T11:55:45.090Z CNTRLR [Node 002] [Wake Up] wakeUpInterval: metadata updated [Endpoint 0]
2022-11-04T11:55:45.111Z CNTRLR [Node 002] [+] [Wake Up] wakeUpInterval: 0 [Endpoint 0]
2022-11-04T11:55:45.125Z CNTRLR [Node 002] [Wake Up] controllerNodeId: metadata updated [Endpoint 0]
2022-11-04T11:55:45.146Z CNTRLR [Node 002] [+] [Wake Up] controllerNodeId: 1 [Endpoint 0]
2022-11-04T11:55:45.161Z DRIVER « [Node 002] [REQ] [ApplicationCommand]
└─[WakeUpCCIntervalReport]
wake-up interval: 0 seconds
controller node id: 1
2022-11-04T11:55:45.168Z CNTRLR « [Node 002] received wakeup configuration:
wakeup interval: 0 seconds
controller node: 1
2022-11-04T11:55:45.170Z CNTRLR [Node 002] [+] [Wake Up] interviewComplete: true [Endpoint 0] [internal]
2022-11-04T11:55:45.201Z CNTRLR [Node 002] Interview stage completed: CommandClasses
2022-11-04T11:55:45.225Z CNTRLR [Node 002] Interview stage completed: OverwriteConfig
2022-11-04T11:55:45.258Z CNTRLR [Node 002] Interview completed
2022-11-04T11:55:45.300Z CNTRLR [Node 002] The node is ready to be used
2022-11-04T11:55:48.106Z SERIAL « 0x010a00040002028407c300b1 (12 bytes)
2022-11-04T11:55:48.112Z SERIAL » [ACK] (0x06)
2022-11-04T11:55:48.117Z DRIVER « [Node 002] [REQ] [ApplicationCommand]
└─[WakeUpCCWakeUpNotification]
2022-11-04T11:55:48.123Z CNTRLR « [Node 002] received wakeup notification
2022-11-04T11:55:49.107Z SERIAL « 0x010a00040002028407c100b3 (12 bytes)
2022-11-04T11:55:49.114Z SERIAL » [ACK] (0x06)
2022-11-04T11:55:49.119Z DRIVER « [Node 002] [REQ] [ApplicationCommand]
└─[WakeUpCCWakeUpNotification]
2022-11-04T11:55:49.124Z CNTRLR « [Node 002] received wakeup notification
2022-11-04T11:55:50.117Z SERIAL « 0x010a00040002028407c100b3 (12 bytes)
2022-11-04T11:55:50.123Z SERIAL » [ACK] (0x06)
2022-11-04T11:55:50.129Z DRIVER « [Node 002] [REQ] [ApplicationCommand]
└─[WakeUpCCWakeUpNotification]
2022-11-04T11:55:50.139Z CNTRLR « [Node 002] received wakeup notification
2022-11-04T11:55:51.119Z SERIAL « 0x010a00040002028407c100b3 (12 bytes)
2022-11-04T11:55:51.125Z SERIAL » [ACK] (0x06)
2022-11-04T11:55:51.130Z DRIVER « [Node 002] [REQ] [ApplicationCommand]
└─[WakeUpCCWakeUpNotification]
2022-11-04T11:55:51.136Z CNTRLR « [Node 002] received wakeup notification
2022-11-04T11:55:52.121Z SERIAL « 0x010a00040002028407c100b3 (12 bytes)
2022-11-04T11:55:52.129Z SERIAL » [ACK] (0x06)
2022-11-04T11:55:52.135Z DRIVER « [Node 002] [REQ] [ApplicationCommand]
└─[WakeUpCCWakeUpNotification]
2022-11-04T11:55:52.140Z CNTRLR « [Node 002] received wakeup notification
2022-11-04T11:55:53.112Z SERIAL « 0x010a00040002028407bb00c9 (12 bytes)
2022-11-04T11:55:53.118Z SERIAL » [ACK] (0x06)
2022-11-04T11:55:53.123Z DRIVER « [Node 002] [REQ] [ApplicationCommand]
└─[WakeUpCCWakeUpNotification]
2022-11-04T11:55:53.128Z CNTRLR « [Node 002] received wakeup notification
2022-11-04T11:55:54.112Z SERIAL « 0x010a00040002028407bc00ce (12 bytes)
2022-11-04T11:55:54.119Z SERIAL » [ACK] (0x06)
2022-11-04T11:55:54.124Z DRIVER « [Node 002] [REQ] [ApplicationCommand]
└─[WakeUpCCWakeUpNotification]
2022-11-04T11:55:54.129Z CNTRLR « [Node 002] received wakeup notification
2022-11-04T11:55:55.124Z SERIAL « 0x010a00040002028407b900cb (12 bytes)
2022-11-04T11:55:55.130Z SERIAL » [ACK] (0x06)
2022-11-04T11:55:55.135Z DRIVER « [Node 002] [REQ] [ApplicationCommand]
└─[WakeUpCCWakeUpNotification]
2022-11-04T11:55:55.140Z CNTRLR « [Node 002] received wakeup notification
2022-11-04T11:55:56.125Z SERIAL « 0x010a00040002028407bb00c9 (12 bytes)
2022-11-04T11:55:56.131Z SERIAL » [ACK] (0x06)
2022-11-04T11:55:56.136Z DRIVER « [Node 002] [REQ] [ApplicationCommand]
└─[WakeUpCCWakeUpNotification]
2022-11-04T11:55:56.141Z CNTRLR « [Node 002] received wakeup notification
2022-11-04T11:55:59.242Z SERIAL « 0x010b000404020380035cca00e0 (13 bytes)
2022-11-04T11:55:59.250Z SERIAL » [ACK] (0x06)
2022-11-04T11:55:59.257Z CNTRLR [Node 002] [Battery] level: metadata updated [Endpoint 0]
2022-11-04T11:55:59.291Z CNTRLR [Node 002] [+] [Battery] level: 92 [Endpoint 0]
2022-11-04T11:55:59.334Z CNTRLR [Node 002] [Battery] isLow: metadata updated [Endpoint 0]
2022-11-04T11:55:59.355Z CNTRLR [Node 002] [+] [Battery] isLow: false [Endpoint 0]
2022-11-04T11:55:59.374Z CNTRLR [Node 002] [Battery] chargingStatus: metadata updated [Endpoint 0]
2022-11-04T11:55:59.388Z CNTRLR [Node 002] [Battery] rechargeable: metadata updated [Endpoint 0]
2022-11-04T11:55:59.406Z CNTRLR [Node 002] [Battery] backup: metadata updated [Endpoint 0]
2022-11-04T11:55:59.450Z CNTRLR [Node 002] [Battery] overheating: metadata updated [Endpoint 0]
2022-11-04T11:55:59.482Z CNTRLR [Node 002] [Battery] lowFluid: metadata updated [Endpoint 0]
2022-11-04T11:55:59.515Z CNTRLR [Node 002] [Battery] rechargeOrReplace: metadata updated [Endpoint 0]
2022-11-04T11:55:59.534Z CNTRLR [Node 002] [Battery] disconnected: metadata updated [Endpoint 0]
2022-11-04T11:55:59.564Z CNTRLR [Node 002] [Battery] lowTemperatureStatus: metadata updated [Endpoint 0]
2022-11-04T11:55:59.585Z DRIVER « [Node 002] [REQ] [ApplicationCommand]
│ type: broadcast
└─[BatteryCCReport]
level: 92
is low: false
```
Antoine
Bonjour Antoine,
Merci pour le post. J’ai testé cette procédure de reset. ça ne marche pas mieux après, avec une inclusion sécurisée ou non.
J’ai remarqué, étonnement, que l’exclusion, elle est bien détectée. Le module comme le contrôleur réagissent en quelque secondes seulement. Donc je ne comprends vraiment pas d’où ça peut venir.
Merci.