Time-out on multiChannelNodeId about node-homey-zwavedriver HOT 6 CLOSED

Might be related to https://github.com/athombv/homey/issues/773

from node-homey-zwavedriver.

Not related, Meter CC just times out from time to time.

Does it show both end Nodes in the debug?
or just end node 1

Does it also happen if you leave away the Meter CC in endnode 1?
maybe we need to add a small timeout when multiple Meter CC commands are being called.

from node-homey-zwavedriver.

It shows only channel 0. Channels 1,2 and 3 time-out.

Will try later without Meter CC.

from node-homey-zwavedriver.

channel 0? i don't know any devices that use endnode 0

what device are we talking about? model number etc

from node-homey-zwavedriver.

BeNext P1 Dongle

I recieved the following information from benext:
`Kanaal 0

• Wattage
  • METER_REPORT zonder ratetype (reserved) (teruglevering wordt bepaald a.d.h.v. negatieve signed waarden)
• kWh van verbruikte energie
  • METER_REPORT met ratetype 1 (used)

Z-Wave Kanaal 1 (energie hoog tarief )

• Wattage verbruikte energie
  • METER_REPORT met ratetype 1 (import)
• Wattage opgewekte energie
  • METER_REPORT met ratetype 2 (export)
• kWh van verbruikte energie
  • METER_REPORT met ratetype 1 (import)
• kWh van teruggeleverde energie
  • METER_REPORT met ratetype 2 (export)

Z-Wave Kanaal 2 (energie laag tarief )

• Wattage verbruikte energie
  • METER_REPORT met ratetype 1 (import)
• Wattage opgewekte energie
  • METER_REPORT met ratetype 2 (export)
• kWh van verbruikte energie
  • METER_REPORT met ratetype 1 (import)
• kWh van teruggeleverde energie
  • METER_REPORT met ratetype 2 (export)

Z-Wave Kanaal 3 (gasstanden)

• totaal m3 stand
  • METER_REPORT`

from node-homey-zwavedriver.

this issue can be closed, someone made it work with the p1 dongle
https://github.com/ajterpstra/eu.benext

from node-homey-zwavedriver.