RoomNode2 data format
I have connected a light sensor to 1 room node and am seeing readings appear on my HAH in the form Node ID followed by an integer similar to 168 and then some zeros. I have set up my jeenodeApplet.lua file to include light=1 and restarted the serial scheam and plugboard service but I am getting "?" in the value field from the light endnode.
Looking at the source for roomnode2.pde, the payload format specifies that light should come first, followed by moved etc.. My question is should the specification of the endnodes in jeenodeApplet.lua be in the same order as that in the source code of the roomnode?
Thanks for any help
Chris
Like Brett, I'm running with roomNode2 and the HAHcentral. The temp/lobat/moved/light are good for me. Batteries have been in place for 6 months and still no 'lobat'.
>am seeing readings appear on my HAH in the form Node ID followed by an integer similar to 168 and then some zeros.
Are you seeing this via microcom? If so, 168 is your LDR value. If you cover this over, the number should drop.
If this value is being reported at a rate greater than your 'ttl' setting, I'm confused as to why you might see a '?' on the endpoint.
The low frequency of readings that you see via microcom is intentional. I recall that (in order to save precious battery power) the light/lowbat/temp readings are only pumped out every 150secs or so. Only the PIR is interrupt driven, immediately reported and acknowledged by the HAHCentral - the thinking here is that the other values generally change quite slowly.
Do try moving the roomNode a lot closer to the HAH and upping the ttl until you get something working.
- Do read this thread http://www.homeautomationhub.com/content/how-get-roomnode-id
- Also are you using an instance setting? : http://www.homeautomationhub.com/content/jeenode-issue
- Did you enable xap-serial ? http://www.homeautomationhub.com/content/jeenode-xap-messages-state are you getting data?
Brett
Do you have any other scripts in the plugboard directory, if so remove them and restart the service as you have previously.
You could also try running the plugboard manually and see if you get any errors output to the console. To do this stop the scripting engine, through the web interface or by killing the process, and then login to the HAH and run xap-plugboard, read here for more info. This will hopefully show you any errors generated by the script. Post the errors back here so that we can try and resolve it.
Karl
Don't forget all the log files in /var/log which might contain hints of what went wrong. Note: a reboot will loose all of these so examine then BEFORE you reboot !
It looks like you might have defined a wrong endpoint name :-
lua: /usr/share/lua/5.1/xap/jeenode.lua:198: RoomNode[3]: has no 'humid' configurable endpoint stack traceback:
Check your jeenodeApplet file and change it to humi instead, read http://www.dbzoo.com/livebox/hah_hahnode#room_node for more info.
Karl
Glad it worked, I've corrected the Wiki.
You are confusing enabling the functionality with decoding structures these things are not related. As long as you specify light=1 somewhere in the configuration it will be enabled correctly. The payload you are seeing in the the RoomNode.PDE does match how the data is decoded in backend LUA decoder (I don't have the source to hand but I know its right) - I'm using both of these.
Do check the light sensor is between ANALOGUE and GND for the correct PORT, in anycase if you are getting a ? - it would imply your BASE Node unit is not receiving data as if it was you would see a '0' for your sensor even if it was incorrectly pinned. You have a comms problem between your nodes at this point that needs resolving first.
You do have 2 of these setup right- some people think they can just configure the base unit with a sketch and away they go. The unit in the HAH must be running HAH Central and be configured correctly and the other running roomNode2.pde. Verify you are getting comms before even setting up all the HAH LUA backend applets.
Brett