Z-Wave Polling Questions Answered

Configuration
45

I’m well aware of that, unfortunately I have found no way to make any change to that value. Every time I set it, then query it again, it still shows as zero.

So if I can’t set that, the obvious workaround is to get home assistant to poll the device, as that obviously works or it wouldn’t update on home-assistant restart. Unfortunately polling doesn’t seem to work on home assistant without a restart, so I’m somewhat stuck.

EDIT:
2018-04-18 16:05:22.098 Info, Node021, Value::Set - COMMAND_CLASS_CONFIGURATION - Group 1
Reports - 101 - 1 - 768
2018-04-18 16:05:22.099 Info, Node021, Configuration::Set - Parameter=101, Value=768 Size=4
2018-04-18 16:05:22.099 Detail,
2018-04-18 16:05:22.099 Detail, Node021, Queuing (WakeUp) ConfigurationCmd_Set (Node=21): 0x01, 0x0f,
0x00, 0x13, 0x15, 0x08, 0x70, 0x04, 0x65, 0x04, 0x00, 0x00, 0x03, 0x00, 0x25, 0xe2, 0x2f
2018-04-18 16:05:22.099 Detail,
2018-04-18 16:05:22.099 Detail, Node021, Queuing (WakeUp) ConfigurationCmd_Get (Node=21): 0x01,
0x0a, 0x00, 0x13, 0x15, 0x03, 0x70, 0x05, 0x65, 0x25, 0xe3, 0x26
2018-04-18 16:07:53.913 Detail, Node021, AdvanceQueries queryPending=0 queryRetries=0
queryStage=ProtocolInfo live=1
2018-04-18 16:07:53.913 Detail, Node021, QueryStage_Probe
2018-04-18 16:07:53.914 Info, Node021, NoOperation::Set - Routing=true
2018-04-18 16:07:53.914 Detail,
2018-04-18 16:07:53.914 Detail, Node021, Queuing (WakeUp) NoOperation_Set (Node=21): 0x01, 0x09,
0x00, 0x13, 0x15, 0x02, 0x00, 0x00, 0x25, 0xe4, 0x33
2018-04-18 16:07:53.914 Info,
2018-04-18 16:07:53.914 Detail, Node021, Queuing (WakeUp) Query Stage Complete (Probe)

46

Your device is sleeping, you have to wake it up before issuing the configuration command. Tap the action button then issue the update to the reports configuration. That should fix you up.

1 Like
47

I will try that, however it doesn’t make any sense. If the device is sleeping, how can it respond to the polling request sent by home assistant when it restarts?

48

Sleeping devices report in every so often, while the zwave stack/stick is initializing it tells the network it’s doing so thus causing all nodes to report their current values then resume whatever they were doing ie: sleeping, routing, etc. That is why you get an initial value when you restart HASS.

49

Then why can’t I poll these devices to get a response any time other than on a restart?

That’s the crux of the issue in this “polling” thread. Polling works properly on restart, but never again. That strikes me as a polling problem.

50

Are you sure there isn’t another setting you are missing? Like a threshold? Many of these energy meter devices only report a change when it sees one or it goes above a threshold.

So if the device reports whenever it see’s a change, you need to figure out the devices resolution. If the energy change is less than the resolution of the device, it won’t report anything.

Just looking at the devices manual:

https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/6009584508/original/27%20Home%20Energy%20Meter%20G2.pdf?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJ2JSYZ7O3I4JO6DA%2F20180419%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20180419T160921Z&X-Amz-Expires=300&X-Amz-Signature=7c6c9c54ac496e742d4c91e74c9381bfb2a3ae23fdb025928635759280845852&X-Amz-SignedHeaders=Host&response-content-type=application%2Fpdf

It appears as if there is a threshold parameter. Make sure that is set properly.

You will need to wake the device to change that property.

51

Every solution you propose is related to settings on the energy meter itself. And while I agree that’s the ideal solution, it’s also completely unrelated to this thread.

The question is, when I have a device that obviously responds properly when polled, why can’t I get home assistant to actually poll that device other than during a restart?

To be clear, thank you very much for the proposed solutions related to the energy meter itself, and I will be trying all of those. But I’m curious as to the other side of it all as well.

52

It even has parameters that only make it change if its above a percentage from its last value. Looks like this is a complicated device. I would look into those properties and compare them to the wattage that your washer/dryer are using.

53

I understand your frustration, but this is how ZWAVE works, not home assistant. This may be a nuance of OZW, which is the api that home assistant uses. Currently, that api is outdated by ~2 years and i believe we are waiting on them to make a new version.

54

If it wasn’t related to home assistant, then a home-assistant restart wouldn’t affect it.

The fact that restarting home assistant causes the value to refresh proves that there’s something home assistant does that can get that value. So how do we make home assistant do “that thing” without restarting?

My understanding is that the polling command is explicitly for this purpose, and it feels to me like it’s simply not working. So that leads me to believe that one of two things is happening:

  1. I have polling set up wrong
  2. There’s a bug in the current version of home assistant that doesn’t allow polling.
55

This is openzwave though… not home assistant. You are literally pulling that error from the ozwave log, which is created by openzwave. Openzwave is not managed from the creators of home assistant.

56

Now home assistant could be reading that incorrectly.

57

Ok, the bug could be in OZW I suppose, but either way, can we at least admit that polling is supposed to be an option, and if I’ve configured it wrong, see where, and if it’s a bug, see who to report it to?

58

You’d need to report it on github for home assistant. Same for openzwave if its on github, I’m pretty sure it is.

59

On 67.1 this was fixed it seems. Polling now works correctly; again.

1 Like
60

Does this fix correct the issue with polling_intensity when read from configuration.yaml?

61

Yes it does in my installation.

1 Like
62

I’m on 67.1 and just added a GE Dimmer and the polling doesn’t seem to be read from the config yaml. Tried calling polling intensity as well to no avail. Did you get it to work?

63

I did not. I can say that it’s just the interface. There is something odd in general with z-wave and GE dimmers. I have not found a solution, I’m just ignoring it for now because I barely use the interface. All on/off commands work correctly.

64

Thanks, very helpful for understanding how the Aeotec MultiSensor6 works.