@nayelyz I am using the latest version. As I told you, the temperature history is relative, it works for an hour and then returns to 0º. at night it works like until 11:00 pm then it returns to 0º. During the day, it only works at around 12:30 a.m., then it returns to 0º
ok, the logs don’t contain any event for temperature measurement, only for motionSensor.
About this message, it means it’s not recognizing the command, so you might be using a CLI version where this command wasn’t added yet, have you verified you’re using the last one?
Also, please don’t use the symbol “[ ]” to wrap the device ID because you’ll get a syntax error.
About the events that are shown in the IDE, I see there are events for the temperature after the value of 0.0, so, you should be seeing the value change in the app.
@nayelyz I am using the latest version. As I told you, the temperature history is relative, it works for an hour and then returns to 0º. at night it works like until 11:00 pm then it returns to 0º. During the day, it only works at around 12:30 a.m., then it returns to 0º
ok, what I’m trying to check is if the device is sending this value at some point, the driver shouldn’t send it on its own unless there’s an issue with the conversion. So, you need to check in the logs the message received from the device and the result sent from the driver as a capability event for temperatureMeasurement around the hour you mention it stops working.
@nayelyz Hello, I send you in an annex what you asked for. Please I need help and get it working. Another thing that happens is that I cannot remove the light from the sensor. Before I could do it now it won’t let me,
───────────────────────────────────────────────────────────────────────────────
Time Component Capability Attribute Value
───────────────────────────────────────────────────────────────────────────────
2023-2-8 10:26:32 main motionSensor motion “active”
2023-2-8 10:25:57 main motionSensor motion “inactive”
2023-2-8 10:24:44 main motionSensor motion “active”
2023-2-8 10:21:03 main motionSensor motion “inactive”
2023-2-8 10:20:31 main motionSensor motion “active”
───────────────────────────────────────────────────────────────────────────────
2023-2-8 10:20:12 main motionSensor motion “inactive”
2023-2-8 10:18:05 main motionSensor motion “active”
2023-2-8 10:18:04 main motionSensor motion “inactive”
2023-2-8 10:17:03 main motionSensor motion “active”
2023-2-8 10:00:14 main illuminanceMeasurement illuminance 0 lux
───────────────────────────────────────────────────────────────────────────────
2023-2-8 10:00:14 main temperatureMeasurement temperature 0 °C
2023-2-8 9:56:38 main temperatureMeasurement temperature 16.2 °C
2023-2-8 9:50:36 main illuminanceMeasurement illuminance 265 lux
2023-2-8 9:38:32 main illuminanceMeasurement illuminance 371 lux
2023-2-8 9:23:28 main illuminanceMeasurement illuminance 269 lux
───────────────────────────────────────────────────────────────────────────────
2023-2-8 9:08:23 main illuminanceMeasurement illuminance 157 lux
2023-2-8 8:50:16 main motionSensor motion “inactive”
2023-2-8 8:49:14 main motionSensor motion “active”
2023-2-8 8:23:01 main motionSensor motion “inactive”
2023-2-8 8:21:12 main motionSensor motion “active”
────────────────────────────────────────
Hello, @Jesus_De_Oliveira
So sorry for the delay.
In the events you sent here, we can only see the generated event, it’s like the end of the process, so, we cannot know why, that can be seen only in the driver logs.
You can let the logcat capturing the logs from the time it might fail (Eg. 09:55 pm) and save them into a file directly with this command:
smartthings edge:drivers:logcat driverId --hub-address=xx.x.x > log.log
The file will be saved in the same place as the file of the CLI. You won’t see the logs on the screen because the console will be writing them in the file.
However, as you mentioned it only happens at a certain time, it is highly possible this is because the device reported it.
Also, we can ask the team to see if there’s something strange around the time the temperature drops to 0. To do so, please do the following:
- Send the Hub logs from the IDE after the issue happened (no more than 12 hours after), please:
- In the IDE, enter “my hubs”
- Enter the corresponding Hub and go to “view utilities”
- Click on “send” below "send hub logs
- Share your Hub ID so the team can look for those logs in the system. This is the one that appears on the IDE.