- turisimoMemberJune 25, 2013 at 1:11 amPost count: 16
I am sending this to my RaspP zbpserver
Node_BindTableRequest 48823 1
I get this back
Node_BindTableRequest 2 32aa173c-49e3-42d2-ae66-bde21979b449
but i see return status = 2 (what does that mean btw?) and no Node_BindTableRsp async reply is ever sent
I am trying to query an Insteon device to find out what controller’s/responders its linked with, i assume this is the right command to use for that ?
any suggestions on what i am doing wrong ?DhawalMemberJune 25, 2013 at 10:18 pmPost count: 259turisimoMemberJuly 17, 2013 at 5:46 amPost count: 16
Appologies got busy with work and only just got back to my Pi
I’ll give that a try and see if it resolves my problem
thanks again and much appreciated
SturisimoMemberJuly 18, 2013 at 3:58 amPost count: 16
ok i sent this
and get this back
which says i have 6 nodes, and node 2 is 0x6c65 which is my node 27749 which is an insteon lamp
so i send this
and get this error response = 2 again
if i send this to node 48823 , which is my PLM
i also get this
any help or assistance on what i am doing wrong would be greatly appreciated
SturisimoMemberJuly 18, 2013 at 4:29 amPost count: 16
btw the zbpserver log reports this
Jul 18 04:23:39 raspberrypi ZBPServer: ClientThread::Thread started
Jul 18 04:23:40 raspberrypi ZBPServer: HttpSessionStore: create new session with ID 3111ea0c-7897-48d7-adcd-e1b30ce0b037
Jul 18 04:23:45 raspberrypi ZBPServer: Inside Node_BindTableRequest
Jul 18 04:23:55 raspberrypi ZBPServer: ClientThread::Terminated!
I did notice my timeout waiting was only 10 seconds before closing the connnction,
I extended to 60 seconds but no difference
SDhawalMemberJuly 19, 2013 at 12:02 amPost count: 259
Looks like a bug in the ZBPServer, we are in the process of updating our debian package, will include a fix for this bug. Thanks for your help, i’ll let you know when the package is updated.
- You must be logged in to reply to this topic.