Navigation

    • Register
    • Login
    • OpenHardware.io
    • Categories
    • Recent
    • Tags
    • Popular
    1. Home
    2. joaoabs
    3. Topics
    • Profile
    • Following
    • Followers
    • Topics
    • Posts
    • Best
    • Groups

    Topics created by joaoabs

    • joaoabs

      Is it possible to request sensor status (via MQTT)?
      Troubleshooting • • joaoabs  

      2
      0
      Votes
      2
      Posts
      58
      Views

      BearWithBeard

      "Usually" is the correct term. You can request whatever you want using MQTT, but you need to handle the response manually inside the receive() function. This isn't an automatic internal process like the echo or ack response. void receive(const MyMessage &message) { if (message.getCommand() == C_REQ) { switch (message.getSensor()) { case 10: // Send SSR 1 state break; case 11: // Send SSR 2 state break; case 20: // Send temperature sensor value break; case 40: // Send humidity sensor value break; default: break; } } } Note: It's best to not send a message from within receive() as it can cause all sorts of weird stuff, including recursive loops. Preferably, you'd set a flag and handle everything else in the main loop.
    • joaoabs

      Soldering a coax cable to RFM69
      My Project • • joaoabs  

      2
      0
      Votes
      2
      Posts
      31
      Views

      mfalkvidd

      @joaoabs yes that looks fine. Keep the non-shielded part of the cable as short as possible, but you’ve already done a great job so I think it would be hard to make it shorter. Personally I would probably have chosen to solder a pigtail (with sma contact) to the rfm module, to make it possible to switch to a different antenna/coax cable without soldering. But each connector introduces loss, so soldering might be the best choice.
    • joaoabs

      Can a node request a status from other node?
      Feature Requests • • joaoabs  

      3
      0
      Votes
      3
      Posts
      41
      Views

      BearWithBeard

      While it would be possible via request() as @mfalkvidd suggests, I wouldn't recommend to do that in this case. I think it's rather pointless to regularly request variables which only change rarely. It adds a lot of traffic to the network - at least 4 messages (including echos) per request - while the requested values stay unchanged 98% of the time or so. Not to mention that the status LEDs could show a wrong condition for up to 10 minutes if you toggle a light switch right after its state has been requested. I'd suggest to use one of the following alternatives instead: You could have the light nodes send messages to both the gateway and the node with the status LEDs. The status LEDs would update immediately when a light is toggled and there's a lot less unnecessary traffic on the network. Let the controller handle the logic. Whenever a light node sends a state change to the gateway, tell the controller to send a message to the node with the status LEDs. This method has the same benefits as the one before and it's easier maintainable since you don't need to re-upload sketches to multiple nodes if something changes - just reconfigure a script in your controller.
    • joaoabs

      Can't receive parent answer
      Troubleshooting • • joaoabs  

      4
      0
      Votes
      4
      Posts
      37
      Views

      frits

      @joaoabs said in Can't receive parent answer: Maybe the slim node page could have some reference to this? I totally agree, the IRQ line should be routed, also for nrf24 modules. Could you propose this in the slimnode maker's thread?
    • joaoabs

      How to req actuator status?
      Troubleshooting • • joaoabs  

      2
      0
      Votes
      2
      Posts
      29
      Views

      frits

      might be related to that thread: https://forum.mysensors.org/topic/11427
    • joaoabs

      Anyone using Slimnode (RFM69) with MySensors 2.3.2?
      Troubleshooting • • joaoabs  

      8
      0
      Votes
      8
      Posts
      58
      Views

      joaoabs

      After much tentative-error, found a working setup. The drawback is that the node cannot be more that 4m away from the gateway in order to communication flow normally. Could this be bad quality RFM69's? I mean, isn't supposed that 433MHz range would be higher than this? I was expecting it to cross walls and so... The Slim node is currently powered by a USB/serial adapter (not battery) connected to the laptop so it shouldn't be a low power issue. All nrf2rfm69 modules have a bought 433MHz spiral antenna (like the picture), including the GW and I have also soldered a 10uF SMD tantalum capacitor (smd code 106A) in the back side.
    • joaoabs

      RFM69(HW) 433Mhz interference with other home devices?
      Troubleshooting • • joaoabs  

      4
      0
      Votes
      4
      Posts
      38
      Views

      joaoabs

      Well, After removing some counters cycles on a node, I can state I have the MySensors GW working non-stop for 24h now with 2 nodes without any noticeable issue. Both nodes are using Encryption and Signing. The nodes are simply reporting temperature and Humidity every minute or so. Will try now the behavior with actuator nodes (relay). In the log I can see it isn't perfect yet. There are quite a few signing failures. The node #80 is 6 meters away from the gateway with line-of-sight, which concerns me a bit because when I place the nodes in the final locations, I'm sure the radio path will not be better than this. I'm assuming that the signing is failing due to radio issues - I might be wrong. Dec 03 17:46:12 DEBUG TSF:MSG:READ,80-80-0,s=20,c=1,t=0,pt=7,l=5,sg=1:14.0 Dec 03 17:46:12 DEBUG SGN:BND:NONCE=326B170BBDFD3CE66C91DE485E2C465D98434C6917C4D7269DAAAAAAAAAAAAAA Dec 03 17:46:12 DEBUG SGN:BND:HMAC=602409810E55FA10445022FEECCB08697878B9F0FD1652B9303FF9D543B240FD Dec 03 17:46:12 DEBUG SGN:VER:OK Dec 03 17:46:12 DEBUG GWT:TPS:TOPIC=mysensors-out/80/20/1/0/0,MSG SENT Dec 03 17:46:13 DEBUG TSF:MSG:READ,80-80-0,s=40,c=3,t=16,pt=0,l=0,sg=1: Dec 03 17:46:13 DEBUG SGN:SKP:MSG CMD=3,TYPE=16 Dec 03 17:46:13 DEBUG SGN:SKP:MSG CMD=3,TYPE=17 Dec 03 17:46:13 DEBUG TSF:MSG:SEND,0-0-80-80,s=255,c=3,t=17,pt=6,l=25,sg=1,ft=0,st=OK:<NONCE> Dec 03 17:46:13 DEBUG SGN:NCE:XMT,TO=0 Dec 03 17:46:13 DEBUG TSF:MSG:READ,80-80-0,s=40,c=1,t=1,pt=7,l=5,sg=1:63.0 Dec 03 17:46:13 DEBUG SGN:BND:NONCE=854FF116C7AA8566A8176AAA1A319BE95D90D8417AA92EDB3EAAAAAAAAAAAAAA Dec 03 17:46:13 DEBUG SGN:BND:HMAC=C54BAC9E3FE050E9170CEE17AB23836A98EA270ADFC089A4523E27610D587E88 Dec 03 17:46:13 DEBUG SGN:VER:OK Dec 03 17:46:13 DEBUG GWT:TPS:TOPIC=mysensors-out/80/40/1/0/1,MSG SENT Dec 03 17:46:14 DEBUG TSF:MSG:READ,80-80-0,s=21,c=3,t=16,pt=0,l=0,sg=1: Dec 03 17:46:14 DEBUG SGN:SKP:MSG CMD=3,TYPE=16 Dec 03 17:46:14 DEBUG SGN:SKP:MSG CMD=3,TYPE=17 Dec 03 17:46:14 DEBUG TSF:MSG:SEND,0-0-80-80,s=255,c=3,t=17,pt=6,l=25,sg=1,ft=0,st=OK:<NONCE> Dec 03 17:46:14 DEBUG SGN:NCE:XMT,TO=0 Dec 03 17:46:14 DEBUG TSF:MSG:READ,80-80-0,s=21,c=1,t=0,pt=7,l=5,sg=1:8.0 Dec 03 17:46:14 DEBUG SGN:BND:NONCE=BA1DABAF567A20CEABF5CFC35D638E7A1A3E5CF94204D96935AAAAAAAAAAAAAA Dec 03 17:46:14 DEBUG SGN:BND:HMAC=8735CDA75D1148784B3D73601E7A4199DB44CFD039C75584EBA9ADD24897355A Dec 03 17:46:14 DEBUG SGN:VER:OK Dec 03 17:46:14 DEBUG GWT:TPS:TOPIC=mysensors-out/80/21/1/0/0,MSG SENT Dec 03 17:47:15 DEBUG TSF:MSG:READ,80-80-0,s=20,c=3,t=16,pt=0,l=0,sg=1: Dec 03 17:47:15 DEBUG SGN:SKP:MSG CMD=3,TYPE=16 Dec 03 17:47:15 DEBUG SGN:SKP:MSG CMD=3,TYPE=17 Dec 03 17:47:16 DEBUG TSF:MSG:SEND,0-0-80-80,s=255,c=3,t=17,pt=6,l=25,sg=1,ft=0,st=OK:<NONCE> Dec 03 17:47:16 DEBUG SGN:NCE:XMT,TO=0 Dec 03 17:47:16 DEBUG TSF:MSG:READ,80-80-0,s=20,c=1,t=0,pt=7,l=5,sg=1:14.0 Dec 03 17:47:16 DEBUG SGN:BND:NONCE=EF0F98582847EC766BDBC6FB13B7920FCB68CA984C600DA0FBAAAAAAAAAAAAAA Dec 03 17:47:16 DEBUG SGN:BND:HMAC=7AB74FA813953F8965393306FFF67FCA429DCE7F293E08357B9AAE4B0D33C5C1 Dec 03 17:47:16 DEBUG SGN:VER:OK Dec 03 17:47:16 DEBUG GWT:TPS:TOPIC=mysensors-out/80/20/1/0/0,MSG SENT Dec 03 17:47:17 DEBUG TSF:MSG:READ,80-80-0,s=20,c=1,t=0,pt=7,l=5,sg=1:14.0 Dec 03 17:47:17 DEBUG !SGN:BND:VER ONGOING Dec 03 17:47:17 DEBUG !SGN:VER:FAIL Dec 03 17:47:17 DEBUG !TSF:MSG:SIGN VERIFY FAIL Dec 03 17:47:17 DEBUG TSF:MSG:READ,80-80-0,s=20,c=1,t=0,pt=7,l=5,sg=1:14.0 Dec 03 17:47:17 DEBUG !SGN:BND:VER ONGOING Dec 03 17:47:17 DEBUG !SGN:VER:FAIL Dec 03 17:47:17 DEBUG !TSF:MSG:SIGN VERIFY FAIL Dec 03 17:47:18 DEBUG TSF:MSG:READ,80-80-0,s=20,c=1,t=0,pt=7,l=5,sg=1:14.0 Dec 03 17:47:18 DEBUG !SGN:BND:VER ONGOING Dec 03 17:47:18 DEBUG !SGN:VER:FAIL Dec 03 17:47:18 DEBUG !TSF:MSG:SIGN VERIFY FAIL We can see in the log that the same node/child have both successful signing as well as failed signing. This signature failure isn't critical for temp/Humidity readings (even if it fails now, it will be fine in the next round), but for actuator nodes (where you really want something to be turned on/off) it will be a concern. I haven't noticed any other 433MHz interference (but only used the garage remote a couple of times during the day). It can be that a buggy node sketch makes the RFM69 unstable and jams the frequency. One of the side effects is that there are no entries in the GW log and therefore it seems is it down. Well, something to take into consideration when coding the nodes. My 2 cents
    • joaoabs

      RPI GW - Including build flags somewhere for future reference
      Feature Requests • • joaoabs  

      6
      3
      Votes
      6
      Posts
      62
      Views

      monte

      @mfalkvidd not necessary. We already have #define MY_GATEWAY_LINUX, so just #ifdef MY_GATEWAY_LINUX to define those constants in runtime at the init stage. As I see it, only SPI driver needs to be defined at compilation, other options could easily be set via config.
    • joaoabs

      [solved] Rebuilding a RPI GW - What do I need to get signing working again?
      Troubleshooting • • joaoabs  

      4
      0
      Votes
      4
      Posts
      40
      Views

      joaoabs

      Hi, Got it working! It was a strange mix of RFM69/RFM69HW devices (all soldered into the nrf2rfm69 board - so couldn't tell which type it was) and also a faulty RFM69. Also, it seems the signing consumes much processing power (and memory) to the little at328 chips. A sketch with more than 65% memory usage may fail some signatures, so not recommended to put many functionalities in the same node, specially when running my_debug. Simple sketches just with a sht21 sensor are working fine with signing and RFM69 encryption. Copying the correct HMAC, soft-serial and AES to the mysensors.conf file and with RPI reboots after each config/make/makeinstall cycle solved the problem. Thanks, Joaoabs
    • joaoabs

      Error compiling for RPI4 64 bit: RFM69_MAX_PACKET_LEN
      Troubleshooting • • joaoabs  

      2
      0
      Votes
      2
      Posts
      16
      Views

      mfalkvidd

      @joaoabs said in Error compiling for RPI4 64 bit: RFM69_MAX_PACKET_LEN: Maybe MySensors isn't yet ready for 64bit It won’t be until someone wants it badly enough, and has the time and skills to do whatever is needed. You seem to have made some progress. Hopefully you or someone else can figure out how to proceed.
    • joaoabs

      Is MySensors RPI GW 32bit only?
      Troubleshooting • • joaoabs  

      12
      0
      Votes
      12
      Posts
      186
      Views

      suspendfunction

      Anyone tried this with RFM69HCW? I got it compiled on Arch Linux ARM with the aarch64 linux-rpi kernel after editing ./configure and hal/transport/RFM69/driver/new/RFM69_new.h as described above. [root@alarm git]# cat /proc/cpuinfo | grep Model && uname -a Model : Raspberry Pi 4 Model B Rev 1.4 Linux netberry 6.1.11-2-rpi-ARCH #1 SMP PREEMPT Tue Feb 14 06:34:59 MST 2023 aarch64 GNU/Linux It runs, but doesn't communicate with the radio properly: [root@alarm MySensors]# ./bin/mysgw Feb 16 13:20:45 INFO Starting gateway... Feb 16 13:20:45 INFO Protocol version - 2.4.0-alpha Feb 16 13:20:45 DEBUG MCO:BGN:INIT GW,CP=RPNGL---,FQ=NA,REL=1,VER=2.4.0-alpha Feb 16 13:20:45 DEBUG TSF:LRT:OK Feb 16 13:20:45 DEBUG TSM:INIT Feb 16 13:20:45 DEBUG TSF:WUR:MS=0 Feb 16 13:20:45 DEBUG RFM69:INIT Feb 16 13:20:45 DEBUG RFM69:INIT:PIN,CS=24,IQP=22,IQN=25 Feb 16 13:20:45 DEBUG RFM69:PTX:LEVEL=5 dBm Feb 16 13:20:45 DEBUG RFM69:DUMP:Registers Address | HEX value Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x01 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x02 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x03 Value=0x1a Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x04 Value=0x0b Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x05 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x06 Value=0x52 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x07 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x08 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x09 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x0a Value=0x01 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x0b Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x0c Value=0x02 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x0d Value=0x92 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x0e Value=0xf5 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x0f Value=0x20 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x10 Value=0x24 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x11 Value=0x9f Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x12 Value=0x09 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x13 Value=0x1a Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x14 Value=0x40 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x15 Value=0xb0 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x16 Value=0x7b Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x17 Value=0x9b Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x18 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x19 Value=0x86 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x1a Value=0x8a Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x1b Value=0x40 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x1c Value=0x80 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x1d Value=0x06 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x1e Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x1f Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x20 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x21 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x22 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x23 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x24 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x25 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x26 Value=0x05 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x27 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x28 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x29 Value=0xff Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x2a Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x2b Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x2c Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x2d Value=0x03 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x2e Value=0x98 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x2f Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x30 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x31 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x32 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x33 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x34 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x35 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x36 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x37 Value=0x10 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x38 Value=0x40 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x39 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x3a Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x3b Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x3c Value=0x0f Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x3d Value=0x02 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x3e Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x3f Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x40 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x41 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x42 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x43 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x44 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x45 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x46 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x47 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x48 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x49 Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x4a Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x4b Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x4c Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x4d Value=0x00 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x4e Value=0x01 Feb 16 13:20:45 DEBUG RFM69:DUMP:REG=0x4f Value=0x00 Feb 16 13:20:45 DEBUG !RFM69:INIT:SANCHK FAIL Feb 16 13:20:45 DEBUG !TSM:INIT:TSP FAIL Feb 16 13:20:45 DEBUG TSM:FAIL:CNT=1 Feb 16 13:20:45 DEBUG TSM:FAIL:DIS Feb 16 13:20:45 DEBUG TSF:TDI:TSL Feb 16 13:20:45 DEBUG RFM69:RSL I have built commit aa520cea, the latest from the development branch, using this config: ./configure --my-gateway=ethernet --my-transport=rfm69 --my-is-rfm69hw --my-rfm69-frequency=868 --extra-cxxflags="-DMY_DEBUG_VERBOSE_RFM69 -DMY_DEBUG_VERBOSE_RFM69_REGISTERS" My hardware should be fine, i didn't change anything and it was working with the 32-bit kernel before.
    • joaoabs

      Node personalizer sketch seems broken in MySensors 2.3.1
      Bug Reports • • joaoabs  

      3
      0
      Votes
      3
      Posts
      598
      Views

      tekka

      Bingo! This is a backwards incompatibility - thanks for reporting! @joaoabs You should be able to fix this by using the SecurityPersonalizer example from the 2.3.1 lib and copy/paste the settings section from your current sketch to the example sketch. @Anticimex issue originates from replacing all signerSHA256xyz() functions in the cryptoHAL
    • joaoabs

      Check Uplink fails - Using RFM69 with signing and encryption
      Troubleshooting • • joaoabs  

      2
      0
      Votes
      2
      Posts
      463
      Views

      joaoabs

      Doing further investigation, still no sucess.... Got the logs from the working node, based on Sensebender and everything seems fine. Changed the radios, still the same problem. Took the basic relay example from my sensors and just added my radio/signing stuff: Still the same problem. The code doesn't even reach setup() function, so it must be something on the MySensors initialization, but if that was the case, why does it work fine with the Sensebender micro? Any idea? How common is it in mysensors community to have RFM69's with HW signing and encryption? __ __ ____ | \/ |_ _/ ___| ___ _ __ ___ ___ _ __ ___ | |\/| | | | \___ \ / _ \ `_ \/ __|/ _ \| `__/ __| | | | | |_| |___| | __/ | | \__ \ _ | | \__ \ |_| |_|\__, |____/ \___|_| |_|___/\___/|_| |___/ |___/ 2.3.1 16 MCO:BGN:INIT NODE,CP=RPNNAA-X,REL=255,VER=2.3.1 67 TSM:INIT 69 TSF:WUR:MS=0 71 TSM:INIT:TSP OK 73 TSM:INIT:STATID=50 75 TSF:SID:OK,ID=50 77 TSM:FPAR 88 TSF:MSG:SEND,50-50-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK: 1017 TSF:MSG:READ,0-0-50,s=255,c=3,t=8,pt=1,l=1,sg=1:0 1024 TSF:MSG:FPAR OK,ID=0,D=1 2097 TSM:FPAR:OK 2097 TSM:ID 2099 TSM:ID:OK 2101 TSM:UPL 2119 TSF:MSG:SEND,50-50-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=0,st=OK:1 2340 TSF:MSG:READ,0-0-50,s=255,c=3,t=25,pt=1,l=1,sg=1:1 2347 TSF:MSG:PONG RECV,HP=1 2351 TSM:UPL:OK 2353 TSM:READY:ID=50,PAR=0,DIS=1 2367 TSF:MSG:SEND,50-50-0-0,s=255,c=3,t=15,pt=6,l=2,sg=0,ft=0,st=OK:0101 2580 TSF:MSG:READ,0-0-50,s=255,c=3,t=15,pt=6,l=2,sg=0:0101 2607 TSF:MSG:SEND,50-50-0-0,s=255,c=3,t=16,pt=0,l=0,sg=0,ft=0,st=OK: 2824 TSF:MSG:READ,0-0-50,s=255,c=3,t=17,pt=6,l=25,sg=0:<NONCE> 2955 TSF:MSG:SEND,50-50-0-0,s=255,c=0,t=17,pt=0,l=5,sg=1,ft=0,st=OK:2.3.1 2981 TSF:MSG:SEND,50-50-0-0,s=255,c=3,t=16,pt=0,l=0,sg=1,ft=0,st=OK: 3198 TSF:MSG:READ,0-0-50,s=255,c=3,t=17,pt=6,l=25,sg=1:<NONCE> 3342 TSF:MSG:SEND,50-50-0-0,s=255,c=3,t=6,pt=1,l=1,sg=1,ft=0,st=OK:0 3379 TSF:MSG:READ,0-0-50,s=255,c=3,t=16,pt=0,l=0,sg=1: 3684 TSF:MSG:SEND,50-50-0-0,s=255,c=3,t=17,pt=6,l=25,sg=1,ft=0,st=OK:<NONCE> 3713 TSF:MSG:READ,0-0-50,s=255,c=3,t=6,pt=0,l=1,sg=1:M 3862 TSF:MSG:SEND,50-50-0-0,s=255,c=3,t=16,pt=0,l=0,sg=1,ft=0,st=OK: 4098 TSF:MSG:READ,0-0-50,s=255,c=3,t=17,pt=6,l=25,sg=1:<NONCE> 4732 TSF:MSG:SEND,50-50-0-0,s=255,c=3,t=11,pt=0,l=13,sg=1,ft=0,st=OK:SENSOR JANELA 5261 TSF:MSG:SEND,50-50-0-0,s=255,c=3,t=16,pt=0,l=0,sg=1,ft=0,st=OK: 5543 TSF:MSG:READ,0-0-50,s=255,c=3,t=17,pt=6,l=25,sg=1:<NONCE> 6543 TSF:MSG:SEND,50-50-0-0,s=255,c=3,t=12,pt=0,l=9,sg=1,ft=0,st=OK:JS 2018V1 6774 TSF:MSG:SEND,50-50-0-0,s=20,c=3,t=16,pt=0,l=0,sg=1,ft=0,st=OK: 7067 TSF:MSG:READ,0-0-50,s=255,c=3,t=17,pt=6,l=25,sg=1:<NONCE> 7241 TSF:MSG:SEND,50-50-0-0,s=20,c=0,t=6,pt=0,l=0,sg=1,ft=0,st=OK: 7411 TSF:MSG:SEND,50-50-0-0,s=40,c=3,t=16,pt=0,l=0,sg=1,ft=0,st=OK: 7696 TSF:MSG:READ,0-0-50,s=255,c=3,t=17,pt=6,l=25,sg=1:<NONCE> 8173 TSF:MSG:SEND,50-50-0-0,s=40,c=0,t=7,pt=0,l=0,sg=1,ft=0,st=OK: 8701 TSF:MSG:SEND,50-50-0-0,s=199,c=3,t=16,pt=0,l=0,sg=1,ft=0,st=OK: 9357 TSF:MSG:READ,0-0-50,s=255,c=3,t=17,pt=6,l=25,sg=1:<NONCE> 9549 TSF:MSG:SEND,50-50-0-0,s=199,c=0,t=13,pt=0,l=0,sg=1,ft=0,st=OK: 9617 TSF:MSG:SEND,50-50-0-0,s=30,c=3,t=16,pt=0,l=0,sg=1,ft=0,st=OK: 10022 TSF:MSG:READ,0-0-50,s=255,c=3,t=17,pt=6,l=25,sg=1:<NONCE> 10180 TSF:MSG:SEND,50-50-0-0,s=30,c=0,t=0,pt=0,l=8,sg=1,ft=0,st=OK:Persiana 10188 MCO:REG:REQ 11352 TSF:MSG:SEND,50-50-0-0,s=255,c=3,t=26,pt=1,l=1,sg=1,ft=0,st=OK:2 11737 TSF:MSG:READ,0-0-50,s=255,c=3,t=16,pt=0,l=0,sg=1: 12355 TSF:MSG:SEND,50-50-0-0,s=255,c=3,t=17,pt=6,l=25,sg=1,ft=0,st=OK:<NONCE> 12548 TSF:MSG:READ,0-0-50,s=255,c=3,t=27,pt=1,l=1,sg=1:1 12668 MCO:PIM:NODE REG=1 12670 MCO:BGN:STP isMetric: 1 TempDiff :122.35 HumDiff :150.00 T: 22.35 H: 50 13742 TSF:MSG:SEND,50-50-0-0,s=20,c=3,t=16,pt=0,l=0,sg=1,ft=0,st=OK: 14575 TSF:MSG:READ,0-0-50,s=255,c=3,t=17,pt=6,l=25,sg=1:<NONCE> 14753 TSF:MSG:SEND,50-50-0-0,s=20,c=1,t=0,pt=7,l=5,sg=1,ft=0,st=OK:22.4 14862 TSF:MSG:SEND,50-50-0-0,s=40,c=3,t=16,pt=0,l=0,sg=1,ft=0,st=OK: 15097 TSF:MSG:READ,0-0-50,s=255,c=3,t=17,pt=6,l=25,sg=1:<NONCE> 15362 TSF:MSG:SEND,50-50-0-0,s=40,c=1,t=1,pt=2,l=2,sg=1,ft=0,st=OK:50 TempDiff :0.04 HumDiff :0.50 T: 22.39 H: 51 15511 TSF:MSG:SEND,50-50-0-0,s=20,c=3,t=16,pt=0,l=0,sg=1,ft=0,st=OK: 15804 TSF:MSG:READ,0-0-50,s=255,c=3,t=17,pt=6,l=25,sg=1:<NONCE> 16123 TSF:MSG:SEND,50-50-0-0,s=20,c=1,t=0,pt=7,l=5,sg=1,ft=0,st=OK:22.4 16150 TSF:MSG:SEND,50-50-0-0,s=40,c=3,t=16,pt=0,l=0,sg=1,ft=0,st=OK: 16467 TSF:MSG:READ,0-0-50,s=255,c=3,t=17,pt=6,l=25,sg=1:<NONCE> 16703 TSF:MSG:SEND,50-50-0-0,s=40,c=1,t=1,pt=2,l=2,sg=1,ft=0,st=OK:51 16748 TSF:MSG:SEND,50-50-0-0,s=199,c=3,t=16,pt=0,l=0,sg=1,ft=0,st=OK: 17057 TSF:MSG:READ,0-0-50,s=255,c=3,t=17,pt=6,l=25,sg=1:<NONCE> 17188 TSF:MSG:SEND,50-50-0-0,s=199,c=1,t=38,pt=7,l=5,sg=1,ft=0,st=OK:3.349 17246 TSF:MSG:SEND,50-50-0-0,s=255,c=3,t=16,pt=0,l=0,sg=1,ft=0,st=OK: 17465 TSF:MSG:READ,0-0-50,s=255,c=3,t=17,pt=6,l=25,sg=1:<NONCE> 17772 TSF:MSG:SEND,50-50-0-0,s=255,c=3,t=0,pt=1,l=1,sg=1,ft=0,st=OK:103 17780 MCO:BGN:INIT OK,TSP=1 LOOP 17840 TSF:MSG:SEND,50-50-0-0,s=30,c=3,t=16,pt=0,l=0,sg=1,ft=0,st=OK: 18063 TSF:MSG:READ,0-0-50,s=255,c=3,t=17,pt=6,l=25,sg=1:<NONCE> 18333 TSF:MSG:SEND,50-50-0-0,s=30,c=1,t=16,pt=2,l=2,sg=1,ft=0,st=OK:1 TempDiff :0.06 HumDiff :0.00 18360 MCO:SLP:MS=60000,SMS=0,I1=1,M1=1,I2=255,M2=255 18366 TSF:TDI:TSL 18370 MCO:SLP:WUP=-1 18372 TSF:TRI:TSB LOOP TempDiff :0.72 HumDiff :0.50 T: 21.67 H: 52 18452 TSF:MSG:SEND,50-50-0-0,s=20,c=3,t=16,pt=0,l=0,sg=1,ft=0,st=OK: 18716 TSF:MSG:READ,0-0-50,s=255,c=3,t=17,pt=6,l=25,sg=1:<NONCE> 18962 TSF:MSG:SEND,50-50-0-0,s=20,c=1,t=0,pt=7,l=5,sg=1,ft=0,st=OK:21.7 19048 TSF:MSG:SEND,50-50-0-0,s=40,c=3,t=16,pt=0,l=0,sg=1,ft=0,st=OK: 19286 TSF:MSG:READ,0-0-50,s=255,c=3,t=17,pt=6,l=25,sg=1:<NONCE> 19542 TSF:MSG:SEND,50-50-0-0,s=40,c=1,t=1,pt=2,l=2,sg=1,ft=0,st=OK:52 19550 MCO:SLP:MS=60000,SMS=0,I1=1,M1=1,I2=255,M2=255 19556 TSF:TDI:TSL Gateway: Jan 9 22:34:50 nettemp mysgw: TSF:MSG:READ,50-50-255,s=255,c=3,t=7,pt=0,l=0,sg=0: Jan 9 22:34:50 nettemp mysgw: TSF:MSG:BC Jan 9 22:34:50 nettemp mysgw: TSF:MSG:FPAR REQ,ID=50 Jan 9 22:34:50 nettemp mysgw: TSF:PNG:SEND,TO=0 Jan 9 22:34:50 nettemp mysgw: TSF:CKU:OK Jan 9 22:34:50 nettemp mysgw: TSF:MSG:GWL OK Jan 9 22:34:51 nettemp mysgw: TSF:MSG:SEND,0-0-50-50,s=255,c=3,t=8,pt=1,l=1,sg=1,ft=0,st=OK:0 Jan 9 22:34:52 nettemp mysgw: TSF:MSG:READ,50-50-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1 Jan 9 22:34:53 nettemp mysgw: TSF:MSG:PINGED,ID=50,HP=1 Jan 9 22:34:53 nettemp mysgw: TSF:MSG:SEND,0-0-50-50,s=255,c=3,t=25,pt=1,l=1,sg=1,ft=0,st=OK:1 Jan 9 22:34:53 nettemp mysgw: TSF:MSG:READ,50-50-0,s=255,c=3,t=15,pt=6,l=2,sg=0:0101 Jan 9 22:34:53 nettemp mysgw: TSF:MSG:SEND,0-0-50-50,s=255,c=3,t=15,pt=6,l=2,sg=0,ft=0,st=OK:0101 Jan 9 22:34:53 nettemp mysgw: TSF:MSG:READ,50-50-0,s=255,c=3,t=16,pt=0,l=0,sg=0: Jan 9 22:34:53 nettemp mysgw: TSF:MSG:SEND,0-0-50-50,s=255,c=3,t=17,pt=6,l=25,sg=0,ft=0,st=OK:<NONCE> Jan 9 22:34:53 nettemp mysgw: TSF:MSG:READ,50-50-0,s=255,c=0,t=17,pt=0,l=5,sg=1:2.3.1 Jan 9 22:34:53 nettemp mysgw: TSF:MSG:READ,50-50-0,s=255,c=3,t=16,pt=0,l=0,sg=1: Jan 9 22:34:54 nettemp mysgw: TSF:MSG:SEND,0-0-50-50,s=255,c=3,t=17,pt=6,l=25,sg=1,ft=0,st=OK:<NONCE> Jan 9 22:34:54 nettemp mysgw: TSF:MSG:READ,50-50-0,s=255,c=3,t=6,pt=1,l=1,sg=1:0 Jan 9 22:34:54 nettemp mysgw: GWT:RFC:C=0,MSG=50;255;3;0;6;M Jan 9 22:34:54 nettemp mysgw: TSF:MSG:SEND,0-0-50-50,s=255,c=3,t=16,pt=0,l=0,sg=1,ft=0,st=OK: Jan 9 22:34:54 nettemp mysgw: GWT:RFC:C=0,MSG= Jan 9 22:34:54 nettemp mysgw: TSF:MSG:READ,50-50-0,s=255,c=3,t=17,pt=6,l=25,sg=1:<NONCE> Jan 9 22:34:54 nettemp mysgw: TSF:MSG:SEND,0-0-50-50,s=255,c=3,t=6,pt=0,l=1,sg=1,ft=0,st=OK:M Jan 9 22:34:54 nettemp mysgw: TSF:MSG:READ,50-50-0,s=255,c=3,t=16,pt=0,l=0,sg=1: Jan 9 22:34:55 nettemp mysgw: TSF:MSG:SEND,0-0-50-50,s=255,c=3,t=17,pt=6,l=25,sg=1,ft=0,st=OK:<NONCE> Jan 9 22:34:55 nettemp mysgw: TSF:MSG:READ,50-50-0,s=255,c=3,t=11,pt=0,l=13,sg=1:SENSOR JANELA Jan 9 22:34:56 nettemp mysgw: TSF:MSG:READ,50-50-0,s=255,c=3,t=16,pt=0,l=0,sg=1: Jan 9 22:34:56 nettemp mysgw: TSF:MSG:SEND,0-0-50-50,s=255,c=3,t=17,pt=6,l=25,sg=1,ft=0,st=OK:<NONCE> Jan 9 22:34:57 nettemp mysgw: TSF:MSG:READ,50-50-0,s=255,c=3,t=12,pt=0,l=9,sg=1:JS 2018V1 Jan 9 22:34:57 nettemp mysgw: TSF:MSG:READ,50-50-0,s=255,c=3,t=12,pt=0,l=9,sg=1:JS 2018V1 Jan 9 22:34:57 nettemp mysgw: !TSF:MSG:SIGN VERIFY FAIL Jan 9 22:34:57 nettemp mysgw: TSF:MSG:READ,50-50-0,s=20,c=3,t=16,pt=0,l=0,sg=1: Jan 9 22:34:58 nettemp mysgw: TSF:MSG:SEND,0-0-50-50,s=255,c=3,t=17,pt=6,l=25,sg=1,ft=0,st=OK:<NONCE> Jan 9 22:34:58 nettemp mysgw: TSF:MSG:READ,50-50-0,s=20,c=0,t=6,pt=0,l=0,sg=1: Jan 9 22:34:58 nettemp mysgw: TSF:MSG:READ,50-50-0,s=40,c=3,t=16,pt=0,l=0,sg=1: Jan 9 22:34:58 nettemp mysgw: TSF:MSG:SEND,0-0-50-50,s=255,c=3,t=17,pt=6,l=25,sg=1,ft=0,st=OK:<NONCE> Jan 9 22:34:59 nettemp mysgw: TSF:MSG:READ,50-50-0,s=40,c=0,t=7,pt=0,l=0,sg=1: Jan 9 22:34:59 nettemp mysgw: TSF:MSG:READ,50-50-0,s=199,c=3,t=16,pt=0,l=0,sg=1: Jan 9 22:35:00 nettemp mysgw: TSF:MSG:SEND,0-0-50-50,s=255,c=3,t=17,pt=6,l=25,sg=1,ft=0,st=OK:<NONCE> Jan 9 22:35:00 nettemp mysgw: TSF:MSG:READ,50-50-0,s=199,c=0,t=13,pt=0,l=0,sg=1: Jan 9 22:35:00 nettemp mysgw: TSF:MSG:READ,50-50-0,s=30,c=3,t=16,pt=0,l=0,sg=1: Jan 9 22:35:01 nettemp mysgw: TSF:MSG:SEND,0-0-50-50,s=255,c=3,t=17,pt=6,l=25,sg=1,ft=0,st=OK:<NONCE> Jan 9 22:35:01 nettemp mysgw: TSF:MSG:READ,50-50-0,s=30,c=0,t=0,pt=0,l=8,sg=1:Persiana Jan 9 22:35:01 nettemp mysgw: TSF:MSG:ACK REQ Jan 9 22:35:02 nettemp mysgw: !TSF:MSG:SEND,0-0-50-50,s=30,c=0,t=0,pt=0,l=8,sg=0,ft=0,st=NACK:Persiana Jan 9 22:35:02 nettemp mysgw: TSF:MSG:READ,50-50-0,s=255,c=3,t=26,pt=1,l=1,sg=1:2 Jan 9 22:35:02 nettemp mysgw: TSF:MSG:SEND,0-0-50-50,s=255,c=3,t=16,pt=0,l=0,sg=1,ft=0,st=OK: Jan 9 22:35:03 nettemp mysgw: TSF:MSG:READ,50-50-0,s=255,c=3,t=17,pt=6,l=25,sg=1:<NONCE> Jan 9 22:35:03 nettemp mysgw: TSF:MSG:SEND,0-0-50-50,s=255,c=3,t=27,pt=1,l=1,sg=1,ft=0,st=OK:1 Jan 9 22:35:04 nettemp mysgw: TSF:MSG:READ,50-50-0,s=20,c=3,t=16,pt=0,l=0,sg=1: Jan 9 22:35:05 nettemp mysgw: !TSF:MSG:SEND,0-0-50-50,s=255,c=3,t=17,pt=6,l=25,sg=1,ft=0,st=NACK:<NONCE> Jan 9 22:35:05 nettemp mysgw: TSF:MSG:READ,50-50-0,s=20,c=3,t=16,pt=0,l=0,sg=1: Jan 9 22:35:05 nettemp mysgw: TSF:MSG:SEND,0-0-50-50,s=255,c=3,t=17,pt=6,l=25,sg=1,ft=0,st=OK:<NONCE> Jan 9 22:35:06 nettemp mysgw: TSF:MSG:READ,50-50-0,s=20,c=1,t=0,pt=7,l=5,sg=1:22.4 Jan 9 22:35:06 nettemp mysgw: TSF:MSG:READ,50-50-0,s=40,c=3,t=16,pt=0,l=0,sg=1: Jan 9 22:35:06 nettemp mysgw: TSF:MSG:SEND,0-0-50-50,s=255,c=3,t=17,pt=6,l=25,sg=1,ft=0,st=OK:<NONCE> Jan 9 22:35:06 nettemp mysgw: TSF:MSG:READ,50-50-0,s=40,c=1,t=1,pt=2,l=2,sg=1:50 Jan 9 22:35:06 nettemp mysgw: TSF:MSG:READ,50-50-0,s=20,c=3,t=16,pt=0,l=0,sg=1: Jan 9 22:35:07 nettemp mysgw: TSF:MSG:SEND,0-0-50-50,s=255,c=3,t=17,pt=6,l=25,sg=1,ft=0,st=OK:<NONCE> Jan 9 22:35:07 nettemp mysgw: TSF:MSG:READ,50-50-0,s=20,c=1,t=0,pt=7,l=5,sg=1:22.4 Jan 9 22:35:07 nettemp mysgw: TSF:MSG:READ,50-50-0,s=40,c=3,t=16,pt=0,l=0,sg=1: Jan 9 22:35:07 nettemp mysgw: TSF:MSG:SEND,0-0-50-50,s=255,c=3,t=17,pt=6,l=25,sg=1,ft=0,st=OK:<NONCE> Jan 9 22:35:08 nettemp mysgw: TSF:MSG:READ,50-50-0,s=40,c=1,t=1,pt=2,l=2,sg=1:51 Jan 9 22:35:08 nettemp mysgw: TSF:MSG:READ,50-50-0,s=199,c=3,t=16,pt=0,l=0,sg=1: Jan 9 22:35:08 nettemp mysgw: TSF:MSG:SEND,0-0-50-50,s=255,c=3,t=17,pt=6,l=25,sg=1,ft=0,st=OK:<NONCE> Jan 9 22:35:08 nettemp mysgw: TSF:MSG:READ,50-50-0,s=199,c=1,t=38,pt=7,l=5,sg=1:3.349 Jan 9 22:35:08 nettemp mysgw: TSF:MSG:READ,50-50-0,s=255,c=3,t=16,pt=0,l=0,sg=1: Jan 9 22:35:08 nettemp mysgw: TSF:MSG:SEND,0-0-50-50,s=255,c=3,t=17,pt=6,l=25,sg=1,ft=0,st=OK:<NONCE> Jan 9 22:35:09 nettemp mysgw: TSF:MSG:READ,50-50-0,s=255,c=3,t=0,pt=1,l=1,sg=1:103 Jan 9 22:35:09 nettemp mysgw: TSF:MSG:READ,50-50-0,s=30,c=3,t=16,pt=0,l=0,sg=1: Jan 9 22:35:09 nettemp mysgw: TSF:MSG:SEND,0-0-50-50,s=255,c=3,t=17,pt=6,l=25,sg=1,ft=0,st=OK:<NONCE> Jan 9 22:35:09 nettemp mysgw: TSF:MSG:READ,50-50-0,s=30,c=1,t=16,pt=2,l=2,sg=1:1 Jan 9 22:36:09 nettemp mysgw: TSF:MSG:READ,50-50-0,s=20,c=3,t=16,pt=0,l=0,sg=1: Jan 9 22:36:09 nettemp mysgw: TSF:MSG:SEND,0-0-50-50,s=255,c=3,t=17,pt=6,l=25,sg=1,ft=0,st=OK:<NONCE> Jan 9 22:36:09 nettemp mysgw: TSF:MSG:READ,50-50-0,s=20,c=1,t=0,pt=7,l=5,sg=1:21.7 Jan 9 22:36:10 nettemp mysgw: TSF:MSG:READ,50-50-0,s=40,c=3,t=16,pt=0,l=0,sg=1: Jan 9 22:36:10 nettemp mysgw: TSF:MSG:SEND,0-0-50-50,s=255,c=3,t=17,pt=6,l=25,sg=1,ft=0,st=OK:<NONCE> Jan 9 22:36:10 nettemp mysgw: TSF:MSG:READ,50-50-0,s=40,c=1,t=1,pt=2,l=2,sg=1:52 Jan 9 22:36:28 nettemp mysgw: TSM:READY:NWD REQ Jan 9 22:36:28 nettemp mysgw: TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=OK: Jan 9 22:37:10 nettemp mysgw: TSF:MSG:READ,50-50-0,s=20,c=3,t=16,pt=0,l=0,sg=1: Jan 9 22:37:10 nettemp mysgw: TSF:MSG:SEND,0-0-50-50,s=255,c=3,t=17,pt=6,l=25,sg=1,ft=0,st=OK:<NONCE> Jan 9 22:37:10 nettemp mysgw: TSF:MSG:READ,50-50-0,s=20,c=1,t=0,pt=7,l=5,sg=1:21.2 Jan 9 22:37:10 nettemp mysgw: TSF:MSG:READ,50-50-0,s=40,c=3,t=16,pt=0,l=0,sg=1: Jan 9 22:37:10 nettemp mysgw: TSF:MSG:SEND,0-0-50-50,s=255,c=3,t=17,pt=6,l=25,sg=1,ft=0,st=OK:<NONCE> Jan 9 22:37:10 nettemp mysgw: TSF:MSG:READ,50-50-0,s=40,c=1,t=1,pt=2,l=2,sg=1:54
    • joaoabs

      MySGW 2.3 log hangs frequently in RaspberryPi
      Bug Reports • • joaoabs  

      1
      0
      Votes
      1
      Posts
      491
      Views

      No one has replied

    • joaoabs

      [Solved] RFM69 and RaspberryPI GW
      Troubleshooting • • joaoabs  

      2
      0
      Votes
      2
      Posts
      871
      Views

      joaoabs

      Well, one of the problems when buying from china is that it takes so long to get the stuff that we sometimes forgot what we ordered It seems my RFM69's are in fact RFM69HW (eventhough the chip has a "H"). After reconfiguring the sensebender code and the raspberry configure command accordingly I got dialogue between them! Will now try encryption Update: It seems it's not as simple as just adding the "#define MY_RFM69_ENABLE_ENCRYPTION" in the arduino code and "#define MY_RFM69_ENABLE_ENCRYPTION" in the ./configure command for the RPI GW... Will try to sort it out and if not able to make it work, will open a different thread. Update2: It seems it really is after all. Just needed a reboot, and the signing personalization will be re-used
    • joaoabs

      Antenna for the RFM69
      Hardware • • joaoabs  

      3
      0
      Votes
      3
      Posts
      1070
      Views

      scalz

      @joaoabs said in Antenna for the RFM69: I'll be connecting a single core wire to act as an antenna to the RFM69 module. I could understand that it should be exactly 164.7mm long for 434Mhz. I could also understand that having the most accurate lenght makes all of the difference in the antenna efficiency. Now my question is: Since I'm going to solder it in the RFM69 hole, should I consider a few mm more, for the part that goes through the hole? In other words, is the 164.7mm the size from the PCB surface (and therefore needs a few mm extra to get into the hole), or what matters is having a 164.7mm wire soldered (and having some mm out in the other PCB surface). this exact antenna length is in an ideal world, but it's a good start. There are some points here that can also modify rf performance too https://forum.mysensors.org/post/91880 In short, pcb shape and its gnd size including battery (called the antenna gnd counterpoise, wider for 433mhz), antenna shape, bent or not, can have effects on bandwidth, efficiency etc. when you don't have tools for checking rf, you could empirically experiment by adding/removing few millimeters and see how it affects rssi for example. And better checking it with your node in final setup (in enclosure with battery, as it can also affect perf). This is fine tuning but sometimes depending on the node build it can improve range, then needs less TX power for same job, less TX power = less batt used.. and "greener" RF/less loud
    • joaoabs

      How does the serial GW work after all?
      Troubleshooting • • joaoabs  

      8
      0
      Votes
      8
      Posts
      1005
      Views

      joaoabs

      This is actually strange. Its the same sketch, the difference is just the commented debug flag. With the debug flag off, I reset the GW, wait for the startup and then I reset some nodes in order to force presentation, but all I get is this: 0;255;3;0;14;Gateway startup complete. 0;255;0;0;18;2.2.0 With the debug flag on, I don't even need to reset the nodes, I get "automagically" the communication from my 3 test nodes (4, 10 and 44). 0;255;3;0;9;0 MCO:BGN:INIT GW,CP=RNNGA---,VER=2.2.0 0;255;3;0;9;4 TSM:INIT 0;255;3;0;9;6 TSF:WUR:MS=0 0;255;3;0;9;14 TSM:INIT:TSP OK 0;255;3;0;9;17 TSM:INIT:GW MODE 0;255;3;0;9;20 TSM:READY:ID=0,PAR=0,DIS=0 0;255;3;0;9;23 MCO:REG:NOT NEEDED 0;255;3;0;14;Gateway startup complete. 0;255;0;0;18;2.2.0 0;255;3;0;9;28 MCO:BGN:STP 0;255;3;0;9;34 MCO:BGN:INIT OK,TSP=1 0;255;3;0;9;1915 TSF:MSG:READ,4-4-0,s=1,c=3,t=16,pt=0,l=0,sg=0: 0;255;3;0;9;4982 TSF:MSG:READ,44-44-0,s=3,c=3,t=16,pt=0,l=0,sg=0: 0;255;3;0;9;6920 TSF:MSG:READ,4-4-0,s=2,c=3,t=16,pt=0,l=0,sg=0: 0;255;3;0;9;10014 TSF:MSG:READ,44-44-0,s=4,c=3,t=16,pt=0,l=0,sg=0: 0;255;3;0;9;11924 TSF:MSG:READ,4-4-0,s=70,c=3,t=16,pt=0,l=0,sg=0: 0;255;3;0;9;15047 TSF:MSG:READ,44-44-0,s=30,c=3,t=16,pt=0,l=0,sg=0: 0;255;3;0;9;16928 TSF:MSG:READ,4-4-0,s=71,c=3,t=16,pt=0,l=0,sg=0: 0;255;3;0;9;20079 TSF:MSG:READ,44-44-0,s=31,c=3,t=16,pt=0,l=0,sg=0: 0;255;3;0;9;21932 TSF:MSG:READ,4-4-0,s=10,c=3,t=16,pt=0,l=0,sg=0: 0;255;3;0;9;25122 TSF:MSG:READ,44-44-0,s=70,c=3,t=16,pt=0,l=0,sg=0: 0;255;3;0;9;26937 TSF:MSG:READ,4-4-0,s=50,c=3,t=16,pt=0,l=0,sg=0: 0;255;3;0;9;30155 TSF:MSG:READ,44-44-0,s=10,c=3,t=16,pt=0,l=0,sg=0: 0;255;3;0;9;31941 TSF:MSG:READ,4-4-0,s=60,c=3,t=16,pt=0,l=0,sg=0: 0;255;3;0;9;35186 TSF:MSG:READ,44-44-0,s=255,c=3,t=26,pt=1,l=1,sg=0:2 0;255;3;0;9;35194 TSF:MSG:SEND,0-0-44-44,s=255,c=3,t=27,pt=1,l=1,sg=0,ft=0,st=OK:1 0;255;3;0;9;35217 TSF:MSG:READ,44-44-0,s=30,c=3,t=16,pt=0,l=0,sg=0: 0;255;3;0;9;36947 TSF:MSG:READ,4-4-0,s=255,c=3,t=26,pt=1,l=1,sg=0:2 0;255;3;0;9;36955 TSF:MSG:SEND,0-0-4-4,s=255,c=3,t=27,pt=1,l=1,sg=0,ft=0,st=OK:1 0;255;3;0;9;39106 TSF:MSG:READ,4-4-0,s=70,c=3,t=16,pt=0,l=0,sg=0: 0;255;3;0;9;40248 TSF:MSG:READ,44-44-0,s=31,c=3,t=16,pt=0,l=0,sg=0: 0;255;3;0;9;44111 TSF:MSG:READ,4-4-0,s=71,c=3,t=16,pt=0,l=0,sg=0: 0;255;3;0;9;45270 TSF:MSG:READ,44-44-0,s=70,c=3,t=16,pt=0,l=0,sg=0: 0;255;3;0;9;50302 TSF:MSG:READ,44-44-0,s=70,c=3,t=16,pt=0,l=0,sg=0: 0;255;3;0;9;53968 TSF:MSG:READ,10-10-0,s=30,c=3,t=16,pt=0,l=0,sg=1: 0;255;3;0;9;64184 TSF:MSG:READ,10-10-0,s=30,c=3,t=16,pt=0,l=0,sg=1: 0;255;3;0;9;69276 TSF:MSG:READ,4-4-0,s=10,c=3,t=16,pt=0,l=0,sg=0: 0;255;3;0;9;76290 TSF:MSG:READ,4-4-0,s=60,c=3,t=16,pt=0,l=0,sg=0: 0;255;3;0;9;81298 TSF:MSG:READ,4-4-0,s=50,c=3,t=16,pt=0,l=0,sg=0: What should I see in the serial GW when the debug mode is off? My serial GW code is prety standard, I'd say: /** * The MySensors Arduino library handles the wireless radio link and protocol * between your home built sensors/actuators and HA controller of choice. * The sensors forms a self healing radio network with optional repeaters. Each * repeater and gateway builds a routing tables in EEPROM which keeps track of the * network topology allowing messages to be routed to nodes. * * Created by Henrik Ekblad <henrik.ekblad@mysensors.org> * Copyright (C) 2013-2015 Sensnology AB * Full contributor list: https://github.com/mysensors/Arduino/graphs/contributors * * Documentation: http://www.mysensors.org * Support Forum: http://forum.mysensors.org * * This program is free software; you can redistribute it and/or * modify it under the terms of the GNU General Public License * version 2 as published by the Free Software Foundation. * ******************************* * * DESCRIPTION * The ArduinoGateway prints data received from sensors on the serial link. * The gateway accepts input on serial which will be sent out on radio network. * * The GW code is designed for Arduino Nano 328p / 16MHz * * Wire connections (OPTIONAL): * - Inclusion button should be connected between digital pin 3 and GND * - RX/TX/ERR leds need to be connected between +5V (anode) and digital pin 6/5/4 with resistor 270-330R in a series * * LEDs (OPTIONAL): * - To use the feature, uncomment any of the MY_DEFAULT_xx_LED_PINs * - RX (green) - blink fast on radio message received. In inclusion mode will blink fast only on presentation received * - TX (yellow) - blink fast on radio message transmitted. In inclusion mode will blink slowly * - ERR (red) - fast blink on error during transmission error or receive crc error * */ // Enable debug prints to serial monitor #define MY_DEBUG // Enable and select radio type attached #define MY_RADIO_NRF24 //#define MY_RADIO_NRF5_ESB //#define MY_RADIO_RFM69 //#define MY_RADIO_RFM95 // Set LOW transmit power level as default, if you have an amplified NRF-module and // power your radio separately with a good regulator you can turn up PA level. #define MY_RF24_PA_LEVEL RF24_PA_LOW // Enable serial gateway #define MY_GATEWAY_SERIAL // Define a lower baud rate for Arduinos running on 8 MHz (Arduino Pro Mini 3.3V & SenseBender) #if F_CPU == 8000000L #define MY_BAUD_RATE 38400 #endif // Enable inclusion mode #define MY_INCLUSION_MODE_FEATURE // Enable Inclusion mode button on gateway #define MY_INCLUSION_BUTTON_FEATURE // Inverses behavior of inclusion button (if using external pullup) //#define MY_INCLUSION_BUTTON_EXTERNAL_PULLUP // Set inclusion mode duration (in seconds) #define MY_INCLUSION_MODE_DURATION 180 // Digital pin used for inclusion mode button #define MY_INCLUSION_MODE_BUTTON_PIN 3 // Set blinking period #define MY_DEFAULT_LED_BLINK_PERIOD 300 // Inverses the behavior of leds //#define MY_WITH_LEDS_BLINKING_INVERSE // Flash leds on rx/tx/err // Uncomment to override default HW configurations //#define MY_DEFAULT_ERR_LED_PIN 4 // Error led pin //#define MY_DEFAULT_RX_LED_PIN 6 // Receive led pin //#define MY_DEFAULT_TX_LED_PIN 5 // the PCB, on board LED #include <MySensors.h> void setup() { // Setup locally attached sensors } void presentation() { // Present locally attached sensors } void loop() { // Send locally attached sensor data here } Thanks,
    • joaoabs

      SW_Signing failing: !TSF:MSG:SIGN FAIL
      Troubleshooting • • joaoabs  

      27
      0
      Votes
      27
      Posts
      2541
      Views

      joaoabs

      @tekka What debug flag should I activate for this? When I see the erratic behavior there isn't nothing appearing in the serial console, even with the MY_DEBUG on, so I guess there should be other that is of your interest... Thanks
    • joaoabs

      Eastrom SDM120 with RS485
      Hardware • • joaoabs  

      3
      0
      Votes
      3
      Posts
      1772
      Views

      rejoe2

      @joaoabs If you want to go the "arduino-based" route: There seem to exist already a lot of projects reading this type of meter with a microcontroller e.g. an ESP8266. The code itself seems to be rather simple (assuming, the code provided eg here: https://github.com/reaper7/SDM_Energy_Meter/blob/master/examples/sdm_simple/sdm_simple.ino really works, but there seem to be some more working projects out there). So you may either combine this with normal mysensors-code and just use send commands instead of serial prints (at lower frequency). Could be you'll need a more powerfull mcu than the ATMega32, but most likely a STM32F103 will have enough resources to fullfill this task.
    • joaoabs

      Dual mode for battery powered sensors
      Feature Requests • • joaoabs  

      5
      0
      Votes
      5
      Posts
      2401
      Views

      xydix

      Is there any progress in this area? I guess this is not the same as smart sleep?
    • joaoabs

      Is anyone using senserbender with HC-SR501 PIR ?
      General Discussion • • joaoabs  

      3
      0
      Votes
      3
      Posts
      1636
      Views

      mvader

      yeah i'm running a bunch. connect to the bottom pin on the top left side (basically not the vcc pin on the bottom) it take 3v and works great.
    • joaoabs

      Managing interrupts from several sources
      Development • • joaoabs  

      7
      0
      Votes
      7
      Posts
      3202
      Views

      joaoabs

      Hello, Fresh update: With 5k1 pull-down resistors the reel switches work as expected (with the diode "OR"), so I can keep the original plan and use the MySensors sleep methods. Thanks for that tip! And by the way, is it possible to configure the MySensors interrupts on the rising edge, or is it just limited to change? However, with the PIR (modified to work at 3.3V) the maximum voltage it reaches with a 5k1 pull-down resistor is 2.2V, witch is still not enough to activate the interrupt. I kept increasing the pull-down resistor up to 20k, but then the behaviour gets erratic: It starts activating/deactivating without any sense. Was anyone been able to use a modified HC-SR501 PIR (initial diode and 3.3v voltage regulator bypassed) successfully, or the step up to 5V is really needed? (Its a shame to step up 3.3v to 5v so then step it down again to 3.3v, but if there is no other way...). Anyone willing to share the experience with HC-SR501 PIR's in mysensors framework? Thanks, Joao
    • joaoabs

      Use of ack sending messages
      Development • • joaoabs  

      5
      0
      Votes
      5
      Posts
      5499
      Views

      hek

      The "payoff" is that you know if you need to resend value or not. I would only use it for important values, like when you turn on/off a light or something. Asking for ack on sensor values doesn't give much benefit.
    • joaoabs

      How can I tell if my arduino mini pro is 3.3V or 5v?
      Hardware • • joaoabs  

      11
      0
      Votes
      11
      Posts
      12556
      Views

      NickBuilder

      @Alexandre-Magno Hi! Look here: https://www.arduino.cc/en/Main/ArduinoBoardProMini Check the documentation/schematics section.