Justin Hammond

I need to test that with Quibino Devices, which the original fix broke your fibaro devices. both of which, IMHO are not compliant with the specifications. *sigh*

thanks. I'll look into this eventually.

Regarding Aftermark - Only a few CommandClasses support it. You would need to update the COMMAND_CLASS_SWITCH_MULTILEVEL to also property support Aftermark: 1) Only expose ValueID's that are appropriate for reporting...

In Progress on the Dev Branch: https://github.com/OpenZWave/open-zwave/blob/Dev/cpp/src/ValueIDIndexes.h I should be able to merge this to master after this weekend.

Sorry - I know nutz about the Python interpreter and it’s internals. One of the original authors of the python wrapper has just reappeared and said he will have a...

I think we should keep the discussions here on github. There are a few people that have indicated they want to help out. Ultimately @bibi21000 has the final say on...

With "regards" to transfering the ENUM's over... you may not need to. (I'm not sure about how python handles enums though). All that fancy pre-processor magic turns each ENUM block...

Essentially - OZW just reports whatever the devices send. We don't "massage" values etc. In this case, I've seen devices occasionally send weird values. As you note - The CRC...

Seems like a reasonable fix. Could you post a patch/pull request?

@RicardP wow. This is the type of attitude that demotivates me from doing anything on this project. Banned...