You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I definitively want to report a bug within deCONZ or its REST-API
Is there already an existing issue for this?
I have searched the existing issues and there is none for the bug at hand
Describe the bug
With f9bd82f, DDF manufacturername matching becamse case insensitive to ease up the situation with differenct spellings of manufacturernames (see also #5903 (comment)). However, due to some internal deconz changes, his functionality got lost again. The anticipated fix (#7864) does apparently not restore an insensitive check.
Take a device you know the manufacturername of (exact spelling), which is NOT paired to deconz. Must have a valid DDF available
Modify the DDFs manufacturername and change capitalization of an arbitrary letter. Ensure the DDF does not contain a fitting manufacturername, spelling-wise.
Try to pair the device and watch it fail
Expected behavior
Manufacturername should be matched case-insensitive.
Screenshots
Environment
Host system: (Raspberry Pi / PC / NAS / MAC)
Running method: (Raspbian / Ubuntu / Home Assistent deCONZ Add-on / deconz-docker container / Windows / Virtual Machine)
Firmware version: (26xxyy00)
deCONZ version (not Home assistant Addon version!): (2.xx.yy)
Device: (ConBee I / ConBee II / ConBee III / RaspBee I / RaspBee II)
Do you use an USB extension cable: (yes / no) -- only relevant for ConBee I/II/III
Is there any other USB or serial devices connected to the host system? If so: Which?
deCONZ Logs
13:08:16:891 DEV no DDF for 0xCCCCCCFFFE393896, modelId: eTRV0100
Additional context
No response
The text was updated successfully, but these errors were encountered:
Does the issue really belong here?
Is there already an existing issue for this?
Describe the bug
With f9bd82f, DDF manufacturername matching becamse case insensitive to ease up the situation with differenct spellings of manufacturernames (see also #5903 (comment)). However, due to some internal deconz changes, his functionality got lost again. The anticipated fix (#7864) does apparently not restore an insensitive check.
Similar behavior discussed in #7949.
Steps to reproduce the behavior
Expected behavior
Manufacturername should be matched case-insensitive.
Screenshots
Environment
deCONZ Logs
13:08:16:891 DEV no DDF for 0xCCCCCCFFFE393896, modelId: eTRV0100
Additional context
No response
The text was updated successfully, but these errors were encountered: