Out of the blue my JeeNode which is in my airing cupboard has stopped sending out real values when I view the messages using XFX Viewer all 3 outputs (light, temp & lowbat) all show '?' for the state and text e.g.
xap-header
{
v=12
hop=1
uid=FF00D802
class=xAPBSC.info
source=dbzoo.livebox.jeenode:immersion.temp
}
input.state
{
state=?
text=?
}
Anyone know what is wrong/how I fix?
Member for
14 years 5 months? means nothing has been received from node.
The ? means that nothing has been received from the node for a while. So either the node isn't transmitting any more or the HAH basenode isn't receiving.
Have you tried resetting the node? Then reset the box?
Member for
17 yearsIf nothing else changed ...
... the most likely thing is that the batteries on the roomNode are drained. If your monitoring script raises an alert when the lowbat signal becomes active, you can have this act as a warning that the batteries are on their way out.
Member for
14 years 7 monthsI've put fresh batteries into
Member for
17 yearsNext thing to do
It's worth doing a manual inspection of what (if anything) is being received by the baseNode.
Telnet onto the HAH and kill off any processes that are using the serial port. Then fire up microcom and see what is coming in over the serial port.
Member for
14 years 7 monthsHi Derek, I know how to
I know how to telnet onto the box however can you tell me how I kill the processes and fire up microcom?
Member for
17 yearsA few basic busybox commands
Use 'ps' to list all of the running processes. 'kill -9 <process id>' will kill a specified process. kill the plugboard and any xap-serial processes.
microcom is just a simple terminal emulator 'microcom -s 57600 /dev/USBxx' (replace xx with the number of your USB port).
use 'dmesg' to check which USB port your cable has been allocated.
Member for
14 years 7 monthsNot getting anything back when I run microcom
usbserial.c: PL-2303 converter detected
usbserial.c: PL-2303 converter now attached to ttyUSB0 (or usb/tts/0 for devfs)
hub.c: USB new device connect on bus1/1/4, assigned device number 4
usbserial.c: PL-2303 converter detected
usbserial.c: PL-2303 converter now attached to ttyUSB1 (or usb/tts/1 for devfs)
Not getting anything back when I run microcom -s 57500 /dev/ttyUSB0 after killing the xap-serial process
# ps
PID USER VSZ STAT COMMAND
1 root 1796 S init
2 root 0 SW [keventd]
3 root 0 RWN [ksoftirqd_CPU0]
4 root 0 SW [kswapd]
5 root 0 SW [bdflush]
6 root 0 SW [kupdated]
7 root 0 SW [mtdblockd]
8 root 0 SW [khubd]
35 root 0 SWN [jffs2_gcd_mtd2]
101 root 1792 S udhcpc -T 10 -i br0
114 root 1668 S dropbear -p 22
126 root 1784 S tcpsvd -vE 0.0.0.0 21 ftpd -w /
138 root 1792 S crond
144 root 1028 S /usr/bin/xap-hub -i br0
147 root 1080 S /usr/bin/xap-pachube -i br0
148 root 1072 S /usr/bin/xap-livebox -s /dev/ttyS0 -i br0
155 root 1044 S /usr/bin/xap-serial -i br0
157 root 3976 S /usr/bin/kloned
159 root 2620 S /usr/bin/xap-currentcost -s /dev/ttyUSB1 -i br0
163 root 3796 S lua /etc_ro_fs/plugboard/plugboard.lua
193 root 1740 R dropbear -p 22
194 root 1812 S -ash
196 root 1784 R ps
# kill -9 155
# ps
PID USER VSZ STAT COMMAND
1 root 1796 S init
2 root 0 SW [keventd]
3 root 0 RWN [ksoftirqd_CPU0]
4 root 0 SW [kswapd]
5 root 0 SW [bdflush]
6 root 0 SW [kupdated]
7 root 0 SW [mtdblockd]
8 root 0 SW [khubd]
35 root 0 SWN [jffs2_gcd_mtd2]
101 root 1792 S udhcpc -T 10 -i br0
114 root 1668 S dropbear -p 22
126 root 1784 S tcpsvd -vE 0.0.0.0 21 ftpd -w /
138 root 1792 S crond
144 root 1028 S /usr/bin/xap-hub -i br0
147 root 1080 S /usr/bin/xap-pachube -i br0
148 root 1072 S /usr/bin/xap-livebox -s /dev/ttyS0 -i br0
157 root 3976 S /usr/bin/kloned
159 root 2620 S /usr/bin/xap-currentcost -s /dev/ttyUSB1 -i br0
163 root 3796 S lua /etc_ro_fs/plugboard/plugboard.lua
193 root 1740 S dropbear -p 22
194 root 1812 S -ash
197 root 1784 R ps
# microcom -s 57500 /dev/ttyUSB0
Member for
16 years 10 monthsMake sure you use the correct
Make sure you use the correct baud rate you entered 57500 which is wrong its 57600.
# microcom -s 57600 /dev/ttyUSB0
In any case before you got that low I would have checked to see if xap-serial was reporting xAP packets.
JEENODE BASE ----serial---> xap-serial ---> xAP (serial class)
xAP (serial class) -----> Plugboard.lua ---> JeeNodeApplet.lua ---> xAPBSC
Member for
14 years 5 monthsother process
You should also kill the plugboard process.
Do you have any other jeenodes or is this the only one?
Member for
14 years 7 monthsI’ve managed to get it to
I’ve managed to get it to work again, it turned out to relate to the USB Hub attached to my HAH since I’ve had this RoomNode/JeeNode it worked fine with an unpowered USB hub, all I did was add power to the existing hub and now it is working again! I have no idea why it would have worked for months unpowered and now it needs to be powered without any other changes?
Member for
17 yearsVery interesting
All I can think of is that something (temperature at the location of the HAH?) caused the HAH 5V line to drop below the point at which the regulator on the baseNode was happy to keep powering the AVR micro. We do know that folks who make use of the onboard relays of the HAH PCB are better to run the PCB via an external 5V supply ... could be a similar thing.
Anyway, thanks for persevering & letting us know what fixed it for you. I've added a note to the wiki.