- Ask a related questionWhat is a related question?A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
Hello!
I am working with Z-Stack Linux Gateway 1.0.1 with beaglebone black and CC2531 dongle. I followed the instructions as given in quick start guide.
I hit ./zigbeeHAgw bbb
and I get following output:
root@beaglebone:/home/debian/Desktop/Z-Stack_Linux_Gateway-1.0.1/Precompiled_arm/servers# ./zigbeeHAgw bbb running zigbeegw.scr on an ARM resetting beaglebone black sleeping 6 seconds after reset... Using serial port: /dev/ttyACM0 /dev/ttyACM0: No such file or directory /dev/ttyACM0 open failed /dev/ttyACM0: No such file or directory /dev/ttyACM0 open failed done stty: /dev/ttyACM0: No such file or directory stty: /dev/ttyACM0: No such file or directory Starting the ZigBee gateway subsystem deviceKey = 0 (0 ) devPath = '/dev/ttyACM0' logPath = './NpiLnxLog.txt' ... freeing memory (ret 0) Port: 2533 Following IP addresses are available: IPv4: interface: lo IP Address 127.0.0.1 IPv4: interface: eth0 IP Address 192.168.2.72 IPv4: interface: usb0 IP Address 192.168.7.2 IPv6: interface: lo IP Address ::1 IPv6: interface: eth0 IP Address fe80::6eec:ebff:feab:e722 The socket will listen on the following IP addresses: IPv4: 0.0.0.0 IPv6: :: 0.0.0.0 means it will listen to all available IP address waiting for first connection on #3... NPI started (pid 4559) at Thu May 15 02:22:31 UTC 2014 Connected to #5.(127.0.0.1 / ::e8f7:80be:30f8:80be) ^Ccaught SIGTERM, killing all the servers and cleaning up terminating zigbeeHAGW (pid 4402) Killed
The output of dmesg is:
root@beaglebone:~# dmesg | grep tty
[ 0.000000] Kernel command line: console=tty0 console=ttyO0,115200n8 quiet drm.debug=7 capemgr.enable_partno=BB-UART4 root=UUID=aa948514-2113-43af-9436-1317aadd4462 ro rootfstype=ext4 rootwait fixrtc quiet init=/lib/systemd/systemd
[ 0.000000] console [tty0] enabled
[ 0.535601] 44e09000.serial: ttyO0 at MMIO 0x44e09000 (irq = 72) is a OMAP UART0
[ 0.547473] console [ttyO0] enabled
[ 0.723140] 481a8000.serial: ttyO4 at MMIO 0x481a8000 (irq = 45) is a OMAP UART4
[ 1.259463] cdc_acm 1-1:1.0: ttyACM0: USB ACM device
[ 34.266205] cdc_acm 1-1:1.0: ttyACM0: USB ACM device
[ 224.041942] cdc_acm 1-1:1.0: ttyACM1: USB ACM device
[ 238.271082] cdc_acm 1-1:1.0: ttyACM0: USB ACM device
Please tell me if I have missed out something
thanks
YK,
Thank you very much for all your help so far. I'm having an issue with (I think) device attributes. I have no trouble turning on and off a switch but I cannot get input from a simple switch, a temperature measurement device and a motion sensor. The simple switch and temperature sensor are enddpoints on the same device - a Samsung multipurpose sensor (IEEE Addr 00:0D:6F:00:05:98:6E:F1 ). The motion sensor is also Samsung (IEEE Addr 00:0D:6F:00:05:A3:07:F5). Below is my log file, and attached is my configuration for the TI gateway demo file gateway_config.tlg:
//.......... Samsung MultiSensor ................
// Device IDs
#define DeviceID_CombinedInterface 0x0007
// Cluster IDs
#define BasicClusterId 0x0000
#define IdentifyClusterId 0x0003
#define BinaryClusterId 0x000f
#define TempSensorClusterId 0x0402 //0x00402 is TempSense ClusterId and 0x0302 for HVAC ClusterId TempSense DeviceId.
#define UnknownClusterId 0x0019 // Suggested by Samsung!!
endpoint { 9, CombinedInterfaceEpDef, CombinedInterfaceAttrList }
endpointdef CombinedInterfaceEpDef { ha_profile, DeviceID_CombinedInterface , 0, CombinedInterfaceInputClusters, CombinedInterfaceOutputClusters }
// clusterlists include a list of clusters
// the common ZigBee clusters, such as basic, groups can use the symbol, rather than the number (e.g. 0x0006 or onoff) USE: 0x000f for Binary On/Off or Open/Close.
clusterlist CombinedInterfaceOutputClusters { BasicClusterId, IdentifyClusterId }
clusterlist CombinedInterfaceInputClusters { BasicClusterId, BinaryClusterId, TempSensorClusterId }//, UnknownClusterId } //0x000f is the 'Binary Input' cluster id. and 0x0090 is the window status attribute.
// attrs include an identifier, data type, and access control
attr Identify_IdentifyTimeAttr { IdentifyClusterId, 0x0000, uint16, rdwr }
attr Basic_ZCLVersionAttr { BasicClusterId, 0x0000, uint8, rdonly }
attr Basic_BinaryInputAttr { BinaryClusterId, 0x0055, uint8, rdwr } // 0x0055 reports 'PresentValue' (p170 ZigBee Spec.)
attr TempSensorAttr { TempSensorClusterId, 0x0000, uint16, rdonly }
//attr UnknownAttr { UnknownClusterId, 0x0090, uint8, rdonly}
// attrlists are a collection of attributes
attrlist CombinedInterfaceAttrList { Identify_IdentifyTimeAttr, Basic_ZCLVersionAttr, Basic_BinaryInputAttr,TempSensorAttr }//, UnknownAttr }
//attrlist CombinedInterfaceAttrList { Identify_IdentifyTimeAttr, Basic_BinaryInputAttr,TempSensorAttr }
//.......... Motion Sensor ................
// Device IDs
#define DeviceID_IAS_Zone 0x0402
// Cluster IDs
#define BasicClusterId 0x0000
#define IdentifyClusterId 0x0003
#define IAS_ZoneClusterId 0x0500
endpoint { 8, IAS_ZoneEpDef, IAS_ZoneAttrList }
endpointdef IAS_ZoneEpDef { ha_profile, DeviceID_IAS_Zone , 0, IAS_ZoneInputClusters, IAS_ZoneOutputClusters }
// clusterlists include a list of clusters
clusterlist IAS_ZoneOutputClusters { BasicClusterId, IAS_ZoneClusterId }
clusterlist IAS_ZoneInputClusters { BasicClusterId, IdentifyClusterId }
// attrs include an identifier, data type, and access control
// special case: if attribute datatype is charstring or octetstring, a length byte follows the type
// { 99, charstring, 16, rdwr } // a character string up to 16 bytes
attr Identify_IdentifyTimeAttr { IdentifyClusterId, 0x0000, uint16, rdwr }
attr Basic_ZCLVersionAttr { BasicClusterId, 0x0000, uint8, rdonly }
attr IAS_ZoneMotionSensorAttr { IAS_ZoneClusterId, 0x000d, uint8, rdonly }
// attrlists are a collection of attributes
attrlist IAS_ZoneAttrList { Identify_IdentifyTimeAttr, Basic_ZCLVersionAttr, IAS_ZoneMotionSensorAttr }
YK,
Thank you very much for all your help so far. I'm having an issue with (I think) device attributes. I have no trouble turning on and off a switch but I cannot get input from a simple switch, a temperature measurement device and a motion sensor. The simple switch and temperature sensor are enddpoints on the same device - a Samsung multipurpose sensor (IEEE Addr 00:0D:6F:00:05:98:6E:F1 ). The motion sensor is also Samsung (IEEE Addr 00:0D:6F:00:05:A3:07:F5). Below is my log file, and attached is my configuration for the TI gateway demo file gateway_config.tlg:
//.......... Samsung MultiSensor ................
// Device IDs
#define DeviceID_CombinedInterface 0x0007
// Cluster IDs
#define BasicClusterId 0x0000
#define IdentifyClusterId 0x0003
#define BinaryClusterId 0x000f
#define TempSensorClusterId 0x0402 //0x00402 is TempSense ClusterId and 0x0302 for HVAC ClusterId TempSense DeviceId.
#define UnknownClusterId 0x0019 // Suggested by Samsung!!
endpoint { 9, CombinedInterfaceEpDef, CombinedInterfaceAttrList }
endpointdef CombinedInterfaceEpDef { ha_profile, DeviceID_CombinedInterface , 0, CombinedInterfaceInputClusters, CombinedInterfaceOutputClusters }
// clusterlists include a list of clusters
// the common ZigBee clusters, such as basic, groups can use the symbol, rather than the number (e.g. 0x0006 or onoff) USE: 0x000f for Binary On/Off or Open/Close.
clusterlist CombinedInterfaceOutputClusters { BasicClusterId, IdentifyClusterId }
clusterlist CombinedInterfaceInputClusters { BasicClusterId, BinaryClusterId, TempSensorClusterId }//, UnknownClusterId } //0x000f is the 'Binary Input' cluster id. and 0x0090 is the window status attribute.
// attrs include an identifier, data type, and access control
attr Identify_IdentifyTimeAttr { IdentifyClusterId, 0x0000, uint16, rdwr }
attr Basic_ZCLVersionAttr { BasicClusterId, 0x0000, uint8, rdonly }
attr Basic_BinaryInputAttr { BinaryClusterId, 0x0055, uint8, rdwr } // 0x0055 reports 'PresentValue' (p170 ZigBee Spec.)
attr TempSensorAttr { TempSensorClusterId, 0x0000, uint16, rdonly }
//attr UnknownAttr { UnknownClusterId, 0x0090, uint8, rdonly}
// attrlists are a collection of attributes
attrlist CombinedInterfaceAttrList { Identify_IdentifyTimeAttr, Basic_ZCLVersionAttr, Basic_BinaryInputAttr,TempSensorAttr }//, UnknownAttr }
//attrlist CombinedInterfaceAttrList { Identify_IdentifyTimeAttr, Basic_BinaryInputAttr,TempSensorAttr }
//.......... Motion Sensor ................
// Device IDs
#define DeviceID_IAS_Zone 0x0402
// Cluster IDs
#define BasicClusterId 0x0000
#define IdentifyClusterId 0x0003
#define IAS_ZoneClusterId 0x0500
endpoint { 8, IAS_ZoneEpDef, IAS_ZoneAttrList }
endpointdef IAS_ZoneEpDef { ha_profile, DeviceID_IAS_Zone , 0, IAS_ZoneInputClusters, IAS_ZoneOutputClusters }
// clusterlists include a list of clusters
clusterlist IAS_ZoneOutputClusters { BasicClusterId, IAS_ZoneClusterId }
clusterlist IAS_ZoneInputClusters { BasicClusterId, IdentifyClusterId }
// attrs include an identifier, data type, and access control
// special case: if attribute datatype is charstring or octetstring, a length byte follows the type
// { 99, charstring, 16, rdwr } // a character string up to 16 bytes
attr Identify_IdentifyTimeAttr { IdentifyClusterId, 0x0000, uint16, rdwr }
attr Basic_ZCLVersionAttr { BasicClusterId, 0x0000, uint8, rdonly }
attr IAS_ZoneMotionSensorAttr { IAS_ZoneClusterId, 0x000d, uint8, rdonly }
// attrlists are a collection of attributes
attrlist IAS_ZoneAttrList { Identify_IdentifyTimeAttr, Basic_ZCLVersionAttr, IAS_ZoneMotionSensorAttr }
