Can not have several devices with the same driver

veonua · September 1, 2021, 12:33pm

I have been able to connect my first motion sensor but when I try to connect the second one is visible in the hub event list, but never appears in the logcat

2021-09-01 2:20:42.000 PM CEST
moments ago HUB read attr - raw: 66900104060800001801, dni: 6690, endpoint: 01, cluster: 0406, size: 8, attrId: 0000 read attr - raw: 669001040608… read attr - raw: 66900104060800001801, dni: 6690, endpoint: 01, cluster: 0406, size: 8, attrId: 0000, result: success, encodin…
2021-09-01 2:20:37.000 PM CEST
moments ago HUB read attr - raw: 66900104060800001801, dni: 6690, endpoint: 01, cluster: 0406, size: 8, attrId: 0000 read attr - raw: 669001040608… read attr - raw: 66900104060800001801, dni: 6690, endpoint: 01, cluster: 0406, size: 8, attrId: 0000, result: success, encodin…
2021-09-01 2:20:30.000 PM CEST
moments ago HUB read attr - raw: 66900104060800001801, dni: 6690, endpoint: 01, cluster: 0406, size: 8, attrId: 0000 read attr - raw: 669001040608… read attr - raw: 66900104060800001801, dni: 6690, endpoint: 01, cluster: 0406, size: 8, attrId: 0000, result: success, encodin…
2021-09-01 2:20:26.000 PM CEST
moments ago HUB catchall: 0104 0000 01 01 0000 00 8778 00 01 115F 0A 01 01FF421A0121A90B0328220421A8430521C105062401 catchall: 0104 0000 01 01 000… catchall: 0104 0000 01 01 0000 00 8778 00 01 115F 0A 01 01FF421A0121A90B0328220421A8430521C105062401000000000A21C2BD
2021-09-01 2:20:14.000 PM CEST
moments ago HUB read attr - raw: 66900104060800001801, dni: 6690, endpoint: 01, cluster: 0406, size: 8, attrId: 0000 read attr - raw: 669001040608… read attr - raw: 66900104060800001801, dni: 6690, endpoint: 01, cluster: 0406, size: 8, attrId: 0000, result: success, encodin…
2021-09-01 2:20:08.000 PM CEST
moments ago HUB read attr - raw: 66900104060800001801, dni: 6690, endpoint: 01, cluster: 0406, size: 8, attrId: 0000 read attr - raw: 669001040608… read attr - raw: 66900104060800001801, dni: 6690, endpoint: 01, cluster: 0406, size: 8, attrId: 0000, result: success, encodin…
2021-09-01 2:20:02.000 PM CEST
moments ago HUB read attr - raw: 66900104060800001801, dni: 6690, endpoint: 01, cluster: 0406, size: 8, attrId: 0000 read attr - raw: 669001040608… read attr - raw: 66900104060800001801, dni: 6690, endpoint: 01, cluster: 0406, size: 8, attrId: 0000, result: success, encodin…
2021-09-01 2:20:00.000 PM CEST
moments ago HUB raw:66900000158D00014D0EF2, dni:6690, errorCode:00, ieee:00158D00014D0EF2 raw:66900000158D00014D0EF2, d… raw:66900000158D00014D0EF2, dni:6690, errorCode:00, ieee:00158D00014D0EF2

nayelyz · September 1, 2021, 2:25pm

Hi! Are you using the Motion Sensor Driver included here, or a custom Driver?
The logs related to Drivers might not be shown completely in the IDE because they’re not fully supported there.
Both devices are from the same manufacturer and are the same model?

veonua · September 1, 2021, 3:27pm

I am trying to implement Xiaomi Motion sensor. There is not much code added on top of the given example.

I’ve added this to fingerprint

- id: "lumi/motion"
    deviceLabel: Xiaomi Motion Sensor
    manufacturer: LUMI
    model: lumi.sensor_motion
    deviceProfileName: motion-battery

veonua · September 1, 2021, 3:29pm

so how do I get a better log?
It seems like the device is connected to hub but it’s not associated to the driver
With groovy IDE it was clear how to link device to driver.

nayelyz · September 1, 2021, 4:47pm

If you didn’t receive any logs in the CLI > logcat command, this means the Driver wasn’t called and it can be because the device fingerprint didn’t match.
Are you working with is this one?
https://www.mi.com/global/mi-motion-activated-night-light-2/

veonua · September 1, 2021, 6:30pm

I have all the logs for the first device. this means the driver is called and works

I am working with Mi Motion Sensor - Xiaomi Norway

veonua · September 1, 2021, 6:32pm

how can I see the device fingerprint?
this is the groovy DTH that works fine

github.com

bspranger/Xiaomi/blob/master/devicetypes/bspranger/xiaomi-aqara-motion-sensor.src/xiaomi-aqara-motion-sensor.groovy#L40


      
              capability "Battery"
              capability "Sensor"
              capability "Health Check"
          
              attribute "lastCheckin", "String"
              attribute "lastCheckinDate", "String"
              attribute "lastMotion", "String"
              attribute "light", "number"
              attribute "batteryRuntime", "String"
          
              fingerprint endpointId: "01", profileId: "0104", deviceId: "0107", inClusters: "0000,FFFF,0406,0400,0500,0001,0003", outClusters: "0000,0019", manufacturer: "LUMI", model: "lumi.sensor_motion.aq2", deviceJoinName: "Xiaomi Aqara Motion Sensor"
              fingerprint profileId: "0104", deviceId: "0104", inClusters: "0000, 0400, 0406, FFFF", outClusters: "0000, 0019", manufacturer: "LUMI", model: "lumi.sensor_motion", deviceJoinName: "Xiaomi Aqara Motion Sensor"
          
              command "resetBatteryRuntime"
              command "stopMotion"
          }
          
          simulator {
          }
          
          tiles(scale: 2) {

nayelyz · September 1, 2021, 7:34pm

I believe this is what is missing, one fingerprint has the model lumi.sensor_motion but the other adds aq2 at the end. You could add both to see which one is correct.

veonua · September 1, 2021, 7:43pm

 - id: "lumi/motion"
    deviceLabel: Xiaomi Motion Sensor
    manufacturer: LUMI
    model: lumi.sensor_motion
    deviceProfileName: motion-battery  
  - id: "lumi/motionAq2"
    deviceLabel: Aqara Motion Illuminance Sensor
    manufacturer: LUMI
    model: lumi.sensor_motion.aq2
    deviceProfileName: motion-battery-illuminance

the result is the same. the device is “connected”. It writes to the hub events, not to the edge driver logcat.
so likely the matching mechanism does not allow to associate the second device to the same driver. Could you please advice how do I get a log from the association service.

nayelyz · September 1, 2021, 8:04pm

ooh, ok. So a “dummy” device is created but it only says “Connected” and there are no logs in logcat, correct?

Can you check the device status in the API, please? (Have you done it before?)
https://api.smartthings.com/v1/devices/{deviceId}/status

veonua · September 2, 2021, 10:31am

I am not sure if a “dummy” was created, but I can see the zigbee commands form this device in the hub events log SmartThings. Add a little smartness to your things.

Unfortunately I have no knowledge how to use the API, I suppose it’s token protected.
And also I do not know the {deviceId} for the device

Mariano_Colmenarejo · September 2, 2021, 4:26pm

@nayelyz ,
I have connected 2 devices to the same edge drive “zigbee smoke sensor” and the events of the two devices are seen in the logcat of the same driver.

By the way, when you have 2 edge drivers compatible with a device, even if they have custom modifications in the code, the device is paired with one of them. Is there a routine in the Hub to choose the driver to connect to?
In this case, the new device has been connected to the same driver that already had a device connected. Is this a condition to choose that driver?
Thanks

nayelyz · September 2, 2021, 4:57pm

ok, I made some tests and adding the fingerprint is only one step for the acceptance of the device.
As this Driver uses sub-drivers, you need to add one for your device, you can copy an existing one, but it’s important you change the can_handle function adding the corresponding manufacturer (“mfr”) and model. Otherwise, it won’t be recognized as compatible. Eg.

github.com

SmartThingsCommunity/SmartThingsEdgeDrivers/blob/main/drivers/SmartThings/zigbee-motion-sensor/src/nyce/init.lua#L20

    
      
          -- distributed under the License is distributed on an "AS IS" BASIS,
          -- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
          -- See the License for the specific language governing permissions and
          -- limitations under the License.
          
          
local capabilities = require "st.capabilities"
          local zcl_clusters = require "st.zigbee.zcl.clusters"
          local battery_defaults = require "st.zigbee.defaults.battery_defaults"
          local OccupancySensing = zcl_clusters.OccupancySensing
          
          
local ZIGBEE_NYCE_MOTION_SENSOR_FINGERPRINTS = {
            { mfr = "NYCE", model = "3041" },
            { mfr = "NYCE", model = "3043" },
            { mfr = "NYCE", model = "3045" }
          }
          
          
local is_zigbee_nyce_motion_sensor = function(opts, driver, device)
            for _, fingerprint in ipairs(ZIGBEE_NYCE_MOTION_SENSOR_FINGERPRINTS) do
                if device:get_manufacturer() == fingerprint.mfr and device:get_model() == fingerprint.model then
                    return true
                end

nayelyz · September 2, 2021, 5:03pm

Why do you have two, one is from the public Drivers and the other is a custom one?
When you install the device, which Driver is selected?

Drivers are not used only for one device, several devices can be handled by the same Driver (they only have to be compatible with it). Each device is differenced by an ID they get when they’re installed.

Mariano_Colmenarejo · September 2, 2021, 5:38pm

I have 2 drivers because they are part of beta testing. The developer can’t think of all the things that can go through a user’s head, hahahaha …

I have been on both sides throughout my professional life and users are unpredictable.

The two drivers are modified, since the official beta does not have the fingerprint of my sensor.

He chose the one that already had a sensor connected.

I made a different version to test how the driver change tool worked in the app.
I made another version thinking of giving a solution with edge drivers, what I have solved with custom DTHs, and that in the future I may have different temperature sensors that need different configurations and as it is not clear that it can be done easily, it would have to have different drivers for different sensors.
By the way, the multipurpose sensor with the Driver default temperature reports configuration has consumed 15% battery in 3 days. This is not acceptable. There are tens of thousands of these sensors around the world!

In short, these are questions that arise during the tests, such as if the hub chooses a driver and you need another different, I can change it with the app tool, but the app tool does not perform doConfigure, as IDE does with DTHs updated.
That is why in another post it asked as convenient that driverSwitched handler also execute doConfigure or execute doConfigure with a tile, as in the classic app or a setting device menu option.

Thank you very much, I think you are doing an incredible job answering all our questions

veonua · September 2, 2021, 5:55pm

I thought there already will be some logging when can_handle comes into a game.

however, I have a code like yours

local ZIGBEE_LUMI_MOTION_SENSOR_FINGERPRINTS = {
    { mfr = "LUMI", model = "lumi.sensor_motion" },
    { mfr = "LUMI", model = "lumi.sensor_motion.aq2" }
}

nayelyz · September 2, 2021, 5:58pm

Whenever you make changes to the Driver and you don’t delete it but only:

Package the driver
Assign it to the channel again
Install it again (through the CLI)

It might take some time to update.

veonua · September 2, 2021, 6:16pm

well, my driver is like that for several days. also, I’ve rebooted my hab a couple of times.
so it is likely a fingerprint issue, and it would be good to be able to debug this case.

Topic		Replies	Views
[SmartThings Edge] Issue after several drivers updates Writing Edge Drivers	4	580	April 1, 2022
[ST Edge] Issue while trying to change the device's driver Writing Edge Drivers support	20	2021	October 12, 2022
Original ST Multisensors (can't rejoin) - Nov 2022 Devices & Integrations	12	693	November 16, 2022
Multi-Hub Question - Drivers on Secondary Hubs Connected Things	18	334	March 17, 2024
SmartThings Edge Developer Beta \| Known Issues and Bug Tracking Support edge-device	139	12435	December 12, 2022

Can not have several devices with the same driver

Related topics