AEON HEM Gen5 missing values

I can not find this Command Classes:

COMMAND_CLASS_MULTI_CHANNEL V3
COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION_V2

How do I know if a Class Should hav NIF checked?

/Mike

They are multi_instance classes in the list - so -:

Itā€™s the top left corner of the command class table you posted above.

Can you remove NO_OPERATION in http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/375#endpoints and review.

I think i am finished :slight_smile:.

/Mike

1 Like

Done.

Thanks. Iā€™ll try and take a look tonight otherwise tomorrow.

Sorry missed the reset.
Should i use this parameter:

255 1.Value=0x55555555态Default=1态Size=4
Reset to factory default setting and removed from the zwave
network
N/A 4
2.Reset to factory default setting N/A 1

or put this in endpoint 0.

  <channel id="meter_reset" typeId="meter_reset">
    <label>Reset Meter</label>
    <properties>
      <property name="binding:*:OnOffType">METER,BASIC;reset=true</property>
    </properties>
  </channel>

/Mike

Yep - this one. If you add the meter_reset channel to the meter class, it should be right I think.

The other one completely resets the device - you donā€™t want that :wink:

How do i set the OnOffType?

/Mike

You donā€™t need to - just add this channel and it should sort it out I think.

Then I think i am ready.

/Mike

In order to get the meter reset channel do I have to delete the thing and the node27.xml?

Chris has to review it first and then put it into the build.

/Mike

Done alreadyā€¦

Just delete the thing and add it back again - no need to touch the XML file.

Now it seems to work as supposed :slight_smile: and i have learned to change devices.

/Mike

1 Like

@chris
I still receive this error

2017-03-27 22:19:30.739 [WARN ] [class.ZWaveMultiInstanceCommandClass] - NODE 9: CommandClass NO_OPERATION (0x00) not implemented by endpoint 1, fallback to main node.
2017-03-27 22:19:30.822 [WARN ] [class.ZWaveMultiInstanceCommandClass] - NODE 9: CommandClass NO_OPERATION (0x00) not implemented by endpoint 2, fallback to main node.
2017-03-27 22:19:35.910 [WARN ] [class.ZWaveMultiInstanceCommandClass] - NODE 9: CommandClass NO_OPERATION (0x00) not implemented by endpoint 3, fallback to main node.

Should i add NO_OPERATION to Endpoint 1-3?

/mike

Good question - can you provide a short debug log of whatā€™s happening around these warnings.

Have not succeed to capture the NO_OPERATION yet but i have captured this:

2017-03-28 13:37:11.536 [DEBUG] [ternal.converter.ZWaveMeterConverter] - Not the right scale E_W <> E_A
2017-03-28 13:37:11.537 [DEBUG] [ternal.converter.ZWaveMeterConverter] - Not the right scale E_KWh <> E_A
2017-03-28 13:37:11.540 [DEBUG] [ternal.converter.ZWaveMeterConverter] - Not the right scale E_V <> E_A

Do i have to change something?

More log

2017-03-28 13:37:11.497 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 14 00 04 00 09 0E 32 02 A1 6C 00 00 10 E0 00 00 00 00 00 00 E5
2017-03-28 13:37:11.503 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2017-03-28 13:37:11.505 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 14 00 04 00 09 0E 32 02 A1 6C 00 00 10 E0 00 00 00 00 00 00 E5
2017-03-28 13:37:11.507 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 14 00 04 00 09 0E 32 02 A1 6C 00 00 10 E0 00 00 00 00 00 00 E5
2017-03-28 13:37:11.509 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 09 0E 32 02 A1 6C 00 00 10 E0 00 00 00 00 00 00
2017-03-28 13:37:11.511 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 9: Application Command Request (ALIVE:STATIC_VALUES)
2017-03-28 13:37:11.512 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 9: Incoming command class METER
2017-03-28 13:37:11.513 [DEBUG] [.commandclass.ZWaveMeterCommandClass] - NODE 9: Received METER command V3
2017-03-28 13:37:11.515 [DEBUG] [.commandclass.ZWaveMeterCommandClass] - NODE 9: Meter: Type=Electric(1), Scale=A(5), Value=4.32
2017-03-28 13:37:11.516 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveMeterValueEvent
2017-03-28 13:37:11.517 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Got an event from Z-Wave network: ZWaveMeterValueEvent
2017-03-28 13:37:11.518 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Got a value event from Z-Wave network, endpoint = 0, command class = METER, value = 4.32
2017-03-28 13:37:11.520 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Updating channel state zwave:device:f1a14ae3:node9:meter_current to 4.32 [DecimalType]
2017-03-28 13:37:11.536 [DEBUG] [ternal.converter.ZWaveMeterConverter] - Not the right scale E_W <> E_A
2017-03-28 13:37:11.537 [DEBUG] [ternal.converter.ZWaveMeterConverter] - Not the right scale E_KWh <> E_A
2017-03-28 13:37:11.540 [DEBUG] [ternal.converter.ZWaveMeterConverter] - Not the right scale E_V <> E_A

/Mike

This ā€˜not the right scaleā€™ message us 100% normal and isnā€™t an issue. It simply means that if weā€™re looping over a number of meter channels that some donā€™t match the scale - this is correct.