What are you seeing in the debug logs? What version of the binding are you using?
I’m surprised that you need a rule - are you saying that the binding is not polling then even if you set the poll rate higher? That may indicate that the device has not initialised properly, but I’m really just speculating without seeing the log.
I’m using binding version: 126.96.36.199001070048 (because of my ABUS Smart Switch which you recently added to the DB, thanks fot that again).
I currently try to find out how to activate the debug log for zwave, searching for the docs.
Is it a good thing to always let these logs enabled or does it takes to much disk space over the time ?
(Only have an RPi with an 16GB SD Card)
It gives me a value al 10 Minutes like configured in the binding polling period (which is the smallest interval I can configure here)
I also facing strange behavior when switching via openhab:
Light ist switch on (manually by the wall switch)
Watt show 16.5 w (which is ok)
Switching off Light from openhab, light goes off, but watt remains at 16.5
Swtiching on light from openhab, light goes on, but watt goes from 16.5 to 0
What do you need to see from the logs, changing parameters, or just switching the lights from OH and manually ?
It is described toward the bottom of the ZWave binding doc.
The smallest inteval should be 10 or 15 seconds if you want to set it that low (but this is not recommended and the device should send reports rather than set the polling so fast).
In the first instance, let’s just see if it is sending anything. If it’s not, then maybe the associations are not set, or the device is incorrectly configured. If it is, maybe the binding is just not decoding it correctly.
I thought the problem was updates from the device? ie if you change the device state, then OH doesn’t update? If so, can you provide a log that shows what happens (if anything) when you change the state of the switch - but don’t do anything in OH.
The problem with this log though is there are so many commands being sent that I can’t see what is coming from the meter due to polling, and what is coming unsolicited. The log is 40 seconds long, and in that time you’re sending 10 commands to the switch so the log is just full of events.
I would very strongly recommend not to configure any device to report as fast as every 5 seconds. This might be ok if you only have one or two devices, but it will not scale and for sure you will have big problems in future (but for now at least it’s ok for testing).
Anyway, please can you provide a log showing what is received from the device when you don’t do anything in OH. If there really is nothing, then it’s clearly a configuration issue with the device rather than a bug in the binding.
Will do that, but need a way to upload it to a cloud storage as the log will grow above 1024K which I can upload here. There are multiple other devices that report.
What would you recommend as report intervall from such switches (metering data) or power outlet plugs ?
Most devices will allow you to set two parameters for reporting - a period, and a “level”. So it will only report if either the period, or the level are exceeded. I would then set the period reasonably high (eg every few minutes, but the level low - low here will depend on the size of the load.
So, you might set the period to 5 minutes, but the level to 2 watts - if nothing changes because the light is on or off, then the meter checks in every 5 minutes. But as soon as you turn the device on or off, it will change by more than 2 watts, and you instantly get an update.
If the device just has time, then you should have a think about how many devices you have - if you start to overload the controller (and ZWave controllers at the moment do not have fast processors inside) then you will start to see errors showing up in the log. If you only have 5 or 10 devices, maybe 10 seconds is ok (depending on how many reports they send) - if you have 100 devices, then it will be a different story…
So the device is sending notifications to the lifeline (or at least, to one of the association groups). This is resulting in the channel being updated, and therefore should result in the UI being updated.
However, as you have said, there are no meter requests. Given there really is nothing in the log, I think this must be a configuration issue with the device.
What have you configured for parameter 91? According to the manual, this is set to 25W and it will not send an update if there is not a change of this size and I think I saw earlier that the meter readings were about 16W. I would have still expected the device to send readings if you set the duration to a shorter time, but maybe it doesn’t work this way in this device?
One more thing I’d like to check before I’m out of ideas…
Can you do a complete reinitialisation of the device. In the parameters there is an option called something like “Reinitialise device” - select this and save. It will take a minute or so probably, then send me the log so I can see how things are configured.
Ok, did that, here is the log, but nothing changed from what I can see.
Beside that it not sends metering reports on its own by the defined interval, from the logs I can see for example Switch 1 was on and Watt=16, I turn switch 2 on and it reports watt again at 16w and also that Switch 1 is still ok.
I turn switch 2 off and it reports watt=33 which is a report of watt because Switch 2 was an before and so the 2nd lamp.
So what I tought was, when I turn switch 2 on it send me the new report with 33 watt when both lamps are on, but it is that fast that I get the report of what was “shortly” before or some milliseconds after switching.
This makes sende to me now.
But still it sends no report of its own at the defined interval.