Z-wave stat value changed but very slow response in RULE?

[Bruce_Osborne]

@Simon_Thorsted

The power meter :

Here we need brand and model numbers, not images. All I can tell is the brand is Fibaro.

[rossko57]

What are the capabilities of your mystery zwave device? openHAB can’t make it do things that it cannot do.

Perhaps you need to look into polling it a short time after issuing a command to it.

[Simon_Thorsted]

IT`S a : Z-Wave NAS-WR01ZE Wall Plug Switch NEO Coolcam.

I can see that the time can be set to less secounds but not how ?
openhab minimum 30sec. ?

[rossko57]

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.

[Simon_Thorsted]

i don`t know how to do that ? sorry i dident responded to that before

[rossko57]

Clue

Item state not correctly updating after ItemCommand 'ON'

It’s a configuration option on each thing - not the binding. That’s fine - it’s not outdated, but it’s certainly quite old now, and doesn’t contain any new features for well over a year (likely a lot more). I don’t think what you report in the first message is a binding issue. The binding should send the command (which I guess it does) and the system should update the item state. That said, as @5iver points out, the repoll feature will likely also solve this by refreshing the data shortly a…

[Bruce_Osborne]

@Simon_Thorsted

IT`S a : Z-Wave NAS-WR01ZE Wall Plug Switch NEO Coolcam.

I can see that the time can be set to less secounds but not how ?
openhab minimum 30sec. ?

1. That does not agree with your original photo.
2. 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.

[Simon_Thorsted]

[Simon_Thorsted]

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.

[Bruce_Osborne]

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?

[Simon_Thorsted]

How to do the polling , can you show me please i`m not a coder at all

[rossko57]

@Simon_Thorsted

How to do the polling , can you show me please i`m not a coder

@rossko57

It’s a configuration option on each thing

That’s as much as I know

[Bruce_Osborne]

@Simon_Thorsted

How to do the polling ,

@rossko57

It’s a configuration option on each thing

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.

[Simon_Thorsted]

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 )

[rossko57]

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.

[Simon_Thorsted]

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 ??

[Simon_Thorsted]

ok I put in a 3sec. “Interval” whit habadmin ind one of the newer power plugs
så now it`s working ok 3 sec. i can wait for my extra screen and some lights
to come on agin after computer standby.
It does fill a lot in the log but what to do ?

so now i can move on to do some realy nice things whit this knowledge ,this was realy
just a little test to make it work on some think closeby.

Thanks agin.

[rossko57]

@Simon_Thorsted

It does fill a lot in the log but what to do ?

You could maybe not do that, and try the Command Poll Period setting instead. It’s something different.

[Simon_Thorsted]

Can you show how ?

[rossko57]

Like any other Thing you set up in PaperUI, you look to see the available options in PaperUI. If there’s an “advanced options” button or suchlike, you might click that.