UI5 Mysensors library 2.0 gateway issues
-
I meant what should I see in the serial monitor? This is what is being reported:
TSM:INIT TSM:RADIO:OK TSM:FPAR TSP:MSG:SEND 255-255-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc: TSP:MSG:READ 0-0-255 s=255,c=3,t=8,pt=1,l=1,sg=0:0 TSP:MSG:FPAR RES (ID=0, dist=0) TSP:MSG:PAR OK (ID=0, dist=1) TSM:FPAR:OK TSM:ID TSP:MSG:SEND 255-255-0-0 s=255,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=ok: TSM:ID TSP:MSG:SEND 255-255-0-0 s=255,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=ok: TSM:ID TSP:MSG:SEND 255-255-0-0 s=255,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=ok: TSM:ID TSP:MSG:SEND 255-255-0-0 s=255,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=ok: !TSM:CHKID:FAIL (ID=255) !TSM:FAILURE TSM:PDTI am guessing I should see something like "TSP:MSG:READ..."
-
@dbemowsk said:
TSP:MSG:READ 0-0-255 s=255,c=3,t=8,pt=1,l=1,sg=0:0
I know there is somewhere that explains this format seen in the serial monitor, but I can't remember where. The serial API message structure page explains the format that you referred to (255;255;3;0;4;<new node id>), but I need to understand what the s, c, pt, l , sg, ft and st all mean, as well as other information seen in the serial monitor.
-
Just a note. The debug page explains s, c, p, pt, l and sg, but it doesn't explain ft and st. I would assume that an st=ok means that the transmission was successful, but unsure on what ft is. maybe that could be added to the troubleshooting page.
EDIT: my appologies, I see it on the transport messages page.
-
I still do not have this working. Here is a list of things I have tried
- having the sensor right next to the gateway
- changed radios on the gateway
- changed capacitor on the gateway from a 4.7uf to a 47uf
- changed radios on the sensor
- cleared eeprom several times and tried pairing
- tried pairing 2 different sensors (both which worked with Domoticz)
- tried both the development and standard UI7 versions of the plugin
One of the things that I have not tried as of yet is changing the USB FTDI adapter. I am pretty sure I have a spare in the parts box. IF not, I will try the one that I use for programming my sensors. I will also test the FTDI I have connected to Vera for programming my sensors to see if it can do that.
-
So it appears that the saga has been solved. The problem in fact WAS with the FTDI adapter. In all of the testing that I did I am guessing that the FTDI's receive data was working, but the transmit data was the issue. I put my spare FTDI on and Vera was detecting devices left and right. I think I am going to have to redo the inclusion because it said that there were 5 devices found, but nothing was added to Vera, but like I say, the devices did not appear to be presenting at the time.
I want to say though that I appreciate all the time that people spent trying to help me get this going. This forum is a GREAT crowd of people.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login