Getting `Unhandled notification: 4` and `unsupported value type: 0x2` in the log about node-openzwave HOT 13 OPEN

Ok, the 0x2 message should be gone in 0.0.30 now. The group notification will take a bit longer, need to do some reading up on zwave groups and how we should handle them.

from node-openzwave.

Thank you Jonathan - in the process of installing 0.0.29 when I saw this :D (it takes time on a raspberryPi)

Thank you again for addressing these issues - greatly appreciated.

from node-openzwave.

I started working on a sensor and getting a new one:

Unhandled notification: 10

Hope this information helps when you address these issues.

from node-openzwave.

@jperkin - could you help @zonak on this?

many thanks!

from node-openzwave.

@zonak Let me guess, it's a fibaro window/door sensor.

I'm at this problem currently, too. My guess is, that the sensor will notify it's association groups about an value change, which should trigger a fetch of the new values as long as the sensor is not going to sleep.
But maybe I'm completely wrong.

from node-openzwave.

@zonak I'm seeing the same Unhandled notification: 10 error you saw by in later October.
This is coming from Vision Wireless Door/Window Sensor (model # ZD 2102 US).

Did you have any success in resolving your issue?

Thanks!

from node-openzwave.

No luck yet.

from node-openzwave.

Sorry to hear you have not solved it but glad to hear I'm not alone. I'll have this on on the back burner until I can git it resolved and I'll submit a push request if I beat you to it.

from node-openzwave.

@zonak
I have found the root cause of this issue and implemented a temporary fix on my side. I will try to submit a pull request in the coming days

from node-openzwave.

groovy! many thanks!

from node-openzwave.

I may not get a push request soon so I thought I'd pass this on....

If you look in this file https://github.com/jperkin/node-openzwave/blob/master/src/openzwave.cc on line 128 the event is acquired from the openzwave library and thrown up in the queue for node side.

case OpenZWave::Notification::Type_NodeEvent:
notif->event = cb->GetEvent();
break;

This is event type 10 which was my issue.

This notification is the pulled off the queue here, line 155. You'll see there is no corresponding switch statement to pick up Type_NodeEvent.

ie, notif->type == Type_NodeEvent (10).

For this notification type, I added this switch statement

            /*
             * A node has triggered an event.
             */
            case OpenZWave::Notification::Type_NodeEvent:

              args[0] = String::New("event");
              args[1] = Integer::New(notif->nodeid);
              args[2] = Integer::New(notif->event);
              MakeCallback(context_obj, "emit", 3, args);
              break;

which allows me to move forward with my development.

This may not solve your issue but it may help you move the ball forward.

Thanks,
--Walt

On Aug 21, 2014, at 4:01 PM, Marshall T. Rose [email protected] wrote:

groovy! many thanks!

—
Reply to this email directly or view it on GitHub.

from node-openzwave.

Thank you for the update. I came to the same conclusion about the 10-s and the 4-s but wasn't feeling confident to go forward with a PR given my lack of experience with C++.

Hopefully @jperkin will spare some time on it again.

from node-openzwave.

The 4 should be working as there is a switch statement for it.

On Aug 21, 2014, at 4:01 PM, Marshall T. Rose [email protected] wrote:

groovy! many thanks!

—
Reply to this email directly or view it on GitHub.

from node-openzwave.