Problems adding devices to a network.
Miguel Nunes
I was able to compile a Jemma version and managed to create a standalone distribution.
I can log to the ZigBee Admin Console and confirm that the FlexKey dongle is detected.
I click on "Add new devices" and and during the 60 seconds available I try to add a Zone PIR Sensor.
I am out of luck as nothing new gets displayed.
Can someone help me?
Thanks in advance,
My config.properties file is the following:
# Autostart the ZigBee network: 0 to disable (it will wait for a StartGatewayDevice command), 1 to enabled
autostart = 1
# To enable debug messages select "1" (0 to disable)
debugEnabled = 0
# To enable debug messages Rs232 select "1" (0 to disable)
serialDataDebugEnabled = 0
#[DefaultStartupAttributeSet]
# Device Type (0 =Current device type; 1=Coordinator; 2=Router; 3=End Device)
DeviceType = 1
# Default Channel Mask [valid range: 11 - 26, OR '0' for all channels]
ChannelMask = 24 # End device uses this channel. Confirmed using Perytons
# ZigBee Network PANId ('0xFFFF' = generate random value)
PANId = 0xFFFF
# SimpleDescriptor
DefaultEndPoint = 0x01
ApplicationDeviceIdentifier = 0x0500
ApplicationDeviceVersion = 0x01
ApplicationProfileIdentifier = 0x0104
ApplicationInputCluster = 0x0000 0x0003 0x0702
ApplicationOutputCluster= 0x0000 0x0003
# Extended PAN Id (big-endian order) - Note: Set all zeros for Freescale dongle
ExtendedPANId = 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
#ExtendedPANId = 0x00 0x01 0x02 0x03 0x04 0x05 0x04 0x03 //ExtendedPanId used for Energy@Home trial
#ExtendedPANId = 0x00 0x00 0x00 0x10 0x77 0xC2 0x50 0x00 //ExtendedPanId used for commissioning mode
#ExtendedPANId = 0x00 0x00 0x72 0x6F 0x73 0x6E 0x65 0x73 //ExtendedPanId used for some ZigBee Telecom Services tests
# Startup Mode options:
# Commissioning Mode (0) - StartupSet=0x18 (CommissioningMode) AND StartupControlMode=0x00 (Association) --> To be used the first time, when the network is created
# NVM Mode (1) - StartupSet=0x00 (use NVM) AND StartupControlMode=0x04 (SilentStart) --> To be used at running time
# TrustCenter Replacement (2) - StartupSet=0x18 (CommissioningMode) AND StartupControlMode=0x04 (SilentStart) --> To be used for TC Replacement
# StartupSet
#0x00: UseNVMset (Copy NVM set (if any) to working set, then start. If no NVM, use ROM set.)
#0x08: UseROMset (Copy ROM set to working set (factory defaults),then start.)
#0x10: Useworkingset (Use working startup set in RAM.)
#0x18: UseCommissioningclusterset (Copy commissioning cluster set to working set, then start. If not valid, use NVM set.)
StartupSet = 0x00
# StartupControlMode (0=Association; 1=Orphan Rejoin; 2=Network Rejoin; 3=Find and Rejoin; 4=Silent Start)
#0x00: Association (Use association (ZR, ZED only), or form (ZC).)
#0x01: OrphanRejoin (FS specific: use orphan rejoin (ZR, ZED only).)
#0x02: NetworkRejoin (Use NWK rejoin (ZR, ZED only).)
#0x03: FindandRejoin (Valid for ZR, ZED only, search for network on this and other channels, then silent join.)
#0x04: SilentStart (Already part of the network (no form/join needed).)
StartupControlMode = 0x04
# Default Network Key - Note: Set all zeros for Freescale dongle
networkKey = 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
#networkKey = 0x01 0x02 0x03 0x42 0x65 0x65 0x41 0x6c 0x6c 0x69 0x61 0x6e 0x63 0x03 0x02 0x01
# Default Trust Center Link Key - 'ZigBeeAlliance09'
preconfiguredLinkKey = 0x5a 0x69 0x67 0x42 0x65 0x65 0x41 0x6c 0x6c 0x69 0x61 0x6e 0x63 0x65 0x30 0x39
#[DefaultDiscoveryAttributes]
# - 80 - Specify how long to wait (in seconds) before to start polling each node to verify if they're still alive ('0' to disable)
#keepAliveThreshold = 100
keepAliveThreshold = 60
# Once keepAliveThreshold is reached, GAL tries to ping the node for 'keepAliveNumberOfAttempt' before considering it dead
keepAliveNumberOfAttempt = 3
# Specify in seconds a timeout before to force the gateway to send a ping (MGMT_LQI_Req) to the nodes (0 to disable)
#forcePingTimeout = 180
forcePingTimeout = 150
# Automatic discovery unknown nodes before sending or after receiving a message (1 to enable, 0 to disable)
autoDiscoveryUnknownNodes = 1
#[TCKeyTable]
#TCKeyTableSize - Zero to disable the TrustCenterLinkKeytable - Note: maximum number of entries is 12 for Ember, 9 for Freescale
TCKeyTableSize = 0
#Entry n. 00
IEEEAddress00 = 0x00 0x0d 0x6f 0x00 0x00 0x09 0x99 0x1f
#TCLinkKey00 = 0x00 0x01 0x02 0x03 0x04 0x05 0x06 0x07 0x00 0x01 0x02 0x03 0x04 0x05 0x06 0x07
TCLinkKey00 = 0x5a 0x69 0x67 0x42 0x65 0x65 0x41 0x6c 0x6c 0x69 0x61 0x6e 0x63 0x65 0x30 0x39
#Entry n. 01
IEEEAddress01 = 0x00 0x0d 0x6f 0x00 0x00 0x09 0x93 0xa1
TCLinkKey01 = 0x00 0x01 0x02 0x03 0x04 0x05 0x06 0x07 0x00 0x01 0x02 0x03 0x04 0x05 0x06 0x08
#Entry n. 02
IEEEAddress02 = 0x00 0x0d 0x6f 0x00 0x00 0x18 0x57 0x46
TCLinkKey02 = 0x00 0x01 0x02 0x03 0x04 0x05 0x06 0x07 0x00 0x01 0x02 0x03 0x04 0x05 0x06 0x09
CommandTimeoutMS = 9000
TimeForcePingErrorSeconds = 10
TimeFreshnessErrorSeconds = 18
TimeDiscoveryErrorSeconds = 15
TimeForcePingNewNodeSeconds = 1
TimeFreshnessNewNodeSeconds = 3
TimeDiscoveryNewNodeSeconds = 0
NumberOfThreadForAnyPool = 5
#This is a minute value
KeepAliveThread = 3
TimeOutForWaitThread = 50
marco.n...@gmail.com
During the installation process of the new device, it has to respond to:
Ieeeaddress request,
NodeDescriptor request.
If these responses are ok and if the new node type is an enddevice, you can see this in the list.
If the new node type is a router or coordinator there is another request:
LQI request, and at the response it will add to the list.
Regards,
Marco N.
Marco Nieddu
Hi Marco,
Thank you very much for your attention.
In attach I send the log of a session of Jemma. Interestingly I can't find any messages like the ones you mentioned.
I also find a bit strange, that in the sniffer, I pickup very little messages from the End Device.
The only one that sometimes shows on the log is the Beacon Request (that's the one I used to figure out the channel).
Another strange thing is that when the End Device is connected alone (Coordinator Off) and I press the button to add it to a network I see a lot more packets in the sniffer. Do you think there can be some compatibility issues? If so, how do you sugest I can trackthe cause.
Best Regards,
Miguel Nunes
Software Developer
migan...@gmail.com
WSBP – We Solve Building Problems
Rua Pedro Nunes • IPN TecBis - Edifício E • 3030-199 Coimbra • Portugal
T +351 239 700 317 • F +351 239 700 318
www.wsbp.eu
Este email (incluindo quaisquer anexos) pode conter informação confidencial para uso exclusivo do destinatário.
Se não for o destinatário pretendido, não deve usar, distribuir, ou copiar este email.
Se recebeu esta mensagem por engano, por favor informe o emissor e elimine-a imediatamente.
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the sender and delete it immediately.
Inviato da iPhone
--
JEMMA - Java Energy ManageMent Application framework - http://jemma.energy-home.org
---
You received this message because you are subscribed to the Google Groups "JEMMA General Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jemma-genera...@googlegroups.com.
To post to this group, send email to jemma-...@googlegroups.com.
Visit this group at http://groups.google.com/group/jemma-general.
To view this discussion on the web visit https://groups.google.com/d/msgid/jemma-general/545BA049.4010102%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
Miguel Nunes
Thank you very much for your attention.
In attach I send the log of a session of Jemma. Interestingly I can't find any messages like the ones you mentioned.
I also find a bit strange, that in the sniffer, I pickup very little messages from the End Device.
The only one that sometimes shows on the log is the Beacon Request (that's the one I used to figure out the channel).
Another strange thing is that when the End Device is connected alone (Coordinator Off) and I press the button to add it to a network I see a lot more packets in the sniffer. Do you think there can be some compatibility issues? If so, how do you sugest I can trackthe cause.
Best Regards,
Software Developer
migan...@gmail.com
WSBP – We Solve Building Problems
Rua Pedro Nunes • IPN TecBis - Edifício E • 3030-199 Coimbra • Portugal
T +351 239 700 317 • F +351 239 700 318
www.wsbp.eu
Este email (incluindo quaisquer anexos) pode conter informação confidencial para uso exclusivo do destinatário.
Se não for o destinatário pretendido, não deve usar, distribuir, ou copiar este email.
Se recebeu esta mensagem por engano, por favor informe o emissor e elimine-a imediatamente.
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the sender and delete it immediately.
Hi, can you attach the log?During the installation process of the new device, it has to respond to:Ieeeaddress request,NodeDescriptor request.If these responses are ok and if the new node type is an enddevice, you can see this in the list.
If the new node type is a router or coordinator there is another request:LQI request, and at the response it will add to the list.
Regards,Marco N.
Inviato da iPhone
Ranalli Andrea
Dear Miguel,
Let me try to better understand what you’re trying to do.
First of all, I wish to understand why you’re using the GAL in C/C++ rather than the GAL in Java release, which is now the most update version for JEMMA. It already comes with the other OSGi bundles, while instead for the version that you’re using there is another setup, please clarify.
Second, the file that you’re try to associate is a Home Automation 1.1 product, while instead JEMMA is based on HA1.2, which includes some new commissioning procedure (Ez-Mode procedure) that this device may not support, so please verify before to continue with your integration. Perhaps, if you can tell us the name of the product that you’re trying to integrate it should be easier for us to support you.
Anyway, in general, you need to be sure at which channel your node is operating: supposing that it can work across all the channels, please set your sniffer to the channel selected automatically by JEMMA (or that you can specify by editing the config.ini). Once done, put your node in “association/joining” mode: I don’t know now how to do it since I don’t know yet your device but generally when you press some buttons (see the manual) you should start to see that your device starts to send “Beacon Request” command. Clearly, JEMMA will answer only to the previously selected channel, and thus if you’re sniffing on the wrong channel you won’t capture much more… L
To be sure that the JEMMA is up and running please be sure to sniff “link status” message, generally sent every 10-15 seconds by the coordinator of the network. This would guarantee you that if a Beacon Request is received by the coordinator in that specific channel you will see for sure a response (a beacon command).
Finally, please be aware that by default the network is closed and thus devices are not allowed to join: to open the network, you should enter in the /conf setting and open the network by pressing on “add device”, please let us know if you know where this path is located and how to do it.
Thanks in advance and best regards,
Andrea
------------------------------------------------------------------
Telecom Italia
Andrea Ranalli
Open Innovation Research – Future Internet Trial (SI.OIR.FIT)
Via di val cannuta, 182 00166 Roma
Mobile phone: +39 331 60 42 768
Land phone: +39 06 3688 8266
Fax number: +39 06 2331 6872
Da: jemma-...@googlegroups.com [mailto:jemma-...@googlegroups.com]
Per conto di Miguel Nunes
Inviato: venerdì 7 novembre 2014 11:34
A: Marco Nieddu Cv
Cc: Jemma General
Oggetto: Re: [jemma-general] Problems adding devices to a network.
To view this discussion on the web visit https://groups.google.com/d/msgid/jemma-general/545CA022.6000803%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
|
Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi
altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.
This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. |