Author
Topic: Z-Wave capabilities List (Read 3125 times)

Copied from micasa verde wiki. I was hoping a lmce/zwave pro could take a look and verify these are the same numbers that web-admin displays? I am troubleshooting a problem getting energy usage from a module and wanted to make sure it was configured properly.

On a ZWave's properties you'll find 2 values to show what the device can do:

The first 6 numbers in capabilities are what is reported by the ZWave ZW_GetNodeProtocolInfo function (0x41): Capability, Security, Reserved, Basic Device Class (, Generic Device Class, Specific Device Class. If the Capability is >= 128 then the device listens for commands, otherwise it's a battery operated device that only wakes up occasionally.

The version is what's reported by the COMMAND_CLASS_VERSION command VERSION_REPORT. There are 5 values: Z-Wave Library Type, Z-Wave Protocol Version, Z-Wave Protocol Sub Version, Application Version, Application Sub Version. The Application version is specific to the device and not defined by Z-Wave.

I'm not exactly sure what you're trying to tell us with the post... It would really help if you could state what exact device you're using, how it is configured (config params), what you would expect it to do and how it is behaving differently from that.

I have an Aeon Labs Smart Energy switch. When I select Web-Admin>Automation>Show Energy Usage I get an error saying it cannot find the database.

To troubleshoot this I first went on the assumption that the switch was not detected as a energy meter so the database wasn't installed. To test this theory I needed to know the above codes were. Using that I looked up the codes showing in device data for this switch. If none of the numbers in device data list equated to energy meter I would be correct.

The above number meanings tell me that the switch is detected as both a switch and an energy meter but ONLY if that list is the same as the one LMCE uses for its device data. I wanted to move on in troubleshooting so posted the above to confirm.

My next step will be to try and figure out where Web-Admin>Automation>Show Energy Usage points to. If it is a pathname I can follow it until I see other db directories. This would test another assumption that the link is wrong and energy usage db does exist.

If both of the above options are checked out then my troubleshooting ability is expended and I would then ask for help with sqlCVS lookups. Device Tree>Dcerouter>show entire log, shows that the device is changing usage info about 15 times a minute but is not clear if this is being logged anywhere. How a switch in the off position is changing usage is another mystery I will need to figure out.

I think that stuff (not added by me) just tracks on/off events and then cumulates the configured Watt setting of any device. But we also support true energy meter reading with the AEON Labs HEM. Adding this unit will deliver values to the data logger. For your device there is some code missing. It needs to be queried. You can send me a unit (working on EU frequencies) for my demo lab if you want it supported.

1.Enter my best guess for watt usage on that switch into device data.2.Buy a HEM.3.Buy you a European unit.4.(Add the code myself)

1? DCE router log shows energy usage changes when the switch state hasn't changed. Adding a guess into wattage in device data would guess my watt usage based on time in the 'on' position I assume? This would give me historical guess data but don't think it would resolve the constant unhandled socket communications.

2? Are you saying that by adding a HEM, my system will then be able to write data from my switch to the log, or that it would right data from the HEM to a log? If the former is correct could I just add a faux HEM to my device tree so that data logging would activate?

3? I would if I could. Alternatively, could I send you my US AEON Labs USB stick, my US AEON Labs smart energy switch and my US inclusion controller and return postage? I would be without z-wave a while until you found time for it but I survived 30+ years of reaching for a light switch, I'm sure I can manage.

4? Since the device is reporting changes that dcerouter is able to understand (mostly) then I may be able to add code to get this data to the logger. Perhaps a plugin that gets energy usage changes from dcerouter and throws them into a txt file? Alternatively, do you know of a way I can tell a z-wave device to stop reporting and just act like an on/off switch. Given other option $/time costs, I don't need energy monitoring and would be happy with on/off and a clean log.

re 2), the HEM data will be logged by the data logger plugin. That would be completely separate from the switch.

shipping back and forth for 3) would probably be more expensive than the unit itself..

I did look at the code and I do request multilevel sensor data on polling, but I send it to the broadcast address. Maybe the unit does not honor that.. Would you be available for a debug session in IRC? But I will need ssh access to your core, that would speed up things.

I usually get on fairly late in (my time) -5 GMT. I will catch up with you but it means moving some things around to devote time in the morning.

The more I think about it the more I have to laugh at the shipping back and forth to you would probably cost more than the device. However, tv aside this is the most expensive device in my linuxmce setup. Typically my limit on buying new hardware is around $20. I really should grab old receipts and see if I can ballpark a total build cost. Willing to bet it's way below $300 (tv excluded).