Hello.
I`m having some problem whit a z-wave power meter ( NEO Coolcam. NAS-WR01ZE Wall Plug Switch )
It all works fine BUT VERY VERY SLOW 30sec. - 1min…
If i push the switch i sitemap the z-wave response instantly.
On state change in logs i see in the logs the value changes fine ,but openhab waits too responce ???
Does anybody know how to speed this up so it can be used to something meaning full ?
Sitemap :
Switch item=sonoff_5
Text item=zwave_kontor_watt label=" kontor autuelt forbrug [%.1f W]"
More helpful would be to follow the zwave documentation instructions for when things do not go as planned and post some debug logs.
The log viewer is here if you wish to look too.
I think it’s generally recommended to use Habmin to alter settings in zwave devices.
Careful though, do you really want to clag up your zwave network with metering reports every second?
I’ve being trying to prod you to think about the binding’s channel setting for poll after command. If the meter value is returned in a response to that, you might need to alter the time delay. Too quick will give you an old value before the command has taken effect.
You are depending on the Coolcam document with the unit. I have received their devices where the supplied documentation did not match the actual device.
I have some of those plugs, in the US version but do not use the metering. We have 2 entries for that model, depending on the device type & id numbers.One of the entries indeed has a 30 second minimum for meter reporting. These cheap Chinese devices are cheap for a reason
In HABmin, go to Configuration → Things → [device] → Attributes (all the way at the bottom) and post a screenshot. It will look something like this.
I have a lot of this and now i see that i have 2 kinds the one im doing this with i an old one and others i have are a newer and they can be set to report every 1 sec. thanks ,but i will try to look at that pull thing so my logs dont get useless to look at.
ps : i have changed the picture in orginal post , i just thourght it look like that sorry.
I do not know what firmware version our entry was based on but our entry and the attached manual clearly state a 30 second minimum for report in parameter 7. It was last updated 2 months ago. (from our pdf manual)
Your manual says parameter 2 and a 0 minimum. If we make an entry for newer firmware we would need a pdf of an updated manual. Can you find one online?
I think that is the reporting configuration that is currently limited to 30 seconds minimum in your case based on the manufacturer’s documentation we currently have.
ok thanks a lot for the help ,i gues i will be Using my tuya wifi power plug then i can do the trick via. convert to tasmota and then whit mqtt
this works but is on wifi so my 18ps. z-wave plugs i must use for something
were i can wait for 1 min. befor resolut ( turn lights off auto when no movement i some time )
Nope. “poll after Command” is a function of the binding, not the device. Shortly after a command is sent, a one-time status poll can be sent. “Shortly” is under the control of the zwave binding and is a Thing setting - I think it is named Command Poll Period in PaperUI and is expressed in milliseconds.
If this happens too quickly, you’ll get the old state from the device.
So, you could try extending the time, to see if that gives the device time to update its own sensing.
It might not help if the device only measures its own current sensors every five minutes or something.
It might not help if the device does not include the power measurement in its status response.
as i startet the hold thing to tell about the thing that i was woundring about is that the
value changes in my paperui (control )
but afterwoods wait 30sec. to 1min. to do something after it has changed ???
i belive that openhab then knows the value ,but somthing prevetts it to do something
maby it tryes to comfirm or something ??