Closed lucius-the closed 1 year ago
I have making 2 versions of one Zigbee Controller Bridge and have implanted one light device for getting something in the ZHA GUI but its making the same bad light level setting on the cluster. Its one warning that is very harmful and can being ignored.
@TheJulianJES Shall we doing one quirk for the Sonoff repeater and deleting all cluster and only having Identity cluster so it can being used in the GUI ?
So just to confirm, 0x73B0
is the NWK id of the ZBDongle-E router? (and no entities were created in HA?)
Its have "0x0006" as in so at least one (light) switch.
Right. Completely missed this:
ZBDongle-E router is represented in HA as a being some kind of a dual light switch with colors to choose from
Yup, I think we can just remove all relevant clusters via a quirk then
@lucius-the Can you testing this custom quirk SonoffR.zip ? It shall deleting not needed clusters and you is not getting any warnings then the system is loading.
Uhm... how do I test this quirk ? Where do I need to put files from the ZIP ?
Set up local quirk in (Z)HA and putting the unzipped file in the directory and restart HA. Instruction https://github.com/zigpy/zha-device-handlers/discussions/693#discussioncomment-857274.
Sorry i see that i have missing the second endpoint so its not working and i need fixing it.
Updated quirk with endpoint 2 SonoffR.zip.
@lucius-the Can you posting one link to the router firmware you have installed ? I was looking on the normal one and im missing some functions so i dont knowing if its the same.
I used this firmware for router: https://github.com/itead/Sonoff_Zigbee_Dongle_Firmware/tree/master/Dongle-E/Router
I'll try to use the new quirk now, following your instructions and will report back
Hm. I tried with the new quirk, now I'm getting:
Logger: homeassistant.config_entries
Source: components/zha/core/gateway.py:174
First occurred: 19:17:38 (1 occurrences)
Last logged: 19:17:38
Error setting up entry SONOFF Zigbee 3.0 USB Dongle Plus V2 for zha
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 382, in async_setup
result = await component.async_setup_entry(hass, self)
File "/usr/src/homeassistant/homeassistant/components/zha/__init__.py", line 111, in async_setup_entry
await zha_gateway.async_initialize()
File "/usr/src/homeassistant/homeassistant/components/zha/core/gateway.py", line 189, in async_initialize
raise exc
File "/usr/src/homeassistant/homeassistant/components/zha/core/gateway.py", line 174, in async_initialize
self.application_controller = await app_controller_cls.new(
File "/usr/local/lib/python3.10/site-packages/zigpy/application.py", line 163, in new
await app._load_db()
File "/usr/local/lib/python3.10/site-packages/zigpy/application.py", line 80, in _load_db
await self._dblistener.load()
File "/usr/local/lib/python3.10/site-packages/zigpy/appdb.py", line 581, in load
await self._load_unsupported_attributes()
File "/usr/local/lib/python3.10/site-packages/zigpy/appdb.py", line 634, in _load_unsupported_attributes
ep = dev.endpoints[endpoint_id]
KeyError: 2
And below it:
Logger: homeassistant.components.zha.core.gateway
Source: components/zha/core/gateway.py:174
Integration: Zigbee Home Automation ([documentation](https://www.home-assistant.io/integrations/zha), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+zha%22))
First occurred: 19:17:32 (3 occurrences)
Last logged: 19:17:38
Couldn't start EZSP = Silicon Labs EmberZNet protocol: Elelabs, HUSBZB-1, Telegesis coordinator (attempt 1 of 3)
Couldn't start EZSP = Silicon Labs EmberZNet protocol: Elelabs, HUSBZB-1, Telegesis coordinator (attempt 2 of 3)
Couldn't start EZSP = Silicon Labs EmberZNet protocol: Elelabs, HUSBZB-1, Telegesis coordinator (attempt 3 of 3)
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/zha/core/gateway.py", line 174, in async_initialize
self.application_controller = await app_controller_cls.new(
File "/usr/local/lib/python3.10/site-packages/zigpy/application.py", line 163, in new
await app._load_db()
File "/usr/local/lib/python3.10/site-packages/zigpy/application.py", line 80, in _load_db
await self._dblistener.load()
File "/usr/local/lib/python3.10/site-packages/zigpy/appdb.py", line 581, in load
await self._load_unsupported_attributes()
File "/usr/local/lib/python3.10/site-packages/zigpy/appdb.py", line 634, in _load_unsupported_attributes
ep = dev.endpoints[endpoint_id]
KeyError: 2
Great i hope i have getting all parameters OK and the quirk is being loaded. Then i renaming the device class to itead router then its one more model out there with model xsp1989 https://github.com/xsp1989/zigbeeFirmware/blob/master/firmware/Zigbee3.0_Dongle-NoSigned/RouterForDongle/efr32mg21_zigbee_router_6.7.10.gbl also as signed for origianl Sonoff ZBB.
That i have not seen before and i was testing the quirk on one of my test system. ZHA is trying loading the device from the database with the old config and cant finding all parts then i have deleting them. Can you deleting the router and waiting one minute so the database is writing the deletion and then adding it new ?
Yes, but I'll have to try this in a few hours, can't do now...
Ok, so I have deleted the SONOFF router device and waited a few minutes. Now I've re-activated the quirks again and restarted HA. Starts without issues. Joined the SONOFF router device. Now it's not showing the light objects any more.
However, 5 of my end devices (that were connected through this router) seem to be disconnected now... There are all Aqara senzors, was difficult to get them joined. I will wait and see if they reconnect. At the moment they are not reporting on motion detect.
I only got this in HA logs now:
Logger: zigpy.appdb
Source: runner.py:120
First occurred: 21:16:24 (1 occurrences)
Last logged: 21:16:24
Discarding _save_attribute event
Also got this:
Logger: bellows.thread
Source: runner.py:120
First occurred: 21:18:05 (1 occurrences)
Last logged: 21:18:05
Attempted to use a closed event loop
and this:
Logger: homeassistant
Source: /usr/src/homeassistant/homeassistant/runner.py:97
First occurred: 21:18:10 (1 occurrences)
Last logged: 21:18:10
Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/local/lib/python3.10/asyncio/tasks.py", line 456, in wait_for
return fut.result()
asyncio.exceptions.CancelledError
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/bellows/ezsp/v8/__init__.py", line 51, in pre_permit
await self.setPolicy(
File "/usr/local/lib/python3.10/asyncio/tasks.py", line 458, in wait_for
raise exceptions.TimeoutError() from exc
asyncio.exceptions.TimeoutError
In HA logs. I think I wasn't getting these before, but can't be 100% sure...
Aqara device is not jumping to one other router is its parent is offline they silent leaving the network without saying god by. If they is having one paring / reset button press it briefly and the LED is blinking and they is jumping to one router in the near. If its not working you need repairing them without deleting them. Sorry for that :-((
The error is initiating the network and have with permit joining but i have not seen it before and i dont knowing the code. If all is working i think its OK.
Ok, I'll wait and see if they reconnect, if not will try pairing again (with these devices it rarely goes fine from first) but ok ! Thank you for a quick solution !
Also, do I need to keep this in quirks or will it be merged with some next release (and then I have to remove it or something?)
Great !! I doing one PR with the quirk and changing the name so we can adding the second version then its coming. Then the PR is merged and (Z)HA is updating with it in you shall deleting the local quirk for not getting problems in the future (local quirk is overriding ZHA ones) if somthing is changed in ZHA.
Is there already a PR for this?
PR made with last reported working quirk and "branding" the device class Itead.
I do see that this ZBDongle-E router is represented in HA as a being some kind of a dual light switch with colors to choose from. There are no switches and lights, of course, it's just a stick, flashed with router firmware, plugged into a USB power supply that's plugged in to a wall socket.
If possible, could you check if (without the quirk) the dimmable light entity dims the on-board LED?
@lucius-the Can you check (without the quirk) if the dimmable light entity dims the on-board LED?
Z2M seems to expose that option and if we just remove it, we could break functionality for some.
@TheJulianJES At the moment not possible for me, been extremely busy with work, come home only to sleep... And removing quirk means repairing all Zigbee devices again, so really have no time for that currently.
My device actually doesn't have any LED-s, at least not any visible ones. Maybe on th board inside there are some LED-s. For me personally, I don't mind f you put them back - I only opened this issue because of instructions to do so were shown in the logs. It's not that something wasn't working ;)
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
After update 2023.10.1 I'm getting the same error on my ZBDongle-E in router mode.
2023-10-10 18:10:24.899 WARNING (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x3458:2:0x0300]: [Min mireds is 0, setting to 153] Please open an issue on the quirks repo to have this device corrected
The network address is also confirmed to be the ZBDongle.
Has this issue been addressed? I'm getting the same error on my Dongle-E in Router mode.
Same here, I am using the Dongle-E as well as a router and frequently getting the same message in the logs.
Message:
[Min mireds is 0, setting to 153] Please open an issue on the quirks repo to have this device corrected
I am using ZBDongle-E (plugged in my HomeAssistant PC) for a coordinator in ZHE. And using another ZBDongle-E, flashed in router mode, as a router to extend range. Because all of my end devices are battery powered, I used a spare ZBDongle-E to make a router.
I am getting this in HA logs:
And for this reason I am posting here.
Device signature
```yaml { "node_descriptor": "NodeDescriptor(logical_type=Diagnostic information
```yaml { "home_assistant": { "installation_type": "Home Assistant Container", "version": "2023.1.2", "dev": false, "hassio": false, "virtualenv": false, "python_version": "3.10.7", "docker": true, "arch": "x86_64", "timezone": "Europe/Prague", "os_name": "Linux", "os_version": "5.15.83-1-pve", "run_as_root": true }, "custom_components": { "skodaconnect": { "version": "v1.2.3", "requirements": [ "skodaconnect>=1.3.4", "homeassistant>=2022.12.0" ] }, "frigate": { "version": "3.0.0", "requirements": [] }, "hacs": { "version": "1.29.1", "requirements": [ "aiogithubapi>=22.10.1" ] }, "uponor": { "version": "0.8.1", "requirements": [ "UponorJnap==0.1" ] } }, "integration_manifest": { "domain": "zha", "name": "Zigbee Home Automation", "config_flow": true, "documentation": "https://www.home-assistant.io/integrations/zha", "requirements": [ "bellows==0.34.6", "pyserial==3.5", "pyserial-asyncio==0.6", "zha-quirks==0.0.90", "zigpy-deconz==0.19.2", "zigpy==0.53.0", "zigpy-xbee==0.16.2", "zigpy-zigate==0.10.3", "zigpy-znp==0.9.2" ], "usb": [ { "vid": "10C4", "pid": "EA60", "description": "*2652*", "known_devices": [ "slae.sh cc2652rb stick" ] }, { "vid": "1A86", "pid": "55D4", "description": "*sonoff*plus*", "known_devices": [ "sonoff zigbee dongle plus v2" ] }, { "vid": "10C4", "pid": "EA60", "description": "*sonoff*plus*", "known_devices": [ "sonoff zigbee dongle plus" ] }, { "vid": "10C4", "pid": "EA60", "description": "*tubeszb*", "known_devices": [ "TubesZB Coordinator" ] }, { "vid": "1A86", "pid": "7523", "description": "*tubeszb*", "known_devices": [ "TubesZB Coordinator" ] }, { "vid": "1A86", "pid": "7523", "description": "*zigstar*", "known_devices": [ "ZigStar Coordinators" ] }, { "vid": "1CF1", "pid": "0030", "description": "*conbee*", "known_devices": [ "Conbee II" ] }, { "vid": "10C4", "pid": "8A2A", "description": "*zigbee*", "known_devices": [ "Nortek HUSBZB-1" ] }, { "vid": "0403", "pid": "6015", "description": "*zigate*", "known_devices": [ "ZiGate+" ] }, { "vid": "10C4", "pid": "EA60", "description": "*zigate*", "known_devices": [ "ZiGate" ] }, { "vid": "10C4", "pid": "8B34", "description": "*bv 2010/10*", "known_devices": [ "Bitron Video AV2010/10" ] } ], "codeowners": [ "@dmulcahey", "@adminiuga", "@puddly" ], "zeroconf": [ { "type": "_esphomelib._tcp.local.", "name": "tube*" }, { "type": "_zigate-zigbee-gateway._tcp.local.", "name": "*zigate*" }, { "type": "_zigstar_gw._tcp.local.", "name": "*zigstar*" }, { "type": "_slzb-06._tcp.local.", "name": "slzb-06*" } ], "dependencies": [ "file_upload" ], "after_dependencies": [ "onboarding", "usb", "zeroconf" ], "iot_class": "local_polling", "loggers": [ "aiosqlite", "bellows", "crccheck", "pure_pcapy3", "zhaquirks", "zigpy", "zigpy_deconz", "zigpy_xbee", "zigpy_zigate", "zigpy_znp" ], "is_built_in": true }, "data": { "ieee": "**REDACTED**", "nwk": 29616, "manufacturer": "SONOFF", "model": "DONGLE-E_R", "name": "SONOFF DONGLE-E_R", "quirk_applied": false, "quirk_class": "zigpy.device.Device", "manufacturer_code": 4742, "power_source": "Mains", "lqi": 152, "rssi": -62, "last_seen": "2023-01-16T15:50:10", "available": true, "device_type": "Router", "signature": { "node_descriptor": "NodeDescriptor(logical_type=Additional context This stick seems to work ok in router mode, because I am seeing that end devices are connected through it. I do see that this ZBDongle-E router is represented in HA as a being some kind of a dual light switch with colors to choose from. There are no switches and lights, of course, it's just a stick, flashed with router firmware, plugged into a USB power supply that's plugged in to a wall socket.
Reason I am posting here is because the logs are instructing me to do so. I guess there's a reason why those messages are logged, so... providing info as requested !