@celonunes Nope. I figured it out. In my openhab config file there was space prior to my MQTT related lines
" mqtt:mysensor.url=tcp://192.168.1.134:1883"
" mqtt:mysensor.clientId=OpenhabMQTT"
Instead of
"mqtt:mysensor.url=tcp://192.168.1.134:1883"
"mqtt:mysensor.clientId=OpenhabMQTT"
Removed the space and now I get my light sensor output value. I still don't get the sketch name coming through but I'll look into that later.
Ok. My primary problem was the radios I purchased form Ebay weren't the correct type. I've purchased new ones. Still got some problems to work through but I'll put in a seperate thread.
For others reading later:
Other references to these radios:
http://forum.mysensors.org/topic/878/no-debug-data-from-sensors-or-gateway-bad-radios
http://forum.mysensors.org/topic/728/radio-setup-give-check-wires/17
And specifically mentioned on the troubleshooting page as well.
I've been reading about measuring battery level on Vcc for battery powered setups that don't use any step-up converter by comparing it to the internal 1.1V reference. (examples: http://forum.mysensors.org/topic/186/new-library-to-read-arduino-vcc-supply-level-without-resistors-for-battery-powered-sensor-nodes-that-do-not-use-a-voltage-regulator-but-connect-directly-to-the-batteries ; http://provideyourown.com/2012/secret-arduino-voltmeter-measure-battery-voltage/ )
My question. Is it possible to perform the same measurement to determine the voltage coming in on Vraw. I currently power my boards with 4AA's and use the onboard power regulator (http://forum.mysensors.org/topic/483/2-aa-batteries-with-step-up-converter-to-vcc-pin-vs-3-aa-batteries-to-raw-pin/23).
@celonunes Nope. I figured it out. In my openhab config file there was space prior to my MQTT related lines
" mqtt:mysensor.url=tcp://192.168.1.134:1883"
" mqtt:mysensor.clientId=OpenhabMQTT"
Instead of
"mqtt:mysensor.url=tcp://192.168.1.134:1883"
"mqtt:mysensor.clientId=OpenhabMQTT"
Removed the space and now I get my light sensor output value. I still don't get the sketch name coming through but I'll look into that later.
I have restarted my router with no effect. The gateway still does not show up as an active client (using DDWRT) but I still have a connection from phone to gateway.
Added the above line. I've used one before like it but went back to what was given at the beggining of this thread to start anew. I also tried with the following edits
"Light Level"
"Light Level [%s]"
"Light Level [%.1f]"
None of which make a difference. The reason I think OpenHab doesn't even see the gateway is because nothing shows up in sketch name either which should work even if the above line was incorrect.
I have done the testing with the Android App turned off as well since I know OpenHab had some issues earlier if other clients were accessing the gateway.
I still see no reference to my gateway's IP in any of the OpenHab output/logs. So I'm not sure it is even trying.
The only error message in my openhab log is:
11:23:46.951 [ERROR] [sphere.cpr.AtmosphereFramework:2215 ] -
I tried clearing the EEPROM in the gateway. I changed it's Mac address and removed the DHCP lease for it from my router. Still no evidence of the gateway on my router status page but also still able to connect to it with my phone.
Another update:
I installed Mosquitto and I see the light sensor level using mosquitto_sub -h 192.168.1.134 -t MyMQTT
Crazy- I was thinking my network connection as a source of the problem. On my router homepage the gateway does not show up as being given an IP. However, the MyMQTT Android App sees the gateway without issue so the routing across my network from phone to gateway is successful. I have attached a screenshot of the MyMQTT andoird app output.
I am trying to run OpenHab on a windows PC. I don't have mosquitto running at all. My understanding is that it is not required.
I can't seem to get openhab to communicate with my MQTT gateway. I can connect to the gateway with the MyMQTT Android app and I receive messages from my light sensor node including the sketch name and light level. I can ping my gateway without issue as well.
However, OpenHab never seems like it notices the gateway. No data in the sketch name or node result. I've used the sitemap, items, and config files as described above and I've also customized them to match my sensor node more specifically. Both without success. The only change I've made is my sensor node is defined as node ID 20 within it's sketch.
When using start_Debug.bat what should I see in the command line window to indicate OpenHab even sees or connects to the gateway. I see no indication that it attempts to connect to the IP address of my gateway.
Thanks
Ok. My primary problem was the radios I purchased form Ebay weren't the correct type. I've purchased new ones. Still got some problems to work through but I'll put in a seperate thread.
For others reading later:
Other references to these radios:
http://forum.mysensors.org/topic/878/no-debug-data-from-sensors-or-gateway-bad-radios
http://forum.mysensors.org/topic/728/radio-setup-give-check-wires/17
And specifically mentioned on the troubleshooting page as well.
I added capacitors to my radios to see if that would help. I'm also testing with a serial gateway without much difference. I tried assigning a node id of 1. Didn't seem to change much.
The debug output goes to the serial monitor correct? I'm wondering why I'm not getting any debug messages.
I turned on failure_handling within the rf24 config. Now I get the following messageon my serial output:
send: 255-255-255-0 s=255,c=3,t=3,pt=0,l=0,st=fail:
as well as:
sensor started, id 255
req node id
This happens three times before it appears to give up and runs the rest of the parent sketch which starts a serial output of A0.
I forgot about the .cpp files. Did I tell you I was new to this?
So by placing serial.println commands in my mysensors.cpp file I have identified where things seem to get stuck:
Within the findparentnode routine:
Serial.println("FPN1");
sendWrite(BROADCAST_ADDRESS, msg, true);
Serial.println("FPN1");
I'll keep investigating when I get time. Thanks for your help