Wireless nRF24L01+ sniffer for MySensors
-
Hi there,
The (my:blush: ) sniffer tool has trouble interpretating float values, received from temperature/humidity sensors.
The data payload indicates that the sniffer receives 5 bytes instead of the expected 4 bytes of the float32 variable, the extra byte is always a 0x01. The preceeding 4 bytes are the expected bytes of the float.
After swapping the hardware, both cpu and nrf24 , still the same result....
Integers and booleans are received OK, and my serial gateway receives the correct float values. -
@Yveaux
Hi, thanks for the quick response....
But I do not understand: I get float values on my screen but the wrong interpretation.
Perhaps a better question: is there an indication when this will be solved, as I appreciate the sniffer tool very much!? -
@Yveaux
Hi, thanks for the quick response....
But I do not understand: I get float values on my screen but the wrong interpretation.
Perhaps a better question: is there an indication when this will be solved, as I appreciate the sniffer tool very much!?was not implemented yet
Maybe I should rephrase: it was implemented, but doesn't work right ;-)
See: https://github.com/Yveaux/NRF24_Sniffer/issues/2For MySensors 2.0 the sniffer will have to be updated.
I might pick this one up along the way. -
was not implemented yet
Maybe I should rephrase: it was implemented, but doesn't work right ;-)
See: https://github.com/Yveaux/NRF24_Sniffer/issues/2For MySensors 2.0 the sniffer will have to be updated.
I might pick this one up along the way. -
@Yveaux said in Wireless nRF24L01+ sniffer for MySensors:
For MySensors 2.0 the sniffer will have to be updated.
Any chance for Mysensrs 2.1.1 support? -
@bilbolodz not from my side anywhere soon... Just too busy...
-
Wireshark is version 3, MySensors 2.3.1 released 2018. nrf24 protocol with old dll is not working. Cost me hours tot find out it is "Oude Meuk", and not working with Wireshark error message "dissector not found". Please @Hek and @Yveaux release working version or wipe it from the forum at many places, PLEASE!
-
Wireshark is version 3, MySensors 2.3.1 released 2018. nrf24 protocol with old dll is not working. Cost me hours tot find out it is "Oude Meuk", and not working with Wireshark error message "dissector not found". Please @Hek and @Yveaux release working version or wipe it from the forum at many places, PLEASE!
@tonbor said in Wireless nRF24L01+ sniffer for MySensors:
Wireshark is version 3, MySensors 2.3.1 released 2018. nrf24 protocol with old dll is not working. Cost me hours tot find out it is "Oude Meuk", and not working with Wireshark error message "dissector not found".
MySensors protocol support for 1.x and 2.x is included. The protocol 2.x hasn't changed for 2.3.1
The wireshark version referenced from the blog (1.10.8) still works with the included dlls. The Wireshark devs make it nearly impossible to create a dissector that compiles with newer versions as the wireshark api keeps changing.This 'oude meuk' is still working as released.
-
@tonbor said in Wireless nRF24L01+ sniffer for MySensors:
Wireshark is version 3, MySensors 2.3.1 released 2018. nrf24 protocol with old dll is not working. Cost me hours tot find out it is "Oude Meuk", and not working with Wireshark error message "dissector not found".
MySensors protocol support for 1.x and 2.x is included. The protocol 2.x hasn't changed for 2.3.1
The wireshark version referenced from the blog (1.10.8) still works with the included dlls. The Wireshark devs make it nearly impossible to create a dissector that compiles with newer versions as the wireshark api keeps changing.This 'oude meuk' is still working as released.
@yveaux Well this is your description: "Installation As you can see in the description above, the console application and Wireshark dissectors are currently only available for Windows (anyone who volunteers to port them to Linux and/or Mac, please do so and let me know). In the description below I assume you've already downloaded and installed: Wireshark - I used 1.10.8, either 32- or 64-bits"
Well I suppose you meant it is only working with Wireshark - 1.10.8, that's really only using "Oude Meuk" Sorry I wasted my time, and I see too late more people did.
-
@yveaux Well this is your description: "Installation As you can see in the description above, the console application and Wireshark dissectors are currently only available for Windows (anyone who volunteers to port them to Linux and/or Mac, please do so and let me know). In the description below I assume you've already downloaded and installed: Wireshark - I used 1.10.8, either 32- or 64-bits"
Well I suppose you meant it is only working with Wireshark - 1.10.8, that's really only using "Oude Meuk" Sorry I wasted my time, and I see too late more people did.
@tonbor you’ve been a member here long enough to know that this forum is a place for people helping eachother.
I understand that you are frustrated, but if everyone in a diy community who ever got frustrated were to get angry on the other people who tried to help, the world would be full with angry people.
-
https://www.filepuma.com/download/wireshark_64bit_1.10.8-6009/download/
with a little help from my friends ……..:relaxed: :helmet_with_white_cross: -
Hi, I have the sniffer and wireshark running to capture a 256kbps MySensors 2.3.1 network which is part of a working home automation setup. It does capture some packets over a test period of a few minutes but the sniffer program (in verbose mode) reports it is missing several thousand packets. Also, the hundred or so packets that it has captured appear unintelligible in wireshark. Can anyone tell me what parameters I should be using when I start the nrf24sniffer program please ? I think I have some parameters incorrectly set. Many thanks for any advice you can offer.
-
Hi, I have the sniffer and wireshark running to capture a 256kbps MySensors 2.3.1 network which is part of a working home automation setup. It does capture some packets over a test period of a few minutes but the sniffer program (in verbose mode) reports it is missing several thousand packets. Also, the hundred or so packets that it has captured appear unintelligible in wireshark. Can anyone tell me what parameters I should be using when I start the nrf24sniffer program please ? I think I have some parameters incorrectly set. Many thanks for any advice you can offer.
@apharvey99 said in Wireless nRF24L01+ sniffer for MySensors:
... but the sniffer program (in verbose mode) reports it is missing several thousand packets.
What message do you get? The one in https://github.com/Yveaux/NRF24_Sniffer/blob/master/SerialToPipe/src/Nrf24Sniff/Nrf24Sniff.cpp#L445 ?
If you see packets coming in the nRF24 at least detects the packets on air.
What parameters do you use in your setup, and when calling the Nrf24Sniff executable?
Did you compile the binaries yourself or used precompiled ones?
Did you #define BINARY_OUTPUT in the Arduino sketch?I really need more input to be able to help...
-
@apharvey99 said in Wireless nRF24L01+ sniffer for MySensors:
... but the sniffer program (in verbose mode) reports it is missing several thousand packets.
What message do you get? The one in https://github.com/Yveaux/NRF24_Sniffer/blob/master/SerialToPipe/src/Nrf24Sniff/Nrf24Sniff.cpp#L445 ?
If you see packets coming in the nRF24 at least detects the packets on air.
What parameters do you use in your setup, and when calling the Nrf24Sniff executable?
Did you compile the binaries yourself or used precompiled ones?
Did you #define BINARY_OUTPUT in the Arduino sketch?I really need more input to be able to help...
@Yveaux Hi, thanks for your reply. Sorry I didn’t provide more information at first. I do have Binary output defined in the nrf24sniff Arduino sketch.
I have rerun the data collection and the screenshot below shows my nrf24sniff startup parameters, the output I get from nrf24sniff and the output from Wireshark. As you can see, in wireshark even the source and destination address of the MySensors 2.3.1 packets are not visible, neither is the payload.
I don’t fully understand what I’m doing with this but am trying to follow your very helpful instructions to be able to view the nrf24 data packets that my home automation system is clearly sending as it is working fine. I am obviously doing something wrong so your help would be very welcome. Thank you.
-
@Yveaux Hi, thanks for your reply. Sorry I didn’t provide more information at first. I do have Binary output defined in the nrf24sniff Arduino sketch.
I have rerun the data collection and the screenshot below shows my nrf24sniff startup parameters, the output I get from nrf24sniff and the output from Wireshark. As you can see, in wireshark even the source and destination address of the MySensors 2.3.1 packets are not visible, neither is the payload.
I don’t fully understand what I’m doing with this but am trying to follow your very helpful instructions to be able to view the nrf24 data packets that my home automation system is clearly sending as it is working fine. I am obviously doing something wrong so your help would be very welcome. Thank you.
@apharvey99 From the Wireshark capture you can see the packets coming in at an extremely high rate. Also the packet data is all zeroes, except for the node address.
You say you are monitoring your home automation system. Is it a MySensors network? -
@apharvey99 From the Wireshark capture you can see the packets coming in at an extremely high rate. Also the packet data is all zeroes, except for the node address.
You say you are monitoring your home automation system. Is it a MySensors network?@Yveaux Hi, yes it is a mysensors 2.3.1 network using NRF24L01’s and is a PiHome donestic heating control system installation. It is configured in MySensors to use channel 91. The PiHome system is working normally with all nodes connected and monitored by the PiHome gateway. I am unable to monitor the packets by capturing them with NRF24sniffer and Wireshark. PiHome on Github has all the node sketches used. I also don’t understand why nrf24sniffer reports so many lost packets, there aren’t all that many packets sent by piHome as the temperature sensors only send an update once a minute or so and the zone controller data traffic is only a few packets every minute. The sniffer is showing many hundreds of packets every minute and none of them have any content. I am puzzled but must have something wrong in my sniffer setup somewhere.
-
@Yveaux Hi, yes it is a mysensors 2.3.1 network using NRF24L01’s and is a PiHome donestic heating control system installation. It is configured in MySensors to use channel 91. The PiHome system is working normally with all nodes connected and monitored by the PiHome gateway. I am unable to monitor the packets by capturing them with NRF24sniffer and Wireshark. PiHome on Github has all the node sketches used. I also don’t understand why nrf24sniffer reports so many lost packets, there aren’t all that many packets sent by piHome as the temperature sensors only send an update once a minute or so and the zone controller data traffic is only a few packets every minute. The sniffer is showing many hundreds of packets every minute and none of them have any content. I am puzzled but must have something wrong in my sniffer setup somewhere.
-
@apharvey99 did you connect the IRQ line between radio and arduino?
