Interviews, what are they for?

[Mirar]

One of the biggest annoyances with z-way-server is the interviews. Lots of devices have problems getting interviewed, and z-way-server doesn't always keep track of interviewed data (especially not after restoring a backup).

I thought for a while that the interview was learning things from the devices that were necessary to keep the radio up and to send the correct packets. It doesn't seem to be the case, that works fine for other devices.

It can't be to pick the correct device description record. I have to do that manually on many devices.

So what is it for, and why do we have to do so much manual fuzz over getting things interviewed before z-way-server can accept that the devices still work?

(I tried searching the forum for this, but:

The following words in your search query were ignored because they are too common words: interview.

)

[fableman]

> It can't be to pick the correct device description record. I have to do that manually on many devices.

I got lots of different sensors and I always have to select manually . Using: rc15

[Mirar]

>I got lots of different sensors and I always have to select manually . Using: rc15

At least some of mine seems to find it automatically.

I have a few Aeon Labs Multisensor. Some of those find it automatically, some of those I have to set up manually. They are all the same, 1.18 sensors. Z-way-server keeps forgetting one of them ("number 4").