I would also suggest posting a Device diagnostic of this device so we can confirm the configuration is as expected. It’s much easier to parse then written words or screenshots.
Thanks to both of you. Yes, I agree that those must be the HA equivalents to the ST settings.
This is puzzling to me. Is there some way to switch it between ST and HA without exclusion/inclusion?
I had turned on debug logging on the config/integrations/integration/zwave_js page. Where do I find that log?
Here is the device log:
Device log:
Hah, you’re right. Brain fart. Excluding the device and re-including it is therefore resetting the parameters.
This is the device diagnostic. You posted a Z-Wave JS log at Difference in tilt sensor performance between ST and HA - #3 by Jz777.
Based on the diagnostic:
- Automatic Report: Group 1 - kWh (Whole HEM) is currently disabled, but you enabled this in smart things
- Automatic Report: Group 1 - Power (Clamp 1) is enabled, but disabled in ST
- Automatic Report: Group 1 - Power (Clamp 2) is enabled, but disabled in ST
- Report Interval (Group 1) is still set to the default 720
Did you set these yet before uploading the diagnostic? If so, either you had a fat finger or the value wasn’t set correctly by HA or ZJS. Would need a log to confirm that.
BTW, the Aeotec engineering doc says that when the device is on battery power (which yours is) it will only send timed intervals in multiples of 4 minutes, so the 60 second setting is supposed to result in 4 min reports. This is also in the ZJS DB parameter descriptions (“Rounded up to the nearest 4 minutes when battery powered”).
EDIT: Hmm, looking through diagnostic some more, your device is on USB power, is that right? Then none of the battery wake up stuff matters.
Correct, it’s shows as USB but it’s actually powered by a 5v wall wart. No batteries installed.
Right, but I’m not sure how to get that again. I had turned debugging logging on at the start of today’s trial. From where do I download it?
This may all be clearer from the log, but in case it isn’t I had already written it. Maybe it will be useful for someone else.
When I added the meter to HA, and went into its configuration, the switch was off:
Sensors had readings, but did not change through this entire saga:
I went into “entities not shown,” and found:
Which appears to correspond to the parameter I show in the config page above. I enabled it, as well as the other three Automatic Report entities for power: Group 1, Group 2, Group 3, and Whole HEM). I think that 1 and 2 refer to the two sensors I have. If I have whole or 1+2, that would be good.
Each responded with, “The enabled entities will be added to Home Assistant in 30 seconds,” but all still showed as disabled after several minutes. Reloading the page did not change them:
The sensor values remained unchanged from the initial inclusion.
Next, I tried to enable all 4 using the popup menus. Group 3 could not be enabled, which makes perfect sense as I only have 2 sensors. I waited a couple of minutes and reloaded the page. No change.
I went into Configure under Device info, and the switches were on, corresponding with the changes I made:
Finally, I went to my dashboard. Choosing any of the three entities only put “Enable” in place of the power reading.
How does this 5v wall wart work? The device thinks it’s on battery.
No, it’s not the same. The one you changed in ST is Whole HEM. This one is Clamp 1.
Each responded with, “The enabled entities will be added to Home Assistant in 30 seconds,” but all still showed as disabled after several minutes. Reloading the page did not change them:
That is referring to enabling the entities, it doesn’t have anything to do with what their values are. You don’t need the entities unless you are automating them. After you enable the entities you would still need to change the value.
Got me! It just connects to the third of the three ports. The bigger mystery is how I would connect it to a PC to update, but according to Aeotec, there’s no reason for it in my application.
You plug the HEM’s USB port into a USB port on a Windows PC and run their update program. But their firmware page doesn’t even have a changelog, so who knows what’s changed?
If you want the device to behave like a powered device, I think you need to include it on USB power. Right now it’s acting like a battery device and doesn’t listen for config changes until woken up. Or I could be mistaken and it’s always a non-listening device but wakes up every 1 second, which would be weird and would certainly bring a Z-Wave network to its knees (would need log to see it).
Sorry, that was unclear. I switched both on in HA, as you can see from the later screenshot.
Those changes remain, but sensor readings remain the same as they were when first added.
Yes, but there is no USB port on the outside or under the snap-off cover. Maybe there is if I remove the inner cover, but I don’t need to update.
It reports every 60 seconds on ST. It shows as USB powered (read-only) in HA:
Does it show as something different elsewhere?
Sorry for my slowness here.
So do you want the JSON file resulting from the Download diagnostics button? It looks like a config file, not a log file.
Or do you want the home-assistant.log file?
Is it worth putting in batteries and turning on Parameter 12 above?
Are you referring to this one?
These are not the same settings as you had in ST.
ST:
This screenshot:
I mean, I guess I’d still expect power entities to update, but you don’t have any energy reporting enabled (kWh) so those won’t change.
Are you trying to measure, power, energy, both?
Yes, but there is no USB port on the outside or under the snap-off cover. Maybe there is if I remove the inner cover, but I don’t need to update.
I guess Aeotec would have to answer to that, I was just going by the manual. The device does not report OTA firmware update support, so it can’t be done through ZJS.
It reports every 60 seconds on ST. It shows as USB powered (read-only) in HA:
Apparently the device realizes it’s on “USB” power, but I’m not sure Z-Wave JS agrees because it reports:
"isListening": false,
Still, somehow you were able to change the settings anyways, so I’m not sure if this matters then.
I’m asking for the driver log file. Difference in tilt sensor performance between ST and HA - #2 by freshcoast
Yes. I was trying to cast a wide net, as Groups 1 and 2 appear to correspond to the legs in the panel.
I’m fine with power only. Turning on all of those for Group 1 didn’t change anything that I could see.
Still, it’s progressed from requiring a button press for listening to taking changes without one.
I’m trying to comply. From that page:
Set the log level for
zwave_js_servertodebug. This can either be done in yourconfiguration.yamlin theloggersection, or using thelogger.set_levelaction. When the integration detects that the log level has been set todebug, it will also set the Z-Wave JS logs todebugif the level isn’t alreadyverbose,debug, orsillyand will include those logs in the Home Assistant logs. The Z-Wave JS logs can be found under the logger namezwave_js_server.server.
Apologies, but I don’t understand that last sentence. I see 435 entries with “zwave_js_server” in home-assistant.log, which drove my question. Is “logger name” a heading in that file, or does it refer to a separate log file, possibly in a different directory?
Or should I turn on the logging window, then exclude and include again?
Those are the logs from HA (#1). Logger name is the component name that is logged.
Except you posted an actual driver log from a different file in Difference in tilt sensor performance between ST and HA - #3 by Jz777, unfortunately I can’t tell you how you did it, only provide the methods to get them. I suspect you are using ZUI and opened the driver log file (option 2), but I don’t recall you providing which addon you are using. So maybe look there if so, easier than HA logs.
No, not UI.
I could do it again to get more specific ones from the window at /config/zwave_js/logs, but in the meantime I’ll just post the whole home-assistant.log in parts. Let me know which is easier for you.