Posts made by jmmorgan

I had also tried adding the mapping statement, but it had no effect. I have no idea what to try next.? Do you think it could be a problem with the node sketch up?
Thanks

I am currently running Openhab with Mysensor MQTT gateway and it reads the sensors fine. I have added a light switch to a node and Openhab. When I switch the light on, I see in the Openhab log state "received command on", but nothing shows up in the MQTT output, which I monitor with MQTT-spy. The item line in Openhab is :Switch node2_sw2 "sw2" {mqtt=">[mysensor:MyMQTT/2/5/V_LIGHT:command:ON:1],>[mysensor:MyMQTT/2/5/V_LIGHT:command:OFF:0]"}, where the node is 2 and the child_ID is 5. I do not know what to check next. Any help will be appreciated.
John

These modules do not have a SS pin, but rather NSS. Per this topic http://forum.mysensors.org/topic/466/ethernet-gateway-problem/37, these modules may not work. "Checked the board but I see no invertor IC on it so I think NSS is connected to /SCS pin (pin 29). Too bad. I think the shopping list should be updated to a board that has SPI_EN pin (pin 31) connected."

John

My Sensor:
I am trying to get the MQTT gateway to work. I have followed the instruction and I can ping the gateway, but I cannot connect. I know this has been discussed and I search the form, but none of the answers work for me. As the labels on the contact of the W5100 differ from what is on mysensor website, I wanted to check to make sure I was connect everything correct (Mysensor documentation-W5100).

1. GRD=GRD I know this is correct
2. VCC=V+5 This is supposed to be connected to 3.3 v, but it only works when connect to 5V (I assume that is why change the label to (v+5)
3. SCK=SOK???
4. MISO/SO=MI???
5. MOSI/SI=MO??
6. SS/CS=NSS???
   Any help would be appreciated.
   Thanks

It did change the IP in the new sketch. I finally got it to ping, but I am not quite sure how. Probably too many different version of the gateway in effort to get it to work.
Thanks

I am trying to ping my Ethernet Wiznet gateway version 1.4 from my PC. It says the destination is not found. Hence, my gateway does not work with my Vera. I was using gateway version 1.3 and I was able to ping it without problems. So it is not a hardware issue. The sketch for version 1.3 and 1.4 have the same settings. What am I missing?
Thanks
John

I have a similar problem. I upgraded from 1.3 to 1.4 and my Wiznet gateway does not work. I can ping version 1.3 from my PC and it see the gateway. When I ping 1.4 from my PC it says that the destination address can not be found. I have downloaded the latest Ethernet gateway sketch, but it did not help. Has any other file change that could effect this.
Thanks
John

Does anyone with a Vera2 have that file?

Can anyone tell me what setting they have in the /etc/cmh/serproxy.port file?

@wmylionel: Are you using Vera 2? If so what lines do you have in the /etc/cmh/serproxy.port file?
Thanks
John

@BulldogLowell It shows 9600

@hek
I set the L_Arduino.lua to 9600. The mysensor plugin now states to set the it 9600. I set it to 9600 and reload. It again states to set the serial port 9600 (but it is set to 9600), and the plugin fails. Is there something else I need to change?

@hek
How do you set it to 9600 in the Vera mysensor plug in? If I set the Vera serial port to 9600, the mysensor plug in states that it needs to be set to 115200 and the plug in fails.
Thanks
John

@hek
There is my serial configuration screen.

@hek the sensor send a request for the ID and the gateway acknowledge the request, but never send the id.

Here is my log. It seems the gateway startup ok and send the inclusion command. The node requests the ID, which the gateway acknowledge, but nothing happens after that.
jmmlog1.pdf

Well, I knew it was to good to be true. The plug-in loads properly without error and I have set the serial port. However, when I hit the start button (is it suppose to change color and stay that color until is stop) and reset the sensor, nothing happens. What is my next step. The sensor is sending a request for node id, which the gateway acknowledges, but it never send the node ID back. I tried looking at the Vera log, but there are just too many entries.

After much effort, I got it to recognize the serial gateway: Here what I did
Log into WinSCP
Run lsusb
You should see a line similar to this. Bus 001 Device 006: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x Composite Device. The 10c4 is the vendor and the ea60 is the product.

Find
/etc/cmh/serproxy.port
Open it up and make sure it has the line
vendor:10c4 product:ea60
If serproxy.port does not exist, manual create it.
Reboot, Reboot and hope.

Now on to the next step. I hope it is easier.

@hek I am using Arduino Nano, but it does not pop up in the serial configuration page. I have read a lot of the post on USB to serial connection on the Vera forum, but no luck.
JOhn

I am just starting to install my plug in for VERA 2. It created the plug in without a problems. When Vera starts the plug in it states that the serial port has to be selected. How do I do that? Under the serial port tab there is only my serial port for my alarm system. If I ssh into vera I can see both USB ports. My alarm port (usbserial.c: PL-2303 converter now attached to ttyUSB1 (or usb/tts/1 for devfs)0 and the gateway USB (usbserial.c: CP210X converter now attached to ttyUSB0 (or usb/tts/0 for devfs)). So I know it connects, but I do not know how to tell the plug in to use that port. Any help would be appreciated.
John

Thanks
So were to you find the syntax to parse the header such as message.header.??? And what is "atoi (message.data)". I hate to keep asking questions, if there is some place I could read up on it.

I need to understand message coding better. The overview is fine, but I was hoping for a link that would explain it more (i.e. what it message_s? etc).
Thanks
John