I set it to 30, 3600, 100, which is how I had this sensor with the custom DTH and it worked fine all night.
I have seen that it does not send temperature event in the configuration response, showing 0.0ºC until it sends it in the next configured interval.
If you think it is necessary and you want to move these posts to another new thread about Configuration of custom reports.
As an update of the comparison of the battery consumption of the st multipurpose sensor with the default configuration values of Temperature reports (30, 300, 0x10) and the custom one with the code that you sent me with the subdriver (30, 3600, 100):
Default setting (30 sec, 300 sec, 0.1º):
In 4 days it consumed 15% of battery.
Custom configuration (30 sec, 3600 sec, 1°):
In 5 days 0% battery consumption
I still have it installed in case you want updating the consumption data.
In case it is taken into account for the final version of driver of st multipurpose sensor.
Thank you for your feedback. I already reported the concerns about the default values, the engineering team will analyze the next steps regarding this matter.
I can’t replicate the error, the list of my drivers is showing correctly, have you reported this to the Customer Support team? There might be a global issue that is causing the Automation deletion and this behavior.
I agree it’s weird, I’ll be monitoring it and checking if someone else reports it.
I have not been updated either,
but I have noticed since today that when you change the driver with the app tool, all the drivers that are in the hub no longer appear:
If there is no drive compatible with your device, the list appears empty, but if you click in search magnifying glass,all the hub drivers appear.
If there is any, the device label that device has in the fringerprint.yml, appears as many times as drivers find with that label in fingerprints.yml.
If you click on one of them, the compatible driver is loaded different from the one you have installed so that you accept it or not.
It doesn’t seem like a mistake to me.
It seems like an improvement to me, but it is unclear.
A text could come out saying: there are these compatible drivers for this device.
Now it shows the device label, matching in the Hub drivers.
In this case, exist other driver compatible for “Lidl Bulb’”.
By clicking on the label app choose the compatible driver to install.
In this example Two drivers compatibles found for “Lidl Bulb”
It should show the names of the compatible drivers instead of the device label
If you click on the magnifying glass, it shows you all the ones in the hub, as before.
@Mariano_Colmenarejo , @nayelyz
Could you share how to execute integration tests? I’ve searched everywhere but docs (
Driver Tests — SmartThings Edge Device Drivers documentation) only describe the codding itself.
I have always tested with real devices
I can’t help you in this
Do you mean to what is described in this document?
I suggest you check the
/test directory of the drivers released by SmartThings. Eg:
This file has been truncated.
-- Copyright 2022 SmartThings
-- Licensed under the Apache License, Version 2.0 (the "License");
-- you may not use this file except in compliance with the License.
-- You may obtain a copy of the License at
-- Unless required by applicable law or agreed to in writing, software
-- 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.
-- Mock out globals
local test = require "integration_test"
local zigbee_test_utils = require "integration_test.zigbee_test_utils"
local clusters = require "st.zigbee.zcl.clusters"
local IASZone = clusters.IASZone
local TemperatureMeasurement = clusters.TemperatureMeasurement
@nayelyz . The question is how to execute the tests.
When the access to the channels and drivers came to work, I have seen that they have also fixed this problem.
Now when you are going to change a driver for another, the names of the device compatible drivers appear and not the device Labels as before.
Better this way
Please help… Change driver is not working. I’m getting a blank screen
Changing to ZigBee Thing MC .
This is a know Android problem since the last app update
I found a walkaround . You can use CLI to do the change using the following command:
smartthings edge:drivers:switch [DEVICEID]
Worked for me…
@dotan_shai Great! That’s what I was looking for. I had searched for this command in smartthings-cli but I didn’t find it because it was added about month ago. After updating the cli it works fine.
Really now every user who needs to change a edge driver needs to learn CLI because smartthings broke the app?
I found a walkaround
This used to work well and will be fixed , probably , in next the Android App release
Hi, everyone, please follow this thread where there’s a discussion about the latest version of the app:
Hi! Just reposting here in case you’re not following the other thread:
Hello everyone, the hotfix for the change driver tool was released some hours ago, please let me know if this works for you. I just made a test and the menu appears correctly, in my case, I had to reinstall the app (Android only) but you can check if it works by deleting the cache first (Android). Here’s the evidence: