Ok but what does the Group 1 Reports value show? This is the important one.
When I query group 1 reports, it shows 0, however this is exactly like the interval setting in that I have tried multiple times to assign a different number to it, but it just doesnât seem to take.
Group 1 Reports needs to be a non-zero number in order to report readings.
The setting you need to set this to you get from this table:
They have an excel sheet setup to help you as well at that link, once you set this up youâll get your readings.
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)
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
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?
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.
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.
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:
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.
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.
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.
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.
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:
- I have polling set up wrong
- Thereâs a bug in the current version of home assistant that doesnât allow polling.
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.
Now home assistant could be reading that incorrectly.
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?
Youâd need to report it on github for home assistant. Same for openzwave if its on github, Iâm pretty sure it is.
On 67.1 this was fixed it seems. Polling now works correctly; again.
1 Like
Does this fix correct the issue with polling_intensity when read from configuration.yaml?
Yes it does in my installation.
1 Like