Smartthings AEOTEC V3 activity history

Is there someone who know how to look the AEOTEC V3 HUB activity.

I Have some problem or question s about what it do with some intégrated routine.

Thanks.

can you provide more details?

1 Like

Hello. Thanks to answer.

I would like to see aeotec v3 hub actibity to look at routine if some routine start as i want and with witch parameter.
I have sonoff znzb 02p and termostatique trvzb (sonoff). I controle trvzb with the znzb 02p with temperature level.
I saw that sometime the routine start but it seems not always on condition i put.
I m IT and i like to have service trace. Is there something like that with aeotec hub ?
Sorry for my english. I m french.

Thanks.

You can use SmartThings App History ( App Menu right side ).

It’s possible to use Filter

1 Like

Thanks
I have seen this history but it just say that routine start.
It donc show the sensor state or value.

If in the history shown here you see the routine runs then look up that time on the history tab of the device to see what it was reporting at that moment.
e.g.

1 Like

Hi, @Bruno1
If you compare the Routine execution time and the device history (as @Johnnybegoode mentioned) but it doesn’t show an event that could have trigger it, we can open an investigation with the engineering team to know why it is executing.
To do so, we need the following info:

  1. Name of the Routine
  2. Date and time of the execution along with a screenshot of the location history. Please share your timezone so we can convert the time properly to look at the logs
  3. Screenshot of the device history that appears in the SmartThings app to compare the name and the time.
  4. Open support access to your account:

Another option you have is to show us the Routine and tell us how it isn’t working as you expect it to.

It is common for Routines not to behave as we expect, and we often have different expectations from each other. A condition also has to be described in a single short phrase which often doesn’t cover the different circumstances in which the condition may be evaluated, and so it can be misleading.

Sorry for the late reply.

I applied a simple principle: divide and conquer.

I simplified the routines to observe their behavior and created logic diagrams to verify the interactions between them. It's working better now. I have other problems, but they're with Samsung devices, not with routines.

Thank you.