Command Class Basic (Unhandled) about open-zwave HOT 7 CLOSED

An update on this issue.
The 0x20 command class must not be added to the value store (supported classes) 
as 
it serves a different purpose. 
I will discuess the details in the groups post
http://groups.google.com/group/openzwave/browse_thread/thread/1beebdd992f9c72a

Added fixes, should be now working

I can't tell in the SVN log...what fixes are supposed to have affected this?

The fixes were commented out shortly after - I can't remember why.

The code is turned off inside the #ifdef notdef block in
Driver::HandleApplicationCommandHandlerRequest

We ahve to decide how devices notify us of changes in state, plue which ones 
are value changes and which are events.

So, as I understand it, these devices bastardize some standard commands to 
report that their status has changed. Is there no way to generalize the 
behavior besides looking up in OZW which device works which way? Is there a 
main discussion going on somewhere about how devices notify us?

It can be generalized on a command class basis - I just need to find time to 
work through the different reporting mechanisms.

Excellent, I can verify that the error message is gone as of r127.