First of all that 2012 be a great year for you all.
I have a problem with the daemon of Zigbee in Meshlium. Last night for the first time i was running my Meshlium and later I left the room and left the Meshlium working by itself. But this morning and to my surprise, at 7:55 am had stopped not know why.
07/01/2012 7:52:20-mac: 0000000000000000-x: 8-y: -150, z: 1014-temp: 26-bat: 40%
07/01/2012 7:52:20-mac: 0013a2004064ab6c-x: -26, y: -52, z: 997-temp: 27-bat: 41%
07/01/2012 9:45:25-mac: 0000000000000000-x: 8-y: -150, z: 1013-temp: 26-bat: 39%
07/01/2012 9:45:26-mac: 0000000000000000-x: 8-y: -150, z: 1013-temp: 26-bat: 39%
At 9:45 I went back to start the daemon.
There is some extra information I want to add:
1 .- Sometimes we don’t know if one or more nodes are detected with mac 0000000000000000, not sure, but I think it happens when I turn on the 11 pro zigbee nodes running alongside each other.
Could it be that being so close to the data is corrupted?
2 .- It is the second time that the daemon has stopped, I think this time may also be because there are nodes with mac 0000000000000000
3 .- Sometimes I work on the interface button to restart the daemon.
When this happens to me, I can’t resume with
The only thing that helped me is press the button "check status" at the interface, after that the demon begins
4 .- Sometimes when I connect by ssh tightly pushed in the Linux prompt I get a message like this:
I store db 0
I db 1 store
I store db 2
Connected to database: return:
BBDDSucceeded: insert into zigbeeData values (NULL, now (), '0013a2004064abcc ', '12', '-158', '1011 ', '27', '37%
Sometimes, this message appears from anywhere.
I hope you can help