Anyone has Aeotec ZW090 Z-Stick? Do you see it as Z-wave plus?

kembo · April 30, 2017, 9:18pm

Hi,

I got the Aeotec ZW090 Z-Stick Gen5 which is is supposed to be z-wave plus. It works well but I noticed that HA considers it as non zwave plus. (i.e. has is zwave plus false).

Do you also see the same?. Any hint what could be the reason?

Thanks

Coolie1101 · April 30, 2017, 9:53pm

Same, have no clue, maybe additional config in HA.

EID: zwave.aeotec_zw090_zstick_gen5_1

lastRequestRTT: 0
neighbors: 2
sentFailed: 0
is_zwave_plus: false
friendly_name: Aeotec ZW090 Z-Stick Gen5
sentCnt: 1
query_stage: Complete
retries: 0
sentTS: 2017-04-30 17:50:13:236
averageResponseRTT: 0
is_ready: true
is_failed: false
manufacturer_name: Aeotec
receivedCnt: 0
averageRequestRTT: 0
product_name: ZW090 Z-Stick Gen5
is_awake: true
is_info_received: true
receivedDups: 0
lastResponseRTT: 0
max_baud_rate: 40000
capabilities: beaming,listening,primaryController
receivedUnsolicited: 0
node_id: 1
receivedTS: 2017-04-30 17:50:13:135

farstreet · May 1, 2017, 6:18am

same for me

kirichkov · May 1, 2017, 6:58am

Same here.

dawnet · May 1, 2017, 7:17am

How do you check, I will look to see if I have the same issue would explain some of the problem I might be getting.

Cheers

Rich

andrey · May 1, 2017, 7:29am

This is for everyone.

The open-zwave library is to blame. We are not sure if it’s a reporting problem or if zwave+ protocol is not used at all on this device.

Coolie1101 · May 1, 2017, 9:21pm

/dev-state
Look at the attributes

Mukund · May 1, 2017, 10:23pm

same for me.

{
“is_ready”: true,
“receivedUnsolicited”: 0,
“node_id”: 1,
“receivedDups”: 0,
“lastResponseRTT”: 0,
“averageRequestRTT”: 0,
“averageResponseRTT”: 0,
“is_zwave_plus”: false
}

dawnet · May 2, 2017, 1:21pm

Cheers for this…

Same for me also

is_ready: true
manufacturer_name: Aeotec
sentCnt: 1
is_info_received: true
node_id: 1
lastRequestRTT: 0
is_awake: true
receivedCnt: 0
product_name: ZW090 Z-Stick Gen5
is_zwave_plus: false

jinnerbichler · July 24, 2017, 3:34pm

Same for me as well. Has anybody found a solution?

ncareau · January 31, 2018, 3:00am

same for me as well.

@andrey Is there an issue created with open-zwave or anything we could get update on ?

ajobbins · May 16, 2018, 4:01am

Same here. Are we missing out of the benefits of Z-Wave plus given the controller is a pretty important part of the network??

erikv · May 16, 2018, 1:16pm

Same here for me.

Tinkerer · May 16, 2018, 1:17pm

As has been said before - this is a bug/feature of the OpenZWave library and you can ignore it. Every controller, Z-Wave Plus or not, reports this way.

ajobbins · May 17, 2018, 3:12am

I get that it works, but is this ‘bug’ limiting the controller to non-plus functionality? Or is it still working as a plus device (with the features/benefits that come with it) and just mis-reporting the type?

Tinkerer · May 18, 2018, 5:02pm

Nope, not at all, it’s a reporting issue, hence why you can ignore it

(think about it for a moment, if it wasn’t operating in Plus mode then none of your Plus devices would operate as such)

brendan · August 15, 2018, 8:52am

Can anyone actually prove it works in plus mode with actual network data?.

A device reporting it is capable of plus does not mean it is running as such. The info is just a list of what it is capable of, not current operating mode.

Does anyone have anything that purely relies on plus features that will not work as intended in standard mode to test this?

It is one thing to say to think about it, but where is the proof it is using plus features?

These are the main features of Z-Wave Plus.

50% improvement in battery life
67% improvement in range
250% more bandwidth
Three RF channels for improved noise immunity and higher bandwidth
New Plug-n-Play Network-wide Inclusion feature
Improved self-healing and fault tolerance with Explorer Frame feature
Standardized method for Over the Air firmware updates (OTA)
Improved product information capture for product certification database

Apart from that, sensors and everything will work as usual, plus or not, as a plus device is backward compatible and will work on standard z-wave features.

Tinkerer · August 15, 2018, 9:02am

Well, I’ve included a number of Plus devices in-place, where they’re not able to directly see the controller.

That’s my mesh, all of the devices there were added in place. The only devices I couldn’t add in place were the non-Plus devices, that I removed before the next Plus devices were added (they replaced those).

When I removed those non-Plus devices the shape of my mesh changed. I used to have less yellow, and more pink and green. One of the remotes (the little blue boxes) would regularly fail to reach the mesh because it’s out on the edge, it’s worked reliably since.

Now, anecdotal to be sure as I don’t have a Z-Wave sniffer, but I think you’re worrying too much.

brendan · August 15, 2018, 9:25am

@Tinkerer

Anecdotal yes, and it could well be just a reporting issue, but there are people who want to know.

For me, as my network is not as spaced out as yours, I would not know what is running plus and what is standard. I have a mixture of devices that do and do not support plus. In theory, as long as it is not routing via a non-plus anywhere, a device will run plus.

With my mesh, it could do either and I would not know really as the speed makes little difference as the I do not have hundreds of devices and all devices I have are powered not battery operated.

I guess I am playing devils advocate a bit. Also, I would like to know if it is worth putting in a bug fix to the OZW developers.

B.

Tinkerer · August 15, 2018, 9:28am

Oh, I’m all in favour of the bug being fixed. Unless somebody can provide the actual fix to the OZW developers though I have little faith it will get fixed - browsing their mailing list and GitHub is depressing.