JmL
Novembre 12, 2022, 1:41
1
Bonjour,
Je souhaiterai partager mon expérience concernant la dernière version du plugin Deconz, version 2.19.01.tous les micromodule Aqara KO ou Reset ; inclusions down !
Grosse frayeur à 23h hier soir, plus aucuns modules opérationnels … tous les scénarios capout !
Pour solutionner, j’ai du disjoncter tous les micromodules Aqara, lancer la Conbee 2 en mode inclusion et remettre sous tension pour réappairer par pièces les modules.lumi.switch.l0agl1 ; solution trouvée mais …
Avez-vous une idée sur cet incident ? ai-je oublié de lire un sujet sur ces modules dans les changelogs ?
Merci à vous
Bon week-end
Oui connue et remonté déjà sous deconz. Ca devrait être corrigé avec la prochaine stable ou maintenant en beta avec la version d’hier :
opened 10:59AM - 25 Oct 22 UTC
closed 02:01AM - 31 Jan 23 UTC
stale
Bug report
<!--
- Use this issue template to report a bug in the deCONZ REST-API.
- A… nything that is not clearly a bug can implicate manual closure. For support we recommend the forum: https://forum.phoscon.de
- If you want to report a bug for the Phoscon App, please head over to: https://forum.phoscon.de
- Make sure not to remove any headers and fill the template completely. If you remove the headers, the issue will be auto-closed.
- If you're unsure if the bug fits into this issue tracker, please ask for advise in our Discord chat: https://discord.gg/QFhTxqN
- Please make sure sure you're running the latest version of deCONZ: https://github.com/dresden-elektronik/deconz-rest-plugin/releases
-->
## Describe the bug
<!--
Describe the issue you are experiencing here to communicate to the
maintainers. Tell us what you were trying to do and what happened.
Help us understand the issue by providing valuable context.
-->
After updating from 2.18.2 to 2.19.1 my Aqara T1 Switch doesn't work. https://www.aqara.com/en/single_switch_T1_no-neutral.html
In 2.18.2, and before, the switch was recognised as a light, I think this is correct.
But since the upgrade to 2.19.1, the switch appears as both a light and a switch, i.e. 2 entities are created. If you delete either one, the other is also removed. One of these entities is being exposed to home assistant, but it doesn't work. When attempting to switch it on/off in home assistant, I get the error message: -
_[545860309824] 3 /lights/3 resource, /lights/3, not available_
## Steps to reproduce the behavior
<!--
If the problem is reproducable, list the steps here:
1. Go to 'Phoscon HTTP GUI'
2. Click on 'Lights'
3. Scroll down to 'MasterBedroom Light | LUMI | lumi.switch.l0agl1'
4. Click on 'Switches'
5. Scroll down to 'lumi.switch.l0agl1 | LUMI | lumi.switch.l0agl1'
If the problem can't be reproduced and is sporadic, please provide some details
on how often and when the issue happens.
-->
1. Go to 'Phoscon HTTP GUI'
2. Click on 'Lights'
3. Scroll down to 'MasterBedroom Light | LUMI | lumi.switch.l0agl1'
4. Click on 'Switches'
5. Scroll down to 'lumi.switch.l0agl1 | LUMI | lumi.switch.l0agl1'
## Expected behavior
<!--
If applicable, describe what you expected to happen.
-->
I would expect to only see this exposed as a light, I think with two entities available, there is a clash somewhere.
## Screenshots
<!--
If applicable, add screenshots to help explain the problem.
-->
## Environment
<!--
The deCONZ and firmware versions are found in the Phoscon App: Menu -> Settings -> Gateway,
as well as in the deCONZ GUI: Menu > Help > About deCONZ.
-->
- Host system: Raspberry Pi 4 (8GB)
- Running method: Raspbian
- Firmware version: 26720700
- deCONZ version: 2.19.01
- Device: ConBee II
- Do you use an USB extension cable: yes
- Is there any other USB or serial devices connected to the host system? If so: Which? No
## deCONZ Logs
<!--
Debug logs can help to investigate certain problems like device pairing and communication issues.
Logging can be enabled on the command line as described in:
https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/deCONZ-debug-flags
Secondly, for versions above 2.05.87: In the deCONZ GUI: click Help > debug view. Output of APS,ZDP, ZCL and INFO can be handy.
-->
API Info: -
`
"8": {
"etag": "a16e0dcf3996a01210406c742d36c5df",
"hascolor": false,
"lastannounced": null,
"lastseen": "2022-10-25T10:57Z",
"manufacturername": "LUMI",
"modelid": "lumi.switch.l0agl1",
"name": "MasterBedroom Light",
"state": {
"alert": "none",
"on": false,
"reachable": true
},
"swversion": "0.0.0_0022",
"type": "On/Off light",
"uniqueid": "54:ef:44:10:00:07:62:80-01"
},
"ep": 41,
"etag": "9dcdf4cc905be1ee02ff03f24af4ebdb",
"lastannounced": null,
"lastseen": "2022-10-25T10:57Z",
"manufacturername": "LUMI",
"mode": 1,
"modelid": "lumi.switch.l0agl1",
"name": "lumi.switch.l0agl1",
"state": {
"buttonevent": null,
"lastupdated": "none"
},
"swversion": "0.0.0_0022",
"type": "ZHASwitch",
"uniqueid": "54:ef:44:10:00:07:62:80-29-0012"
}
`
## Additional context
<!--
If relevant, add any other context about the problem here, like network size, number of routers and end-devices
and what kind of devices/brands are in the network.
-->
system
Novembre 13, 2022, 2:21
4
Ce sujet a été automatiquement fermé après 24 heures suivant le dernier commentaire. Aucune réponse n’est permise dorénavant.