@skywatch after many nights of tshooting I found that my power brick was the one causing the issues. Not sure why it worked with old radio and not this one. It didn't cross my mind because it was a Samsung brand name 2000ma power brick and it was working properly, but last night it completely failed even with the old radio. I had no lights on my arduino or my ethernet module. I figured it was a good time to retest and the second I put it online with the new adapter it worked. Just wishing I would have tried that earlier...
Posts made by fifo
-
RE: [SOLVED] Troubleshooting MQTT Gateway with Amplified NRF24L01+PA+LNA Long Range Antenna
-
RE: [SOLVED] Troubleshooting MQTT Gateway with Amplified NRF24L01+PA+LNA Long Range Antenna
yes I have a 47uf Cap across the power. Ill try again soon and see what happens. Ill check to make sure the cap is soldered on correctly as well.
-
RE: [SOLVED] Troubleshooting MQTT Gateway with Amplified NRF24L01+PA+LNA Long Range Antenna
@Yveaux said in Troubleshooting MQTT Gateway with Amplified NRF24L01+PA+LNA Long Range Antenna:
heck the pinout?
I got these, https://amzn.to/380eBob "nRF24L01 SPI PA LNA 2.4GHz rf Module E01-ML01DP5 2.5km iot 2.4 ghz rf Transmitter Receiver with Shield for arduino nRF24L01P". The pinout does look identical. I haven't had a chance to plug the gateway into monitor to see what the logs are saying just yet.
-
RE: [SOLVED] Troubleshooting MQTT Gateway with Amplified NRF24L01+PA+LNA Long Range Antenna
Just got the modules but neither of them worked as a drop-in. Did you by any chance have to do anything different with these CD-Byte modules? I like that they are smaller and do look like the craftsmanship is a bit better. Was waiting for it to print out a case for it but I guess I am back to the drawing board. In the meantime, the older amplified modules are working great.
-
RE: [SOLVED] Troubleshooting MQTT Gateway with Amplified NRF24L01+PA+LNA Long Range Antenna
@BearWithBeard I found my problem. It turns out my arduino had a false contact on one of the ground pins I was using to power my radio. When I noticed, I resoldered the header pin on the nano and it magically started working. It works with both the normal and the long range antenna and I do see a big difference in range. Thanks for all the help again. Guess I will have some spare radios now...
-
RE: [SOLVED] Troubleshooting MQTT Gateway with Amplified NRF24L01+PA+LNA Long Range Antenna
@BearWithBeard awesome thanks again for your help!
-
RE: [SOLVED] Troubleshooting MQTT Gateway with Amplified NRF24L01+PA+LNA Long Range Antenna
@BearWithBeard ok sounds good, I assume with this I would be able to talk to all my other nodes that are on the pcb antenna type NRF modules. I purchased two of the CDEByte modules so I can add a repeater if needed later. I'll swing back in a month once I set it all up.
One other question, if I wanted to power this new module and a nano off of a good quality USB plug, could I get one of these https://amzn.to/38h3DfW and power it from the 5v pin on the nano to get my 3v3? If not any suggestions on what the best way to do that would be? Want to make sure I get whatever I need before the new modules get here.
Thanks again!
-
RE: [SOLVED] Troubleshooting MQTT Gateway with Amplified NRF24L01+PA+LNA Long Range Antenna
@BearWithBeard hello again, I went ahead and checked it and I did have the grounds bonded together so nothing. I tried a second antenna ( same brand) and get similar results. I tried adding another cap just in case the one I have is faulty but no difference. Unfortunately, I do not have a ceramic cap but I'll see if I can get one of those to test. I have gone ahead and ordered the CDEByte radios but they will take over a month to get here . I also made sure to reduce the PA level to min and still has the same effect. Guess I am going back to the normal pcb transceiver. Bummed out that I can't get this to work. I thought it would be a simple swap of modules although I did realize the power requirements were different. The aluminum foil thing didn't do a thing for me either. If you can think of anything else I can try let me know.
-
RE: [SOLVED] Troubleshooting MQTT Gateway with Amplified NRF24L01+PA+LNA Long Range Antenna
@BearWithBeard thanks for the response. Few things I might have failed to tie in both grounds so I will check on that today to see if that helps. I did try shielding with foil as well as lowering the PA but neither worked. I'll swing by in a bit and let you know if that floating ground may have been my issue. If it isn't I might consider the other radio you mentioned. What kind of range are you getting with those?
-
[SOLVED] Troubleshooting MQTT Gateway with Amplified NRF24L01+PA+LNA Long Range Antenna
Hi folks, I am having some issues with my gateway that I can't figure out. I have had my gateway setup for some time now but having issues with some nodes that are a little further away. To resolve the issue, I decided to use a long range antenna. I opted for this antenna link text. When operating from the regular NRF antenna I have no issues but when I swap it to this one, I lose communication to all my nodes, and my error led starts flashing. It flashes twice and stops. After researching a little I came across these error codes for the flashes. Each row indicates the error number so 2 flashes means Failed to Transmit messages which seems correct since I cant get it to communicate with anything.
INDICATION_ERR_HW_INIT, //!< HW initialization error my err->INDICATION_ERR_TX, //!< Failed to transmit message. INDICATION_ERR_TRANSPORT_FAILURE, //!< Transport failure. INDICATION_ERR_INIT_TRANSPORT, //!< MySensors transport hardware (radio) init failure. INDICATION_ERR_FIND_PARENT, //!< Failed to find parent node. INDICATION_ERR_GET_NODEID, //!< Failed to receive node ID. INDICATION_ERR_CHECK_UPLINK, //!< Failed to check uplink INDICATION_ERR_SIGN, //!< Error signing. INDICATION_ERR_LENGTH, //!< Invalid message length. INDICATION_ERR_VERSION, //!< Protocol version mismatch. INDICATION_ERR_NET_FULL, //!< Network full. All node ID's are taken. INDICATION_ERR_INIT_GWTRANSPORT, //!< Gateway transport hardware init failure. INDICATION_ERR_LOCKED, //!< Node is locked. INDICATION_ERR_FW_FLASH_INIT, //!< Firmware update flash initialisation failure. INDICATION_ERR_FW_TIMEOUT, //!< Firmware update timeout. INDICATION_ERR_FW_CHECKSUM, //!< Firmware update checksum mismatch.
I have tried different power supplies as I am feeding my Arduino nano with a regular USB 5V adapter you would use to charge your phone. I have the NRF power VCC pin being fed from the 3.3V pin on the arduino nano.
- I have tried multiple and all have the same effect.
- I have tried powering the radio separately as well using an external power supply from my home lab.
- At this point, I don't think the problem is power.
- I do have a capacitor 48uF 10V so I have that covered.
- Thinking it might be interference, I also covered my entire 3d printed housing with aluminum foil leaving only the antenna exposed but this did nothing except obstruct the led lights...
The Serial Monitor Log doesn't show me much of anything that gives me any clue as to what is going on.
Here are a few lines on the tail of that log.
1575208 TSF:MSG:FPAR REQ,ID=6 1575212 TSF:CKU:OK,FCTRL 1575215 TSF:MSG:GWL OK 1577435 !TSF:MSG:SEND,0-0-6-6,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0 1585840 TSF:MSG:READ,5-5-255,s=255,c=3,t=7,pt=0,l=0,sg=0: 1585845 TSF:MSG:BC 1585847 TSF:MSG:FPAR REQ,ID=5 1585850 TSF:PNG:SEND,TO=0 1585852 TSF:CKU:OK 1585854 TSF:MSG:GWL OK 1588473 !TSF:MSG:SEND,0-0-5-5,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0 1589928 TSF:MSG:READ,5-5-255,s=255,c=3,t=7,pt=0,l=0,sg=0: 1589934 TSF:MSG:BC 1589936 TSF:MSG:FPAR REQ,ID=5 1589939 TSF:CKU:OK,FCTRL 1589941 TSF:MSG:GWL OK 1592551 !TSF:MSG:SEND,0-0-5-5,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0 1592772 TSF:MSG:READ,3-3-255,s=255,c=3,t=7,pt=0,l=0,sg=0: 1592777 TSF:MSG:BC 1592779 TSF:MSG:FPAR REQ,ID=3 1592782 TSF:CKU:OK,FCTRL 1592784 TSF:MSG:GWL OK 1595167 !TSF:MSG:SEND,0-0-3-3,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0 1595585 TSF:MSG:READ,4-4-255,s=255,c=3,t=7,pt=0,l=0,sg=0: 1595590 TSF:MSG:BC 1595592 TSF:MSG:FPAR REQ,ID=4 1595595 TSF:CKU:OK,FCTRL 1595597 TSF:MSG:GWL OK 1597721 !TSF:MSG:SEND,0-0-4-4,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
It seems I am getting NACK. Any clue as to what I could try?
-
RE: Help sending nodes commands from openhab
@rozpruwacz said in Issue with item names when sending my nodes a command from openhab to my arduino -> mysensors mqtt gateway / openhab 2.2 snapshot / mosquitto:
t help You with your setup because actually I don't understand what You are doing But why You do it this way ? I have it like that: HabPanel is just an UI for OpenHAB, so I don't send anything from HabPanel just controll OH items. Some of them are mqtt items and they send/receive data to/from
Oh sorry I meant Arduino Nano is my gateway not a broker ( I edited above post to fix). I only have one broker which is the Raspberry Pi. So its basically the same thing but I want to send controls to my sensors via the HabPanel. I can receive from the sensors with no problems. It's the sending that doesnt work when I use the variable "${item}".
-
RE: Help sending nodes commands from openhab
@rozpruwacz said in Issue with item names when sending my nodes a command from openhab to my arduino -> mysensors mqtt gateway / openhab 2.2 snapshot / mosquitto:
what is this mqtt-eventbus.cfg file for
Ok I am by no means an expert, but what I understand it to be is to get all OpenHab events to look like an MQTT message and to thus allow you to update status of items in OpenHab using MQTT messages
So I have my GUI (HabPanel) sending messages to my broker (Raspberry Pi3) who sends info to my gateway (Arduino Nano) who in turn sends the data to my sensor whatever it may be.
It also works in reverse (this reverse part is working as I can get status update from some temp and PIR sensors I have running already)..
-
Help sending nodes commands from openhab
Communication Path
openhab 2.2 snapshot --> mosquitto (Broker) --> mysensors mqtt gateway --> mysensors nodeI can send the following command to my mosquitto broker and it works with no issue to turn a node on and off.
mosquitto_pub -t 'mysgateway-in/5/0/1/0/2' -m 'OFF' mosquitto_pub -t 'mysgateway-in/5/0/1/0/2' -m 'ON'
I am using HabPanel and set up a switch to basically toggle from OFF to ON
The OpenHab item is "mqttsw1"
my items file looks like this
Switch mqttsw1 "Switch 1" (all) {mqtt=">[mysgateway-in/5/0/1/0/2:command:*:default],>[mysgateway-in/5/0/1/0/2:command:off:default,<[mysgateway-in/5/0/1/0/2:command:*:default]]"}
My mqtt-eventbus.cfg looks like this. I believe the issue is in the commandPublishTopic and if I comment out the existing line and replace it with the one right below I can get at least that switch to work.
broker=mosquitto # When available, all status updates which occur on the openHAB event bus are published to the provided topic. The message content will # be the status. The variable ${item} will be replaced during publishing with the item name for which the state was received. #statePublishTopic= # When available, all commands which occur on the openHAB event bus are published to the provided topic. The message content will be the # command. The variable ${item} will be replaced during publishing with the item name for which the command was received. commandPublishTopic=mysgateway-in/${item} #commandPublishTopic=mysgateway-in/5/0/1/0/2 # When available, all status updates received on this topic will be posted to the openHAB event bus. The message content is assumed to be # a string representation of the status. The topic should include the variable ${item} to indicate which part of the topic contains the # item name which can be used for posting the received value to the event bus. stateSubscribeTopic=mosquitto/stateUpdates/${item}/state # When available, all commands received on this topic will be posted to the openHAB event bus. The message content is assumed to be a # string representation of the command. The topic should include the variable ${item} to indicate which part of the topic contains the # item name which can be used for posting the received value to the event bus. commandSubscribeTopic=mosquitto/commandUpdates/${item}/command
Here is what I get when I subscribe to the topic with the eventbus file above.
Client mosqsub/12310-raspberry received PUBLISH (d0, q0, r0, m0, 'mysgateway-in/mqttsw1', ... (3 bytes)) OFF Client mosqsub/12310-raspberry received PUBLISH (d0, q0, r0, m0, 'mysgateway-in/mqttsw1', ... (2 bytes)) ON
Of course it doesnt work because it is using the name of the device instead of "mysgateway-in/5/0/1/0/2" for this instance.
Any clue what I can be doing wrong? I just cant seem to find anything on the web to help me out with this and I am sure its something simple.
-
RE: Vera Plugin - Can't Press start for inclusion on Gateway
***That worked ! Big thanks to both of you. I am powering arduino directly from a usb cable connected to my pc. The wireless radio is on the 3.3v pin with other leg on gnd.
downgraded to .11
Plugged in to serial monitor***
0;255;3;0;9;TSM:INIT
0;255;3;0;9;TSF:WUR:MS=0
0;255;3;0;9;TSM:INIT:TSP OK
0;255;3;0;9;TSM:INIT:GW MODE
0;255;3;0;9;TSM:READY:ID=0,PAR=0,DIS=0
0;255;3;0;9;MCO:REG:NOT NEEDED
IP: 192.168.1.2
0;255;3;0;9;MCO:BGN:STP
0;255;3;0;9;MCO:BGN:INIT OK,TSP=1***Hit start and 0 devices appears button is acting better now and actually staying green
Plugged in my sensor
Eventually found 1 device and it took a while so I reloaded vera so that my sensors would appear.
I should have left it alone.
When it came back I had nothing. I went back to hit start and it was still pressed but this time it said it found 3 devices
left it there for about 10 more seconds and it went from start being highlighted to the stop button. It automatically restarted luua and now I get three devices.***
Arduino Temp 0(1)
Arduino Node 1
Arduino Repeater 0Looks like everything is working so I will leave it running and report later today.
Here is what my serial out looks like now. I'm wondering if some of that is still reboots? I don't see the line with the IP any more so it doesn't seem to be initializing but not sure what exactly to look for. It actually looks good to me.
;255;3;0;9;Eth: 1;255;3;0;6;I
0;255;3;0;9;!TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=6,pt=0,l=1,sg=0,ft=0,st=NACK:I
0;255;3;0;9;Eth:
0;255;3;0;9;TSF:MSG:READ,1-1-0,s=255,c=3,t=12,pt=0,l=3,sg=0:1.1
0;255;3;0;9;TSF:MSG:READ,1-1-0,s=0,c=0,t=6,pt=0,l=0,sg=0:
0;255;3;0;9;TSF:MSG:READ,1-1-0,s=255,c=3,t=26,pt=1,l=1,sg=0:2
0;255;3;0;9;!TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=27,pt=1,l=1,sg=0,ft=0,st=NACK:1
0;255;3;0;9;TSF:MSG:READ,1-1-0,s=0,c=1,t=0,pt=7,l=5,sg=0:73.6
0;255;3;0;9;TSF:MSG:READ,1-1-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;TSF:MSG:BC
0;255;3;0;9;TSF:MSG:FPAR REQ,ID=1
0;255;3;0;9;TSF:PNG:SEND,TO=0
0;255;3;0;9;TSF:CKU:OK
0;255;3;0;9;TSF:MSG:GWL OK
0;255;3;0;9;!TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
0;255;3;0;9;TSF:MSG:READ,1-1-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;TSF:MSG:BC
0;255;3;0;9;TSF:MSG:FPAR REQ,ID=1
0;255;3;0;9;TSF:CKU:OK,FCTRL
0;255;3;0;9;TSF:MSG:GWL OK
0;255;3;0;9;!TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
0;255;3;0;9;TSF:MSG:READ,1-1-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;TSF:MSG:BC
0;255;3;0;9;TSF:MSG:FPAR REQ,ID=1
0;255;3;0;9;TSF:CKU:OK,FCTRL
0;255;3;0;9;TSF:MSG:GWL OK
0;255;3;0;9;!TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
0;255;3;0;9;TSF:MSG:READ,1-1-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;TSF:MSG:BC
0;255;3;0;9;TSF:MSG:FPAR REQ,ID=1
0;255;3;0;9;TSF:PNG:SEND,TO=0
0;255;3;0;9;TSF:CKU:OK
0;255;3;0;9;TSF:MSG:GWL OK
0;255;3;0;9;!TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
0;255;3;0;9;TSF:MSG:READ,1-1-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;TSF:MSG:BC
0;255;3;0;9;TSF:MSG:FPAR REQ,ID=1
0;255;3;0;9;TSF:CKU:OK,FCTRL
0;255;3;0;9;TSF:MSG:GWL OK
0;255;3;0;9;!TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
0;255;3;0;9;TSF:MSG:READ,1-1-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;TSF:MSG:BC
0;255;3;0;9;TSF:MSG:FPAR REQ,ID=1
0;255;3;0;9;TSF:CKU:OK,FCTRL
0;255;3;0;9;TSF:MSG:GWL OK
0;255;3;0;9;!TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
0;255;3;0;9;TSF:MSG:READ,1-1-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;TSF:MSG:BC
0;255;3;0;9;TSF:MSG:FPAR REQ,ID=1
0;255;3;0;9;TSF:CKU:OK,FCTRL
0;255;3;0;9;TSF:MSG:GWL OK
0;255;3;0;9;TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
0;255;3;0;9;TSF:MSG:READ,1-1-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
0;255;3;0;9;TSF:MSG:PINGED,ID=1,HP=1
0;255;3;0;9;!TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=NACK:1
0;255;3;0;9;TSF:MSG:READ,1-1-0,s=255,c=3,t=15,pt=6,l=2,sg=0:0100
0;255;3;0;9;!TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=15,pt=6,l=2,sg=0,ft=0,st=NACK:0100
0;255;3;0;9;TSF:MSG:READ,1-1-0,s=255,c=0,t=17,pt=0,l=5,sg=0:2.1.0
0;255;3;0;9;TSF:MSG:READ,1-1-0,s=255,c=3,t=6,pt=1,l=1,sg=0:0
0;255;3;0;9;Eth: 1;255;3;0;6;I
0;255;3;0;9;!TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=6,pt=0,l=1,sg=0,ft=0,st=NACK:I
0;255;3;0;9;Eth:
0;255;3;0;9;TSF:MSG:READ,1-1-0,s=255,c=3,t=11,pt=0,l=18,sg=0:Temperature Sensor
0;255;3;0;9;TSF:MSG:READ,1-1-0,s=255,c=3,t=12,pt=0,l=3,sg=0:1.1
0;255;3;0;9;TSF:MSG:READ,1-1-0,s=0,c=0,t=6,pt=0,l=0,sg=0:
0;255;3;0;9;TSF:MSG:READ,1-1-0,s=255,c=3,t=26,pt=1,l=1,sg=0:2
0;255;3;0;9;TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=27,pt=1,l=1,sg=0,ft=0,st=OK:1
0;255;3;0;9;TSF:MSG:READ,1-1-0,s=0,c=1,t=0,pt=7,l=5,sg=0:73.6 -
RE: Vera Plugin - Can't Press start for inclusion on Gateway
Some more troubleshooting tonight. This is what I see on my Serial Monitor
0;255;3;0;9;TSM:INIT
0;255;3;0;9;TSF:WUR:MS=0
0;255;3;0;9;TSM:INIT:TSP OK
0;255;3;0;9;TSM:INIT:GW MODE
0;255;3;0;9;TSM:READY:ID=0,PAR=0,DIS=0
0;255;3;0;9;MCO:REG:NOT NEEDED
IP: 192.168.1.2
0;255;3;0;9;MCO:BGN:STP
0;255;3;0;9;MCO:BGN:INIT OK,TSP=1When I press the Inclusion START button on the VERA I see this happen on the Serial monitor.
0;255;3;0;9;Eth: connect
0;255;3;0;9;MCO:BGN:INIT GW,CP=RNNGA--,VER=2.1.1
0;255;3;0;9;TSM:INIT
0;255;3;0;9;TSF:WUR:MS=0
0;255;3;0;9;TSM:INIT:TSP OK
0;255;3;0;9;TSM:INIT:GW MODE
0;255;3;0;9;TSM:READY:ID=0,PAR=0,DIS=0
0;255;3;0;9;MCO:REG:NOT NEEDED
IP: 192.168.1.2
0;255;3;0;9;MCO:BGN:STP
0;255;3;0;9;MCO:BGN:INIT OK,TSP=1Now I pressed the start and turned on my temp module. And I see a bunch of stuff. Still the vera screen shows no proof that it is doing anything. The button doesnt stay depressed for a minute like it should and I get no message stating it found anything.
0;255;3;0;9;Eth: connect
0;255;3;0;9;MCO:BGN:INIT GW,CP=RNNGA--,VER=2.1.1
0;255;3;0;9;TSM:INIT
0;255;3;0;9;TSF:WUR:MS=0
0;255;3;0;9;TSM:INIT:TSP OK
0;255;3;0;9;TSM:INIT:GW MODE
0;255;3;0;9;TSM:READY:ID=0,PAR=0,DIS=0
0;255;3;0;9;MCO:REG:NOT NEEDED
IP: 192.168.1.2
0;255;3;0;9;MCO:BGN:STP
0;255;3;0;9;MCO:BGN:INIT OK,TSP=1
0;255;3;0;9;TSF:MSG:READ,1-1-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;TSF:MSG:BC
0;255;3;0;9;TSF:MSG:FPAR REQ,ID=1
0;255;3;0;9;TSF:CKU:OK,FCTRL
0;255;3;0;9;TSF:MSG:GWL OK
0;255;3;0;9;TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
0;255;3;0;9;TSF:MSG:READ,1-1-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
0;255;3;0;9;TSF:MSG:PINGED,ID=1,HP=1
0;255;3;0;9;!TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=NACK:1
0;255;3;0;9;MCO:BGN:INIT GW,CP=RNNGA--,VER=2.1.1
0;255;3;0;9;TSM:INIT
0;255;3;0;9;TSF:WUR:MS=0
0;255;3;0;9;TSM:INIT:TSP OK
0;255;3;0;9;TSM:INIT:GW MODE
0;255;3;0;9;TSM:READY:ID=0,PAR=0,DIS=0
0;255;3;0;9;MCO:REG:NOT NEEDED
IP: 192.168.1.2
0;255;3;0;9;MCO:BGN:STP
0;255;3;0;9;MCO:BGN:INIT OK,TSP=1
0;255;3;0;9;TSF:MSG:READ,1-1-0,s=255,c=0,t=17,pt=0,l=5,sg=0:2.1.0
0;255;3;0;9;MCO:BGN:INIT GW,CP=RNNGA--,VER=2.1.1
0;255;3;0;9;TSM:INIT
0;255;3;0;9;TSF:WUR:MS=0
0;255;3;0;9;TSM:INIT:TSP OK
0;255;3;0;9;TSM:INIT:GW MODE
0;255;3;0;9;TSM:READY:ID=0,PAR=0,DIS=0
0;255;3;0;9;MCO:REG:NOT NEEDED
IP: 192.168.1.2
0;255;3;0;9;MCO:BGN:STP
0;255;3;0;9;MCO:BGN:INIT OK,TSP=1
0;255;3;0;9;TSF:MSG:READ,1-1-0,s=0,c=0,t=6,pt=0,l=0,sg=0:
0;255;3;0;9;MCO:BGN:INIT GW,CP=RNNGA--,VER=2.1.1
0;255;3;0;9;TSM:INIT
0;255;3;0;9;TSF:WUR:MS=0
0;255;3;0;9;TSM:INIT:TSP OK
0;255;3;0;9;TSM:INIT:GW MODE
0;255;3;0;9;TSM:READY:ID=0,PAR=0,DIS=0
0;255;3;0;9;MCO:REG:NOT NEEDED
IP: 192.168.1.2
0;255;3;0;9;MCO:BGN:STP
0;255;3;0;9;MCO:BGN:INIT OK,TSP=1
0;255;3;0;9;TSF:MSG:READ,1-1-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;TSF:MSG:BC
0;255;3;0;9;TSF:MSG:FPAR REQ,ID=1
0;255;3;0;9;TSF:PNG:SEND,TO=0
0;255;3;0;9;TSF:CKU:OK
0;255;3;0;9;TSF:MSG:GWL OK
0;255;3;0;9;!TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
0;255;3;0;9;MCO:BGN:INIT GW,CP=RNNGA--,VER=2.1.1
0;255;3;0;9;TSM:INIT
0;255;3;0;9;TSF:WUR:MS=0
0;255;3;0;9;TSM:INIT:TSP OK
0;255;3;0;9;TSM:INIT:GW MODE
0;255;3;0;9;TSM:READY:ID=0,PAR=0,DIS=0
0;255;3;0;9;MCO:REG:NOT NEEDED
IP: 192.168.1.2
0;255;3;0;9;MCO:BGN:STP
0;255;3;0;9;MCO:BGN:INIT OK,TSP=1
0;255;3;0;9;TSF:MSG:READ,1-1-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
0;255;3;0;9;TSF:MSG:PINGED,ID=1,HP=1
0;255;3;0;9;!TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=NACK:1
0;255;3;0;9;MCO:BGN:INIT GW,CP=RNNGA--,VER=2.1.1
0;255;3;0;9;TSM:INIT
0;255;3;0;9;TSF:WUR:MS=0
0;255;3;0;9;TSM:INIT:TSP OK
0;255;3;0;9;TSM:INIT:GW MODE
0;255;3;0;9;TSM:READY:ID=0,PAR=0,DIS=0
0;255;3;0;9;MCO:REG:NOT NEEDED
IP: 192.168.1.2
0;255;3;0;9;MCO:BGN:STP
0;255;3;0;9;MCO:BGN:INIT OK,TSP=1Now if I do nothing, my serial monitor keeps showing this which I can only assume is my sensor sending it the temperature although I can't prove it because Im not really sure what I am looking at there.
0;255;3;0;9;TSF:MSG:READ,1-1-0,s=255,c=0,t=17,pt=0,l=5,sg=0:2.1.0
0;255;3;0;9;MCO:BGN:INIT GW,CP=RNNGA--,VER=2.1.1
0;255;3;0;9;TSM:INIT
0;255;3;0;9;TSF:WUR:MS=0
0;255;3;0;9;TSM:INIT:TSP OK
0;255;3;0;9;TSM:INIT:GW MODE
0;255;3;0;9;TSM:READY:ID=0,PAR=0,DIS=0
0;255;3;0;9;MCO:REG:NOT NEEDED
IP: 192.168.1.2
0;255;3;0;9;MCO:BGN:STP
0;255;3;0;9;MCO:BGN:INIT OK,TSP=1
0;255;3;0;9;TSF:MSG:READ,1-1-0,s=255,c=3,t=12,pt=0,l=3,sg=0:1.1
0;255;3;0;9;MCO:BGN:INIT GW,CP=RNNGA--,VER=2.1.1
0;255;3;0;9;TSM:INIT
0;255;3;0;9;TSF:WUR:MS=0
0;255;3;0;9;TSM:INIT:TSP OK
0;255;3;0;9;TSM:INIT:GW MODE
0;255;3;0;9;TSM:READY:ID=0,PAR=0,DIS=0
0;255;3;0;9;MCO:REG:NOT NEEDED
0;255;3;0;9;TSF:MSG:READ,1-1-0,s=0,c=0,t=6,pt=0,l=0,sg=0:
0;255;3;0;9;MCO:BGN:INIT GW,CP=RNNGA--,VER=2.1.1
0;255;3;0;9;TSM:INIT
0;255;3;0;9;TSF:WUR:MS=0
0;255;3;0;9;TSM:INIT:TSP OK
0;255;3;0;9;TSM:INIT:GW MODE
0;255;3;0;9;TSM:READY:ID=0,PAR=0,DIS=0
0;255;3;0;9;MCO:REG:NOT NEEDED
IP: 192.168.1.2
0;255;3;0;9;MCO:BGN:STP
0;255;3;0;9;MCO:BGN:INIT OK,TSP=1
0;255;3;0;9;TSF:MSG:READ,1-1-0,s=255,c=3,t=26,pt=1,l=1,sg=0:2
0;255;3;0;9;!TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=27,pt=1,l=1,sg=0,ft=0,st=NACK:1
0;255;3;0;9;MCO:BGN:INIT GW,CP=RNNGA--,VER=2.1.1
0;255;3;0;9;TSM:INIT
0;255;3;0;9;TSF:WUR:MS=0
0;255;3;0;9;TSM:INIT:TSP OK
0;255;3;0;9;TSM:INIT:GW MODE
0;255;3;0;9;TSM:READY:ID=0,PAR=0,DIS=0
0;255;3;0;9;MCO:REG:NOT NEEDED
IP: 192.168.1.2
0;255;3;0;9;MCO:BGN:STP
0;255;3;0;9;MCO:BGN:INIT OK,TSP=1At this point I restarted the vera not just luup and after a few minutes, I get exactly what I was expecting but not what I was hoping for. Absolutely no devices.
-
RE: 💬 Building an Ethernet Gateway
My WizNET (W5100) Ethernet module had to be connected to 5v pin on arduino as the 3.3v would only allow ping but not function properly.
-
Vera Plugin - Can't Press start for inclusion on Gateway
When I try to click the start button for inclusion it does nothing. I have tried updating the mysensors files to the latest as of today. I have also tried Firefox (Ubuntu), Chrome(Ubuntu), IE (Windows), and finally Chrome on android all with the same results. I have tried deleting and recreating the mysensors device as well but the button does nothing. I am running on a Vera Plus with UI7. Using the Ethernet Gateway with WizNET (W5100) Ethernet module.