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
But when I searched it, it is scanned as name any in ST app, and device type is recognized as edge driver of opple-switch-2.
I noticed that patterns like ^lumi.switch.l.aeu1 are used by device:get_model():find(fingerprint.model) only in opple subdriver code, but couldn't understand why it's happening.
To solve this issue, I had to remove every opple related code & lines from fingerprint.yml and subdriver setup, then I was able to use ST embedded DTH.
I also found another user is also reporting that his Si-Has sensors are also recognized as anyopple-switch-2, and those sensors should use DTH driver instead.
Would you please review this issue?
Thank you.
The text was updated successfully, but these errors were encountered:
It seems that any unknown device is always matched to
opple-switch-2
, and resulting that it is impossible to use DTH instead.I scanned a zigbee device which doesn't need external driver. It should use pre-embedded
easyiot Light
DTH driver in ST hub.But when I searched it, it is scanned as name
any
in ST app, and device type is recognized as edge driver ofopple-switch-2
.I noticed that patterns like
^lumi.switch.l.aeu1
are used bydevice:get_model():find(fingerprint.model)
only inopple
subdriver code, but couldn't understand why it's happening.To solve this issue, I had to remove every
opple
related code & lines fromfingerprint.yml
and subdriver setup, then I was able to use ST embedded DTH.I also found another user is also reporting that his Si-Has sensors are also recognized as
any
opple-switch-2
, and those sensors should use DTH driver instead.Would you please review this issue?
Thank you.
The text was updated successfully, but these errors were encountered: