some questions as a zuno-newbee but a little expirienced Arduino user ...
I want to program a combination device which is mainly a siren but also has one additional relais output.
I defined three items in ZUNO_SETUP_CHANNELS
Code: Select all
ZUNO_SETUP_CHANNELS( ZUNO_SIREN( SIREN_GETTER, SIREN_SETTER) ,ZUNO_SWITCH_BINARY( MULTIFUNC_GETTER, MULTIFUNC_SETTER) ,ZUNO_SWITCH_MULTILEVEL( SETTINGS_GETTER, SETTINGS_SETTER) );
My intention was to have
* channel 1 - the siren - with enable-setter ( with arg-value to control different siren behaviour ) and status-getter.
* channel2 - the multifunc relais ( as an additional switching output like in one of the examples )
* channel 3 - the settings regarding the siren ( how long it should signal )
The surprise is that after binding the zuno to zwave.me I see
* a new device which does not identify itself as a siren but in contrast it has 5 channels ( two dimmers and three switches ) where at least one channel interaction ( e.g. inreasing some dimmer value ) ends in the same setter at the zuno side.
The listed command classes in zwave.me are as follows:
Basic, SwitchBinary, SwitchMultilevel, AssociationGroupInformation, DEviceResetLocaly, ZWavePlusInfo, Multichannel, Configuration, ManufacturerSpecific, PowerLevel, FirmwareUpdate, Association, Version, MultichannelAssociation, SwitchBinary, SwitchBinary, SwitchMultilevel
The Device-mode at zuno side is ZUNO_SLEEPING_MODE_ALWAYS_AWAKE because I am still in debug stage and have not switched on the FLiR mode yet.
What I have done wrong?
What I have to implement for a device which should declare itself as an siren?
Why I get five channels/devices inside zwave.me although I only have declared three in the zuno?
Why some of them targeting same setters in the zuno?
What do I have to code that the bounded zuno-device itself has some well-sounding names for its channels in zwave.me