What is the HomeID?

[Plantje]

I get quite some time out notifications like:
2020-05-19 13:11:46.908 Status: OpenZWave: Received timeout notification from HomeID: 3833672857, NodeID: 46 (0x2e)
However, if I check the node: it is seen seconds ago. All associated devices are also refreshed every few seconds (it is a power plug with polling enabled).
The HomeID is something I do not recognize! If I check the OpenZWave control panel, I see HomeID: e4813499
Is this why I get time out messages of devices that are not timing out whatsoever?

Each and every time out has this HomeID.

[Egregius]

e4813499 is the hexadecimal value of 3833672857

What is node 46?

[Plantje]

Nice one, thanks!
Node 46 is a power plug.

I have also updated the following parameter:
5. RetryTimeout:
100000
(ms) (huidig: 100000)

How long do we wait to timeout messages sent (default 10000)

Perhaps that helps.

[Plantje]

Nice one, thanks!
Node 46 is a power plug.

I have also updated the following parameter:
5. RetryTimeout:
100000
(ms) (huidig: 100000)

How long do we wait to timeout messages sent (default 10000)

Perhaps that helps. Nope.... as it seems there are still quite some time outs

[Egregius]

Try disabling polling. Why do you have it enabled?

[Plantje]

Will do. I have it enabled, because I thought that is needed to get the updates of power consumption etc.

[Egregius]

Depends on the model. I only have polling enabled for one Qubino that doesn’t send the temperature.

[Plantje]

Hmmm... ok, I have reset the parameter on the controller as it didn't seem to help. I have now disabled polling on all of these devices.

[Plantje]

Instantly had some time outs from non polling battery devices. But let's wait and see for a while

[Plantje]

Well, that helps a lot! Now, I have to filter for the word timeout. I see one of my Fibaro carbon monoxide detector and one from one of my 11 Fibaro smoke detectors. Then there are also 4 notifications from a Danfoss radiator thermostat:
2020-05-20 00:10:38.709 Status: OpenZWave: Received timeout notification from HomeID: 3833672857, NodeID: 57 (0x39)
2020-05-20 02:08:33.254 Status: OpenZWave: Received timeout notification from HomeID: 3833672857, NodeID: 57 (0x39)
2020-05-20 03:22:16.167 Status: OpenZWave: Received timeout notification from HomeID: 3833672857, NodeID: 57 (0x39)
2020-05-20 03:22:18.168 Status: OpenZWave: Received timeout notification from HomeID: 3833672857, NodeID: 57 (0x39)
Two are very close to one another.

However, of the two 6 node power strips from Greenwave (that were also giving incidental time outs) I see that the reports on power usage stopped about 10 hours ago. That was why I had polling enabled in the first place.
If I look at the current values, I do see those values and they get updated regularly. But I do not see it in the logging.
I have now set the following parameter from 10 to 1:
"0. Power delta: 1 (%) (huidig: 1) Consumer variation required to send notification. From 1 to 100, default 10"
Let's have some patience again and wait and see, but so far it doesn't seem to be logging.

[Plantje]

Hmmm.... and while writing the previous response:
2020-05-20 07:53:47.047 Status: OpenZWave: Received timeout notification from HomeID: 3833672857, NodeID: 82 (0x52)
2020-05-20 08:30:56.629 Status: OpenZWave: Received timeout notification from HomeID: 3833672857, NodeID: 100 (0x64)
2020-05-20 08:31:06.632 Status: OpenZWave: Received timeout notification from HomeID: 3833672857, NodeID: 100 (0x64)
2020-05-20 08:31:17.411 Status: OpenZWave: Received timeout notification from HomeID: 3833672857, NodeID: 93 (0x5d)
2020-05-20 08:31:27.427 Status: OpenZWave: Received timeout notification from HomeID: 3833672857, NodeID: 93 (0x5d)
2020-05-20 08:31:37.872 Status: OpenZWave: Received timeout notification from HomeID: 3833672857, NodeID: 45 (0x2d)
2020-05-20 08:31:47.879 Status: OpenZWave: Received timeout notification from HomeID: 3833672857, NodeID: 45 (0x2d)
2020-05-20 08:32:05.410 Status: OpenZWave: Received timeout notification from HomeID: 3833672857, NodeID: 29 (0x1d)
2020-05-20 08:32:15.440 Status: OpenZWave: Received timeout notification from HomeID: 3833672857, NodeID: 29 (0x1d)
2020-05-20 08:32:27.869 Status: OpenZWave: Received timeout notification from HomeID: 3833672857, NodeID: 2 (0x02)
2020-05-20 08:32:37.886 Status: OpenZWave: Received timeout notification from HomeID: 3833672857, NodeID: 2 (0x02)

And these all (but one) happen to be the nodes of which I disabled polling and set the power delta parameter to 1%

[Plantje]

Did a reboot of the Domoticz server this morning.
The current usage of all outlets of the two 6 node power strips were logged and that value was next logged every 5 minutes. The devices recorded as not seen after that.
I switched on polling again on those two power strips and the logging immediately started working agin. Unfortunately the time outs also started coming in immediately.

For the single power nodes switching of polling does seem to work better.

[Egregius]

Conclusion: only enable polling if it’s needed. And set the polling time high enough.

[Plantje]

Yes, I have set the polling interval to 60 seconds now. Perhaps that helps. And I can also always still play with the parameter for the timeout:
5. RetryTimeout:
10000
(ms) (huidig: 10000)

How long do we wait to timeout messages sent (default 10000)

[Egregius]

My timeout is set to 5000 msec and I just ignore them because everything’s working as expected.

[Plantje]

The retry timeout is set to 5000msec?
I had the impression that there was this many error logging that it flooded my Domoticz server to an extend where I had to reboot on an almost daily basis. Now, I have fixed a lot of the error messages and I thought I might as well take a look at the warning level time outs. Perhaps I should not bother that much

[Egregius]

If everything's working, why bother? I only look at the logfiles if something went wrong, so almost never.

[Plantje]

Well, yes, I agree. And as a matter of fact: it is not always running flawless. For example: the past week I had several days where I had to restart the machine in the morning in order to be able to switch specific smart outlets.
So, something is wrong to some extent. That's why I started looking in the logging in the first place. First try to minimize the number of errors and then I started getting interested in the time outs as well. Why is the server expecting something in the first place?

Another reason for looking at this is that at times some of my Fibaro smoke detectors give a beep to indicate that there was no communication. Perhaps I can fix that this way as well.