Troubleshooting

• 

  Read this first - it could SAVE YOU A LOT OF TIME
  2 Dec 2014, 08:40 • hek   13 Aug 2022, 23:59

  17
  5
  Votes
  17
  Posts
  25.9k
  Views

  13 Aug 2022, 23:59

  @ctodor sorry, I don’t understand. Could you describe where the sensorid could be added?
• 

  DHT22 wrong sensor type in Home Assistant
  9 days ago • Commodoreuno   3 days ago

  7
  0
  Votes
  7
  Posts
  39
  Views

  3 days ago

  I'm glad that worked!
• 

  JSN SR04T - Temperature Influencing Readings
  ultrasonic water level tank • 6 Sept 2019, 07:51 • Timbergetter   21 days ago

  34
  1
  Votes
  34
  Posts
  1.4k
  Views

  21 days ago

  I'm having the same / a simular issue of temperature related readings, but at a different temperature level (for me it must be > 14 degree). I massure the dew point as well (temperature = orange, dew point = yellow). It looks to be more related to water in the air than only to temperature. @zboblamont have you been finally been able to find a solution?
• 

  JSN-SR04T-V3.0 Coax cable extended
  19 Mar 2025, 21:00 • bocalexandru   28 days ago

  2
  0
  Votes
  2
  Posts
  18
  Views

  28 days ago

  Update and problem fixed! For everybody that will encouter this, the problem was at the sensor side because of the folder of the sensor! We created some metal brackets for it and they where exactly the same diameter. The fact that the mount squeezed the sensor made it return the lowest value. Just needed to adjust the hole and everything was ok!
• 

  Ghost Child
  15 Mar 2025, 07:44 • FcNanoLed   18 Mar 2025, 18:36

  12
  0
  Votes
  12
  Posts
  38
  Views

  18 Mar 2025, 18:36

  I want to thank @FcNanoLed. I had long thought about a serial gateway. This would be a way to add I/O to a linux computer. In the process of trying to help, I built up a linux machine running virtual box. In the virtual machine I ran Home Assistant The not well documented part of that was to connect the USB port of the computer to the virtual machine (settings-->USB-->USB Device Filters) (note that one can buy a refurbished PC for about the same price as an equivalently configured RPi) So thanks for the inspiration!
• 

  NODs stop responding, but ping works.
  8 Mar 2025, 19:47 • Marcin   8 Mar 2025, 19:47

  1
  0
  Votes
  1
  Posts
  11
  Views

  No one has replied

• 

  Getting system time from the controller
  27 Feb 2025, 01:39 • dpcons   3 Mar 2025, 01:00

  13
  0
  Votes
  13
  Posts
  55
  Views

  3 Mar 2025, 01:00

  @mfalkvidd Thanks, I'll try that.
• 

  Compiling Sensor code using BME280 and ESP8266
  26 Feb 2025, 00:32 • dpcons   26 Feb 2025, 06:22

  3
  0
  Votes
  3
  Posts
  11
  Views

  26 Feb 2025, 06:22

  Thanks for looking. What arduino ide version are you using and what version of mysensors?
• 

  Echo request is not set
  12 Aug 2024, 15:36 • kamilb85   3 Sept 2024, 08:58

  2
  0
  Votes
  2
  Posts
  17
  Views

  3 Sept 2024, 08:58

  I've found that: char *protocolMyMessage2Serial(const MyMessage &message) { (void)snprintf_P(_fmtBuffer, (uint8_t)MY_GATEWAY_MAX_SEND_LENGTH, PSTR("%" PRIu8 ";%" PRIu8 ";%" PRIu8 ";%" PRIu8 ";%" PRIu8 ";%s\n"), message.getSender(), message.getSensor(), message.getCommand(), message.isEcho(), message.getType(), message.getString(_convBuffer)); return _fmtBuffer; } We put in the print "message.getEcho()", but this isn't echoed message. I think we should put "message.getRequestEcho()" here.
• 

  Forum Search not working?
  4 Oct 2023, 23:33 • Gibber   2 Sept 2024, 20:28

  8
  0
  Votes
  8
  Posts
  58
  Views

  2 Sept 2024, 20:28

  Search not working for me . Firefox browser.
• 

  Can not compile MySensors on esp8266
  24 Aug 2024, 15:35 • TheoL   29 Aug 2024, 20:47

  6
  0
  Votes
  6
  Posts
  22
  Views

  29 Aug 2024, 20:47

  @TheoL there are two pull requests adding support for newer versions. One is guaranteed to break again. One should not break in the future, but will instead break all existing sketches. I’m sure a third option would be welcome if you write the code and submit.
• 

  Raspberry Pi 5: invalid GPIO 9
  27 Aug 2024, 13:20 • igo   27 Aug 2024, 13:20

  1
  1
  Votes
  1
  Posts
  11
  Views

  No one has replied

• 

  Arduino nano and Uno in same My sensors network with NRF24L01+
  26 Jul 2024, 10:30 • DIY89   27 Aug 2024, 09:59

  6
  0
  Votes
  6
  Posts
  37
  Views

  27 Aug 2024, 09:59

  I have mixed Nanos, Pro Minis, ESP8266 and Unos and no problem. I do however have mixed NRF24L01 and NRF24L01+ due to a bad AliExpress saler that stated he sold NRF24L01+ which in fact were not the + version. So I have set my baudrate on all nodes to 1mb. In order to be helpful we need the log on the Uno.
• 

  Some sensors permanently fail after one/two years
  25 Jul 2024, 17:17 • Kokosnoot   25 Jul 2024, 17:17

  1
  1
  Votes
  1
  Posts
  12
  Views

  No one has replied

• 

  This topic is deleted!
  25 Jul 2024, 12:00 • DIY89   25 Jul 2024, 12:00

  1
  0
  Votes
  1
  Posts
  2
  Views

  No one has replied

• 

  This topic is deleted!
  25 Jul 2024, 11:49 • DIY89   25 Jul 2024, 11:49

  1
  0
  Votes
  1
  Posts
  3
  Views

  No one has replied

• 

  Suddenly a Sensor is Missing, not the whole Node. (RPI Eth Gateway, HA)
  3 Jul 2024, 07:20 • se-O-matic   15 Jul 2024, 08:45

  5
  0
  Votes
  5
  Posts
  20
  Views

  15 Jul 2024, 08:45

  No, it does not recover. The Problem is not easy to debug. I now want to build a serial gateway. With that, I am more flexible to test. Maybe to run MySensors on a second raspberry pi with a standard Home Assistant HASS-Os image. Or I check the MySensors network with MyController. At this moment i run the whole system on 64 Bit raspbian, with HA in docker, which is a little bit experimental and i had to fix some lines in the ethernet gateway to compile it for 64 bit. So this is experimental, too.
• 

  Extraneous info in Debug log
  debug log • 28 Jun 2024, 22:42 • Gibber   28 Jun 2024, 22:42

  1
  0
  Votes
  1
  Posts
  9
  Views

  No one has replied

• 

  Help me build a RFM69 gateway using wemos d1 + keyestudio RFM69 shield
  5 Apr 2024, 23:40 • airmedic79   5 Apr 2024, 23:40

  1
  0
  Votes
  1
  Posts
  32
  Views

  No one has replied

• 

  RS485 to custom PCB - comms working, relay not clicking - need helps
  23 Jan 2024, 20:17 • adds666   29 Jan 2024, 13:55

  3
  0
  Votes
  3
  Posts
  23
  Views

  29 Jan 2024, 13:55

  Hi OSD, thanks for your input. Those are the 4 relays on IO-MCU. I buzzed out the circuit and found that I had an open circuit on the 12v line to the relays. Furthermore 2 of the relays indicator LEDs were illuminating, 2 were not. I suspect, when I first juiced up the circuit on this MCU, the 2 relays fired, but I'd made the trace too thin for the required current. I wired up some jumper wire on the reverse of the PCB and the 2 relays started working. The 2 that remain inoperable? https://forum.arduino.cc/t/using-pins-a6-a7-on-pro-mini-compatible/118050 A6 and A7 can only be analogue inputs, cannot be digitally written to..... - so this part of my PCB is now redundant. However, all in all, some good fault finding, found the two issues, and I'm now going away to re-think my PCB trace widths and reading the datasheets more accurately Thanks
• 

  MySensors (HA) having multiple gateways with local sensors
  21 Jan 2024, 18:54 • Willie-wortel   21 Jan 2024, 18:54

  1
  0
  Votes
  1
  Posts
  5
  Views

  No one has replied

• 

  Can not compile on Arduino Nano ESP 32
  25 Nov 2023, 13:11 • ctodor   13 Dec 2023, 14:50

  15
  0
  Votes
  15
  Posts
  75
  Views

  13 Dec 2023, 14:50

  @ctodor You are very welcome
• 

  Gateway stops communicating (again)
  5 Dec 2023, 16:10 • OldSurferDude   6 Dec 2023, 12:45

  2
  0
  Votes
  2
  Posts
  15
  Views

  6 Dec 2023, 12:45

  Hm, maybe the problem is that your rPI has a short interruption in the WIFI connection, the MQTT TCP connection is interrupted and does not autostart again. Maybe there is something in the logs. Maybe you can find something about reconnects in one of these: journalctl --unit=systemd-networkd journalctl --unit=wpa_supplicant You could try to run wpa_cli in daemon mode to react to disconnects and connects. Create a script like this: #!/bin/bash case "$2" in CONNECTED) <your command to start the gateway>; ;; DISCONNECTED) <your command to stop the gateway>; ;; esac then, start wpa_cli in deamon mode: wpa_cli -a /path/to/your/script #use sudo if your gateway commands need sudo If that helps, you could create a service from this command. Regards, Edi
• 

  Radio RFM95 does not send ATmega1284p
  29 Nov 2023, 09:57 • eiten   4 Dec 2023, 09:56

  2
  0
  Votes
  2
  Posts
  16
  Views

  4 Dec 2023, 09:56

  Don't ask me why, but now it works. I changed nothing! Went to my girl over the weekend, coming back, the node was registred. Maybe a jammer went away?
• 

  can't make getStream() work
  30 Aug 2023, 17:25 • Mizar03   28 Nov 2023, 12:17

  2
  0
  Votes
  2
  Posts
  31
  Views

  28 Nov 2023, 12:17

  @Mizar03 sorry for the late response. getStream() only works for firmware transfers. I'd suggest getString(), this should also work for all types of payloads, as they are normaly ASCII and not binary data.
• 

  High power consumption NRF52832 & SI7021
  30 Nov 2020, 17:46 • ncollins   13 Nov 2023, 02:03

  24
  0
  Votes
  24
  Posts
  252
  Views

  13 Nov 2023, 02:03

  I don't know if any of you guys are still around and using this stuff - I moved and am reviving a few of these 51/52 boards that I had built. Prior to moving I had decent luck with all these fixes though I don't quite remember where I was with any of this stuff seeing as it was 3 years ago. I had a few motion sensors and some temp/humd based on these fixes and they were working great, no dips. Not sure any of you will ever see this but hey it all worked.
• 

  Node broadcast loop
  13 Oct 2023, 23:59 • Oumuamua   28 Oct 2023, 17:26

  2
  0
  Votes
  2
  Posts
  24
  Views

  28 Oct 2023, 17:26

  Solved. Issue with power supply. Added a capacidade to power source.
• 

  Sudden battery drain - Pro-mini + RFM69
  rfm69 battery pro mini si7021 • 6 Apr 2023, 10:58 • Oumuamua   13 Oct 2023, 23:49

  10
  0
  Votes
  10
  Posts
  74
  Views

  13 Oct 2023, 23:49

  Hi all, Should anyone face the same problem, I found the root cause: brownout threshold. I burned a new bootloader (Optiboot 8.0) without such trigger and the node has been working with used batteries (~2.7V) since May. Hope this helps.
• 

  Remotes will not connect after latest compile
  6 Oct 2023, 05:08 • Gibber   6 Oct 2023, 17:26

  3
  0
  Votes
  3
  Posts
  15
  Views

  6 Oct 2023, 17:26

  Thanks for the quick response. Yep! When I updated the IDE I forgot to modify the settings (915 MHz) in the new myconfig.h file. Doh! All good now.
• 

  Send 2x relay states to Home Assistant to make them visible?
  19 Sept 2023, 08:56 • Matt   20 Sept 2023, 09:07

  15
  0
  Votes
  15
  Posts
  41
  Views

  20 Sept 2023, 09:07

  @Matt Yes, the landscape there is incredible. Unfortunately, I mostly have to work when I'm there Where are you from?
• 

  Pulse Water Meter, cant see anything
  2 Sept 2023, 22:22 • Thib.   3 Sept 2023, 21:11

  4
  0
  Votes
  4
  Posts
  17
  Views

  3 Sept 2023, 21:11

  Its seems to be working with this last sketch https://github.com/paolo-rendano/MySensors/blob/c01e14d0942de68126d67325a0687b1a6ce4fa16/examples/WaterMeterPulseSensor/WaterMeterPulseSensor.ino need some time to test it thanks
• 

  Compile on arm64 Raspi 3
  26 Aug 2023, 11:27 • moses   3 Sept 2023, 20:28

  5
  0
  Votes
  5
  Posts
  35
  Views

  3 Sept 2023, 20:28

  @monte thanks, did it!
• 

  Termite terminal for RS485
  24 Aug 2023, 00:51 • AGUSTIN   24 Aug 2023, 00:51

  1
  0
  Votes
  1
  Posts
  14
  Views

  No one has replied

• 

  433MHz amplified (>5V)
  21 May 2015, 21:05 • andriej   18 Aug 2023, 09:35

  22
  0
  Votes
  22
  Posts
  11.5k
  Views

  18 Aug 2023, 09:35

  Hi, I create a rflink pcb with this schema . I have an emission issue, the module RF 433Mhz Out not have 12v in VOUT+. What could I need to do. This is the pcb design, maybe it needs some improvement. Thanks
• 

  Help me build a 6-light-sensor & 2 ch relay node.
  29 Jul 2023, 10:33 • airmedic79   30 Jul 2023, 09:21

  3
  0
  Votes
  3
  Posts
  31
  Views

  30 Jul 2023, 09:21

  Only if you send a correct message from the controller to the node the receive function is called. I don't see a receive in your log. I think in your case the receive-function is not called (or called with a wrong message type or node id). Put a serial.print("receive() is called with type "); serial.println(message.getType()); on top of the receive function to see if the receive function is called and which type is handed over..
• 

  Requesting for help building traffic light led module node
  20 Jul 2023, 21:34 • airmedic79   29 Jul 2023, 10:20

  5
  0
  Votes
  5
  Posts
  41
  Views

  29 Jul 2023, 10:20

  I am sharing my sketch. Based on the sketch below, I am using this led light to show air quality status (good for green, normal for yellow and bad for red). This sketch is just a switch so you should make some automation in HA. https://www.amazon.com/Traffic-Display-Module-Arduino-Mini-Traffic/dp/B07SZMRSDN #define MY_DEBUG #define MY_RADIO_RF24 #define MY_NODE_ID 16 #define MY_RF24_PA_LEVEL RF24_PA_LOW #include <MySensors.h> #define CHILD_ID_GREEN 1 #define CHILD_ID_YELLOW 2 #define CHILD_ID_RED 3 #define GREEN_PIN 3 #define YELLOW_PIN 4 #define RED_PIN 5 bool greenState = false; bool yellowState = false; bool redState = false; MyMessage msgGreen(CHILD_ID_GREEN, V_LIGHT); MyMessage msgYellow(CHILD_ID_YELLOW, V_LIGHT); MyMessage msgRed(CHILD_ID_RED, V_LIGHT); void setup() { Serial.begin(115200); pinMode(GREEN_PIN, OUTPUT); pinMode(YELLOW_PIN, OUTPUT); pinMode(RED_PIN, OUTPUT); wait(200); } void presentation() { // Initialize the MySensors communication sendSketchInfo("Traffic Light Node", "1.0"); present(CHILD_ID_GREEN, S_LIGHT); present(CHILD_ID_YELLOW, S_LIGHT); present(CHILD_ID_RED, S_LIGHT); } void loop() { // Send initial values of the LEDs to the controller send(msgGreen.set(greenState ? 1 : 0)); send(msgYellow.set(yellowState ? 1 : 0)); send(msgRed.set(redState ? 1 : 0)); // Other tasks in the loop if needed // ... // Add a delay to control how often the initial values are sent delay(5000); // Send initial values every 5 seconds (adjust as needed) } void receive(const MyMessage &message) { // Check which LED to control based on the message received if (message.sensor == CHILD_ID_GREEN && message.type == V_LIGHT) { greenState = !greenState; // Toggle the state digitalWrite(GREEN_PIN, greenState ? HIGH : LOW); // Set the pin accordingly send(msgGreen.set(greenState ? 1 : 0)); // Report back the new state } else if (message.sensor == CHILD_ID_YELLOW && message.type == V_LIGHT) { yellowState = !yellowState; digitalWrite(YELLOW_PIN, yellowState ? HIGH : LOW); send(msgYellow.set(yellowState ? 1 : 0)); } else if (message.sensor == CHILD_ID_RED && message.type == V_LIGHT) { redState = !redState; digitalWrite(RED_PIN, redState ? HIGH : LOW); send(msgRed.set(redState ? 1 : 0)); } }
• 

  Consistent NACK + RPI Gateway
  15 Jun 2023, 21:13 • Oumuamua   24 Jun 2023, 00:54

  5
  0
  Votes
  5
  Posts
  47
  Views

  24 Jun 2023, 00:54

  Hi all, Should any one need, the fix mentioned in this page actually works. Thanks,
• 

  Error when restarting Homeassistant (mysensors-error)
  11 Jun 2023, 10:24 • Branther   13 Jun 2023, 13:10

  8
  0
  Votes
  8
  Posts
  27
  Views

  13 Jun 2023, 13:10

  thanks again Edi. I will first make a full backup and put it on a new ssd. after that i will test your solutions as far as i can. sorry, i must have overlooked the code snippets function. best regards
• 

  ATMEGA 328 Timer/Counter2 frequency problem
  31 May 2023, 16:44 • monte   2 Jun 2023, 12:14

  2
  0
  Votes
  2
  Posts
  20
  Views

  2 Jun 2023, 12:14

  Hi Monte! May you please post your sketch? Thank you very much, edi
• 

  Lights on after gateway reboot
  31 May 2023, 13:01 • monte   1 Jun 2023, 17:40

  6
  0
  Votes
  6
  Posts
  19
  Views

  1 Jun 2023, 17:40

  If the message is retained, it will show up already when you connect MQTT explorer to the broker, without HA sending a message yet
• 

  MySensor Network on RS485 - only single node visible
  mysensors • 26 Apr 2020, 17:21 • Rysiek   11 May 2023, 12:00

  13
  0
  Votes
  13
  Posts
  150
  Views

  11 May 2023, 12:00

  Very useful topic for me, thanks. Even though it's been a long time, the information was useful to me. And especially the information on the link you sent.
• 

  Unsolved problem with RFM95
  8 May 2023, 03:24 • Diego Andrade 0   8 May 2023, 03:24

  1
  0
  Votes
  1
  Posts
  8
  Views

  No one has replied

• 

  RSSI affects Sleep Timer??
  7 Apr 2023, 22:55 • Gibber   19 Apr 2023, 10:01

  5
  0
  Votes
  5
  Posts
  37
  Views

  19 Apr 2023, 10:01

  thanks for the feedback
• 

  Error sending switch command, check device/hardware !
  10 Dec 2015, 21:54 • Elfnoir   15 Apr 2023, 05:41

  18
  0
  Votes
  18
  Posts
  6.0k
  Views

  15 Apr 2023, 05:41

  Solved by adding a short delay between the RX/TX turnaround when replying with an ACK message. In file MyTransport.cpp at line 706 in the "if (msg.getRequestEcho) block, right after the debug message "TSF:MSG:"ECHO REQ" added a 2ms delay to allow the caller to switch from TX to RX mode. GS
• 

  NRF24 nodes failing to connect on channels below ~100
  6 Apr 2023, 04:29 • GaryStofer   14 Apr 2023, 15:11

  10
  0
  Votes
  10
  Posts
  53
  Views

  14 Apr 2023, 15:11

  @GaryStofer Okay, then sounds like you're doing what I would. Are you able to turn on debug and connect serial to it to troubleshoot that way? Without getting more info on it, I'm out of ideas at the moment.
• 

  How to change the RFM69 Modem configuration?
  13 Apr 2023, 06:02 • Gibber   13 Apr 2023, 17:54

  3
  0
  Votes
  3
  Posts
  20
  Views

  13 Apr 2023, 17:54

  Working great! Thanks very much!
• 

  Error sending switch command, check device/hardware ! ACK problems gateway to node.
  13 Apr 2023, 04:18 • GaryStofer   13 Apr 2023, 04:18

  1
  0
  Votes
  1
  Posts
  12
  Views

  No one has replied

• 

  multiple definition of `premain()' - PlatformIO
  8 Apr 2023, 06:48 • Tom 0   9 Apr 2023, 17:34

  2
  0
  Votes
  2
  Posts
  14
  Views

  9 Apr 2023, 17:34

  Well, search seems to be broken again on the site. Hopefully a dev will see this come across their screen and know how to fix it. I searched the site for "multiple definition" and 'premain' but neither one got ANY hits, even this topic itself! So if you tried to search the site to see if anyone else had had this problem before, it wouldn't have much chance of success. Anyway, all that is to say that we've run into this before. I'll link below here the thread where I managed to get around it. I'm not sure if there were other threads, but this one should give you some info on how to fix it for yourself. I could find this by going into the history of posts I had made, since search was failing me.... https://forum.mysensors.org/topic/10193/stm32f103c8-problem-at-compilation
• 

  Battery voltage sensor is no longer recognized by Homeassistant
  12 Mar 2023, 08:36 • Branther   28 Mar 2023, 10:27

  10
  0
  Votes
  10
  Posts
  54
  Views

  28 Mar 2023, 10:27

  yes, absolutely. i always order all my components from aliexpress. i don't think it makes any difference which dealer i use there. you can be lucky and sometimes not sometimes you can tell right away, for example an NRF module didn't have an IRQ. sometimes you have to search specifically to get the nrf24l plus model for example, which is different from the normal nrf module. in germany the parts are 3-4 times more expensive. so i put up with it. if you have several components, you can swap them and limit the error. thanks again
• 

  serial nrf24 gateway is rebooting over and over
  17 Mar 2023, 21:54 • bach   19 Mar 2023, 19:26

  3
  0
  Votes
  3
  Posts
  15
  Views

  19 Mar 2023, 19:26

  hi electrick, thank you for the hint, i'm so glad that someone finally talks to me Yes i reached the same conclusion about power supply of the nrf24 board. 3.3V pin from nano can only deliver 50mA when e01-ml01sp4 needs 120mA. I redesigned my project including a ams1117 between nano's 5V pin and the radio board https://forum.mysensors.org/topic/12109/nano-e01-ml01sp4-gateway/4?_=1679247873047 next episode when i'll receive the new pcb !
• 

  STM32F411 BlackpillV2 ST core - problem with reading data from RS485 (HW serial 2)
  14 Mar 2023, 10:36 • thom4s   14 Mar 2023, 19:34

  2
  0
  Votes
  2
  Posts
  17
  Views

  14 Mar 2023, 19:34

  OK problem found. Found out that when I selected "Blackpill F411CE" board before code compilation everything were ok. Usually I am choosing generic types so I used "F411CEUx" in case of blackpill 2 and I found out that generic types has different default "Serial" pins in ST core. Now I can confirm that Bluepill , Blackpill and F4VE board are working with MAX485. ST core v 2.4.0. ../.arduino15/packages/STMicroelectronics/hardware/stm32/2.4.0/variants/STM32F4xx/F411C(C-E)(U-Y)/variant_generic.h // UART Definitions #ifndef SERIAL_UART_INSTANCE #define SERIAL_UART_INSTANCE 2 #endif // Default pin used for generic 'Serial' instance // Mandatory for Firmata #ifndef PIN_SERIAL_RX #define PIN_SERIAL_RX PA3 #endif #ifndef PIN_SERIAL_TX #define PIN_SERIAL_TX PA2 #endif ../.arduino15/packages/STMicroelectronics/hardware/stm32/2.4.0/variants/STM32F4xx/F411C(C-E)(U-Y)/variant_BLACKPILL_F411CE.h // UART Definitions #ifndef SERIAL_UART_INSTANCE #define SERIAL_UART_INSTANCE 1 #endif // Default pin used for generic 'Serial' instance // Mandatory for Firmata #ifndef PIN_SERIAL_RX #define PIN_SERIAL_RX PA10 #endif #ifndef PIN_SERIAL_TX #define PIN_SERIAL_TX PA9 #endif So be carefull while using ST core and generic type of STM32.
• 

  Compiling for STM32F411
  7 Feb 2023, 21:55 • karlheinz2000   26 Feb 2023, 00:51

  3
  0
  Votes
  3
  Posts
  31
  Views

  26 Feb 2023, 00:51

  @karlheinz2000 Sorry I missed your original post. I've used the WhiskyDelta code successfully for gateways using the 401 and 411. Glad you found it.
• 

  Error decoding message from gateway, bad data received
  21 Feb 2023, 17:39 • PCmaniak22   21 Feb 2023, 17:39

  1
  0
  Votes
  1
  Posts
  16
  Views

  No one has replied

• 

  Node is rebooted by waking up from a sleep
  18 Feb 2023, 21:28 • alexsh1   18 Feb 2023, 21:28

  1
  0
  Votes
  1
  Posts
  16
  Views

  No one has replied

• 

  Is MySensors RPI GW 32bit only?
  29 Nov 2020, 23:28 • joaoabs   16 Feb 2023, 14:46

  12
  0
  Votes
  12
  Posts
  183
  Views

  16 Feb 2023, 14:46

  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.
• 

  Debugging without radio messages
  24 Jan 2023, 18:11 • Łukasz T.   25 Jan 2023, 19:33

  2
  0
  Votes
  2
  Posts
  23
  Views

  25 Jan 2023, 19:33

  Yes, comment #define MY_DEBUG and in setup() add Serial.begin(115200);
• 

  ESP32/ESP8266 RS485 gateway - example needed
  8 Sept 2021, 15:44 • Konrad Winiarski   19 Jan 2023, 09:05

  3
  0
  Votes
  3
  Posts
  39
  Views

  19 Jan 2023, 09:05

  Dual Transport (dual bus) Hello Yes a Gateway with several buses or a Node with two different buses would be a good thing. You may have seen the post and the version of @tekka https://forum.mysensors.org/topic/11135/something-s-cooking-in-the-mysensors-labs?_=1674118354490 . maybe not a problem for you "tekka's personal fork from the MySensors 2.4 branch and has not been updated" https://github.com/tekka007/MySensors/tree/UpdateMultiTransport
• 

  New Sense Bender Gateway with no USB response?
  12 Mar 2019, 20:16 • KenKrick   16 Jan 2023, 05:42

  4
  0
  Votes
  4
  Posts
  546
  Views

  16 Jan 2023, 05:42

  @KenKrick - did you ever resolve this? Seeing exactly the same thing on my Sensebender GW.
• 

  MY_TRANSPORT_WAIT_READY_MS does not work
  8 Jan 2023, 16:24 • Bartosz Pawełczyk   8 Jan 2023, 16:24

  1
  0
  Votes
  1
  Posts
  14
  Views

  No one has replied

• 

  mysgw not responding on RS485 data - raspberry pi zero
  21 Sept 2021, 10:54 • Konrad Winiarski   8 Jan 2023, 09:47

  5
  0
  Votes
  5
  Posts
  60
  Views

  8 Jan 2023, 09:47

  Hello @Konrad-Winiarski and best wishes for 2023 if you have time you can tell us more about the architecture you have chosen. the part mysgw (485) : gateway USB? Mqtt : Mosiquitto ! Node Red : flow exemple? yes examples for a small test installation thanks https://forum.mysensors.org/topic/11513/corrupted-data-from-rs485-sensor-node/3
• 

  FindParents on RFM69HW node
  28 Dec 2022, 18:07 • tomvanderputte   30 Dec 2022, 11:48

  3
  1
  Votes
  3
  Posts
  25
  Views

  30 Dec 2022, 11:48

  OK that's embarrassing. It seems I connected interrupt / DIO0 to gnd. But i've reconnected the entire thing several times, including swapping... Anyway thanks for pointing it out. I still get some NACKs and the mqqt is not working anymore for some reason, but I'll figure that out, and do another post if necessary. Thanks for pointing it out!
• 

  Can´t more than 11 Sensors send on my Ardoino over tcp
  26 Dec 2022, 20:50 • StefanH   26 Dec 2022, 21:47

  2
  0
  Votes
  2
  Posts
  12
  Views

  26 Dec 2022, 21:47

  Welcome to the forum @StefanH I took the liberty to edit your post to mark your sketch as code. This makes the code mich easier to read. You can use the </> button on top of the edit area next time. Have you looked at https://github.com/mysensors/MySensorsArduinoExamples/blob/master/examples/DallasTemperatureSensor/DallasTemperatureSensor.ino ? It has support for multiple sensors. In any case, please post the debug output of your sketch. It will make it 10-100x easier to troubleshoot. If you haven't already, see https://forum.mysensors.org/topic/666/read-this-first-it-could-save-you-a-lot-of-time/ for how to enable debug output.
• 

  MySensors in a NERF gun - a question about capacitors
  1 Dec 2022, 07:09 • alowhum   22 Dec 2022, 09:11

  9
  2
  Votes
  9
  Posts
  41
  Views

  22 Dec 2022, 09:11

  I thought I'd give an update. I added four .470 capacitors in paralel, but the gun was still turning itself off. Then I added the diode, and.. it worked! The gun remains stable. ...at least.. while it was on a beefy lab power supply. It indicates that when firing the gun uses about .6 amps, and it prefers to be around 8.5 volts (6 AA batteries). 9 volts seems to be too much. I tried to switch it to the intended portable design, with a USB PD decoy feeding into a 4A up-down adjustable buck converter. But then it crashes again. For example, I tried this: 55W steam deck USB-C PD power supply -> adjustable decoy set to 15 or 20 volt. down-converting that to 8.5v with the buck converter. Maybe all this power converting means that it can't provide the sudden increases in power when the motor spins up? Perhaps using a linear DC-DC converter work better? Or maybe the USB-PD decoy just can't handle it? It's a mystery.
• 

  Detect Interrupt / Timer
  15 Dec 2022, 18:54 • Dave2526   16 Dec 2022, 10:43

  3
  0
  Votes
  3
  Posts
  19
  Views

  16 Dec 2022, 10:43

  Thats what I think, a really simple thing, Thank You, it works! resp_sleep=sleep(INTERRUPT,CHANGE,SLEEP_TIME); and then hust a simple if resp_sleep.... Thanks!
• 

  Send_Frequency_Full Wait
  14 Nov 2022, 14:50 • JeeLet   15 Dec 2022, 16:27

  3
  0
  Votes
  3
  Posts
  33
  Views

  15 Dec 2022, 16:27

  hange of direction, we forget the problems mentioned above, another bookstore. The project : reading of the values of an Electric meter with sending of the values on the bus RS485, from Node To Node. . ATmega328 (uno) / TIC demodulator / RS485 shield . ATmega328 / OLED / RS485 shield (DFRobot_RS485_Shield_SKU__DFR0259) video wiring diagram 2 sketches in txt file the latest version of the MicroQuettas LkyRx_10e.zip (9.4 KB) ... functional project
• 

  Can't get Serial Output from an RF-Nano
  11 Dec 2022, 17:38 • Keichi   12 Dec 2022, 16:20

  6
  0
  Votes
  6
  Posts
  22
  Views

  12 Dec 2022, 16:20

  Nice work @Keichi, thanks for reporting back!
• 

  Cannot compile on Lolin S2 Mini with USBCDC
  4 Dec 2022, 02:42 • Gibber   4 Dec 2022, 21:44

  3
  0
  Votes
  3
  Posts
  11
  Views

  4 Dec 2022, 21:44

  Hi, and thanks for the quick response. I tried the roll back but found that the Lolin S2 Mini was not an option in that version. I tried the Wemos D1 ESP32 and it would compile but the upload failed "Chip is unknown ESP32". I am going to try and use an external FTDI to avoid issues with USBCDC. If that does not work I will just use the D32 module. Thanks for the great body of work and support. I cannot even imagine how much work it must be to try and cover all the different chips and modules. The integration with Home Assistant makes this a breeze!
• 

  WeMos D1 mini won't start as gateway.
  1 Dec 2022, 23:59 • Igor Vinograd   3 Dec 2022, 08:37

  4
  0
  Votes
  4
  Posts
  21
  Views

  3 Dec 2022, 08:37

  Nice work @Igor-Vinograd, thanks for reporting back.
• 

  JSN-SR04T (distance sensor) Reliability Issue Fix?
  25 Oct 2020, 23:21 • Thomas Weeks   1 Dec 2022, 09:17

  24
  1
  Votes
  24
  Posts
  227
  Views

  1 Dec 2022, 09:17

  @Doubletop Thanks for that. I haven't range limited the readings on this version (ie ignore bad results) but do check for two consecutive readings, thus far no bogus readings recorded. In my own case, the 3v node had no spare pins, so had to expand anyway to avoid using to a second dedicated node. Having read on the 5v returning stable results, went with a second pro-mini at 5v controlling the v3.0 (also enabling further expansion) running off a PSU, talking I2C to the Node. My principal problem was winter condensation on the transducer head due to the pipe used, aside that the v2.0 ran two years before finally dying. This time it's on plastic pipe and the v3.0 is socketed for easy swap should it go faulty, fingers crossed for a trouble free winter.
• 

  No LAN connection ESP8266 gateway
  esp8266 • 20 Nov 2022, 14:51 • Bramz   28 Nov 2022, 14:18

  21
  0
  Votes
  21
  Posts
  105
  Views

  28 Nov 2022, 14:18

  Still, there seems to be 'someting rotten in the state of Network' where my LAN is concerned. Although the Arduino serial monitor says: 13:03:55.821 -> connected with XXX, channel 6 13:03:55.868 -> ip:192.168.178.4,mask:255.255.255.0,gw:192.168.178.1 13:03:55.915 -> ip:192.168.178.4,mask:255.255.255.0,gw:192.168.178.1 13:04:04.826 -> pm open,type:2 0 when I ping the IP-address I get: Pinging 192.168.178.4 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 192.168.178.4: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), When I use the tool 'Wireless Network Watcher' I do see that a device is connected at 192.168.178.4 with the correct MAC address. However, when I look at the management page of my FritzBox 7490 modem/router no device is mentioned at 192.168.178.4. I remain at a loss here.
• 

  [Help!] Adafruit Feather M0 with built-in RFM69HCW can't find parent / GW
  rfm69hcw adafruit featherm0 • 6 Nov 2022, 16:09 • DeepCore   21 Nov 2022, 21:10

  9
  0
  Votes
  9
  Posts
  39
  Views

  21 Nov 2022, 21:10

  @DeepCore not wrong frequency no. But it looks like the feather doesn’t come with the antenna pre-soldered. Since the devices should be identical otherwise, the antenna could be what differs. But if it was, the rssi would probably have been different as well.
• 

  Can anyone help me with led strip and distance sensor (similar concept to proximity sensor from the website)
  18 Nov 2022, 17:09 • TinkerTailor   19 Nov 2022, 01:49

  2
  0
  Votes
  2
  Posts
  16
  Views

  19 Nov 2022, 01:49

  Try using the Neopixel library. https://learn.adafruit.com/adafruit-neopixel-uberguide/arduino-library-use https://sbaronda.com/2020/09/20/sk6812-with-arduino-using-neopixel-library/ Those should get you started. Basically, instead of having your code directly turn a pin on or off, you tell it to set a color in the library and then run the show() command and the library will do all the pin toggling needed to actually control the LEDs.
• 

  Trying to build a ethernet gateway but cant set an ip address
  26 Mar 2020, 07:54 • JCH   18 Nov 2022, 05:32

  8
  1
  Votes
  8
  Posts
  41
  Views

  18 Nov 2022, 05:32

  @hoggin I don't know.
• 

  NACK after Core initialized, transport status 1
  19 Oct 2022, 17:59 • Tico   27 Oct 2022, 09:42

  8
  0
  Votes
  8
  Posts
  48
  Views

  27 Oct 2022, 09:42

  Hi There, Still investigating.... I refresh my nodemanager repo, but still same behavior. Thus I downgraded MySensors library from 2.4.0 Alpha to 2.3.2 for the nodemanager, still the same. Which is very strange to me as I have a nodemanager, SensorLatchingRelay2Pins, working perfectly over NRF24 with a serial gateway. I introduced some Serial.println in receive(const MyMessage &message), but looks like never called. Here is my code, maybe I wrote a mistake: /* * 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-2017 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. */ /************************** Template This sketch can be used as a template since containing the most relevant MySensors library configuration settings, NodeManager's settings, all its the supported sensors commented out and a sketch structure fully functional to operate with NodeManager. Just uncomment the settings you need and the sensors you want to add and configure the sensors in before() */ /********************************** * MySensors node configuration */ // General settings #define SKETCH_NAME "NodeManagerRelay" #define SKETCH_VERSION "1.0" #define MY_DEBUG //#define MY_NODE_ID 99 // NRF24 radio settings //#define MY_RADIO_RF24 //#define MY_RF24_ENABLE_ENCRYPTION //#define MY_RF24_CHANNEL 125 //#define MY_RF24_PA_LEVEL RF24_PA_HIGH //#define MY_DEBUG_VERBOSE_RF24 //#define MY_RF24_DATARATE RF24_250KBPS // RFM69 radio settings #define MY_RADIO_RFM69 #define MY_RFM69_FREQUENCY RFM69_868MHZ #define MY_IS_RFM69HW #define MY_RFM69_NEW_DRIVER //#define MY_RFM69_ENABLE_ENCRYPTION //#define MY_RFM69_NETWORKID 100 #define MY_DEBUG_VERBOSE_RFM69 #define MY_RFM69_IRQ_PIN 2 //#define MY_RFM69_IRQ_NUM MY_RFM69_IRQ_PIN #define MY_RFM69_CS_PIN 10 //#define MY_RF69_SPI_CS D2 //#define MY_RFM69_ATC_MODE_DISABLED // Advanced settings #define MY_BAUD_RATE 9600 //#define MY_SMART_SLEEP_WAIT_DURATION_MS 500 //#define MY_SPLASH_SCREEN_DISABLED //#define MY_DISABLE_RAM_ROUTING_TABLE_FEATURE //#define MY_SIGNAL_REPORT_ENABLED // Optimizations when running on 2032 Coin Cell. Also set nodeManager.setSleepBetweenSend(500) and run the board at 1Mhz //#define MY_TRANSPORT_UPLINK_CHECK_DISABLED //#define MY_TRANSPORT_WAIT_READY_MS 5000 //#define MY_SLEEP_TRANSPORT_RECONNECT_TIMEOUT_MS 2000 //#define MY_PARENT_NODE_ID 0 //#define MY_PARENT_NODE_IS_STATIC /********************************** * MySensors gateway configuration */ // Common gateway settings #define MY_REPEATER_FEATURE /*********************************** * NodeManager configuration */ #define NODEMANAGER_DEBUG ON #define NODEMANAGER_INTERRUPTS ON #define NODEMANAGER_SLEEP OFF #define NODEMANAGER_RECEIVE ON #define NODEMANAGER_DEBUG_VERBOSE ON #define NODEMANAGER_POWER_MANAGER OFF #define NODEMANAGER_CONDITIONAL_REPORT OFF #define NODEMANAGER_EEPROM OFF #define NODEMANAGER_TIME OFF #define NODEMANAGER_RTC OFF #define NODEMANAGER_SD OFF #define NODEMANAGER_HOOKING OFF #define NODEMANAGER_OTA_CONFIGURATION OFF #define NODEMANAGER_SERIAL_INPUT OFF // import NodeManager library (a nodeManager object will be then made available) #include <MySensors_NodeManager.h> /*********************************** * Add your sensors */ #include <sensors/SensorRelay.h> SensorRelay relay(6); /*********************************** * Main Sketch */ // before void before() { /*********************************** * Configure your sensors */ // call NodeManager before routine nodeManager.before(); } // presentation void presentation() { // call NodeManager presentation routine nodeManager.presentation(); } // setup void setup() { // call NodeManager setup routine nodeManager.setup(); } // loop void loop() { // call NodeManager loop routine nodeManager.loop(); } //#if NODEMANAGER_RECEIVE == ON // receive void receive(const MyMessage &message) { Serial.println("********* In receive ************"); if (message.isAck()) { Serial.println("************** This is an ack from gateway ******************"); } // call NodeManager receive routine nodeManager.receive(message); } //#endif #if NODEMANAGER_TIME == ON // receiveTime void receiveTime(unsigned long ts) { // call NodeManager receiveTime routine nodeManager.receiveTime(ts); } #endif So the detailed issue would be: A nodemanager doesn't receive ACK anymore after the INIT from the gateway (MQTT with TLS) over RFM69. Looks like receive(const MyMessage &message) is never called. An extract from the node logs to illustrate: 11:26:28.397 -> 7487 RFM69:SWR:ACK,FROM=0,SEQ=13,RSSI=-55 11:26:28.462 -> 7532 TSF:MSG:SEND,2-2-0-0,s=255,c=3,t=26,pt=1,l=1,sg=0,ft=0,st=OK:2 11:26:28.850 -> 7933 RFM69:SAC:SEND ACK,TO=0,RSSI=-44 11:26:28.882 -> 7974 RFM69:CSMA:RSSI=-100 11:26:28.914 -> 8003 TSF:MSG:READ,0-0-2,s=255,c=3,t=27,pt=1,l=1,sg=0:1 11:26:28.978 -> 8060 MCO:PIM:NODE REG=1 11:26:29.010 -> 8087 MCO:BGN:STP 11:26:29.047 -> 8105 NM:STP:ID=2 M=1 11:26:29.047 -> 8128 NM:LOOP:RELAY(1):SET t=2 v=0 11:26:29.717 -> 8235 NM:STP:HW V=3329 F=8 M=1116 11:26:29.749 -> 8269 MCO:BGN:INIT OK,TSP=1 11:26:29.782 -> 8298 NM:MSG:SEND(1) t=2 p=0 11:26:29.815 -> 8327 RFM69:SWR:SEND,TO=0,SEQ=14,RETRY=0 11:26:29.847 -> 8370 RFM69:CSMA:RSSI=-105 11:26:32.071 -> 10600 !RFM69:SWR:NACK I guess I can open an issue in the nodemanager github. Reg Eric.
• 

  Weird voltage output - MQ2 sensor
  19 Oct 2022, 16:49 • sn0w   24 Oct 2022, 22:09

  5
  0
  Votes
  5
  Posts
  29
  Views

  24 Oct 2022, 22:09

  Hello again. I tested everything again and i couldn't see any problem with connections or missing ground to the GND pins. On the breadboard voltage it's stable after a while and oscilating around 360-380mV. But the same MQ2 sensor on the PCB oscilating around 400, 800, 1100 mV and it's not stable at all I dont really get it. I've tried to use it with and without connecting to the USB (i thought that it's some GND missing and it could be stable after connecting USB cos the socket is a next GND, but no, still the same) Maybe the ESP32 wroom 32 needs additional connection to GND apart from the GND and VIN on the board? But the documentation says that: VIN to 5V and GND nothing more. I double checked the 5V regulator and it's regulated the 12V to stable 5V. I'm using thick wire to provide 5V and GND, maybe it's an issue? Should i use thinner one? But the other hand all voltage at the MQ2 or temperature sensor shows correct 5V. Even the ESP from the VIN shows correct voltage. Only output from MQ2 shows floating voltage and i dont know why because on the breadboard it's perfectly fine. :V its frustrating. I'm bet i missing something but i dont know what.
• 

  Help coding: adding functionality relying on MySensors-func/library (saveState/loadState) (c++)
  18 Oct 2022, 14:23 • perIpI   19 Oct 2022, 06:47

  5
  0
  Votes
  5
  Posts
  30
  Views

  19 Oct 2022, 06:47

  @electrik Tested and worked as well. I think this is preferable over the first solution (forward function declaration) as it gives a reference where the functions are defined. Thank you!
• 

  NRF24 Weather Station Issues
  11 Oct 2022, 01:18 • itsthezack   11 Oct 2022, 14:40

  2
  0
  Votes
  2
  Posts
  28
  Views

  11 Oct 2022, 14:40

  Looks like the image didn’t come through. Let’s try again…
• 

  Find Parent (yeah, I know)
  3 Oct 2022, 21:20 • qqlapraline   9 Oct 2022, 09:57

  11
  0
  Votes
  11
  Posts
  69
  Views

  9 Oct 2022, 09:57

  You are right, @NeverDie. Actually, my power supply is coming from a french power meter, that means a lot of noise - as I'm DC from a 50Khz AC :). So, I did two things. Adding a 330 pF capacitor at the entry point of my board and a 47µF right next to the NRF24. Finally, I've upgrade my design to add a tantalium capacitor right next to the smd pads. Global view: Zooming the back with the polarized capacity (old fashion): Front view: New design: Cheers, QQ
• 

  [SOLVED] Ethernet MQTT Gateway Slow to connect
  22 Jan 2019, 13:37 • Guillermo Schimmel   4 Oct 2022, 23:05

  11
  0
  Votes
  11
  Posts
  1.5k
  Views

  4 Oct 2022, 23:05

  Hi @Guillermo-Schimmel, I know it's closed but just noticed this issue, you most probably had STP (Spanning Tree Protocol) enabled on that port, which is normal for ent switch, and while it waits for a loop it blocks trafic from that port. Disabling that feature should solve this problem.
• 

  MySensors GW on rpi3
  gateway • 28 Sept 2022, 11:24 • Kurtsejr   30 Sept 2022, 18:07

  20
  0
  Votes
  20
  Posts
  40
  Views

  30 Sept 2022, 18:07

  Nice work @Kurtsejr, thanks for reporting back
• 

  error compiling
  14 Sept 2022, 17:10 • alexsh1   14 Sept 2022, 20:57

  2
  0
  Votes
  2
  Posts
  15
  Views

  14 Sept 2022, 20:57

  @alexsh1 https://github.com/arduino/ArduinoCore-avr/issues/158 and https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60040 suggests it is a bug in gcc. It seems to have been resolved a long time ago though.
• 

  Raspberry Pi 3 (RPI 3) + MQTT gateway NACK and triple messages
  3 Sept 2022, 18:55 • Oumuamua   10 Sept 2022, 20:34

  4
  0
  Votes
  4
  Posts
  28
  Views

  10 Sept 2022, 20:34

  Thanks @mfalkvidd @OldSurferDude ! The problem really was the antenna. I was using the helical antenna below and I welded in the "wrong" part of it the first time. The second I welded it on the "right" place and it work. The RSSI is still below that the old and good wire... am I welding it on the really right place? Are helical antennas good? Thanks again for the great support you provide.
• 

  NRF5 Receive Challenges
  4 Sept 2022, 03:07 • nagelc   5 Sept 2022, 20:40

  5
  0
  Votes
  5
  Posts
  41
  Views

  5 Sept 2022, 20:40

  Nice work @nagelc, thanks for reporting back.
• 

  Gateway sends NACK to node
  gateway • 23 Jul 2022, 14:51 • mariusl   5 Sept 2022, 07:19

  15
  0
  Votes
  15
  Posts
  128
  Views

  5 Sept 2022, 07:19

  Aah ok that makes sense. My application is for rural use and I need the max distance possible. The slow response will not be a problem as the sensors don't send a lot of data at all. So maybe I will stay with the SF4096 for now but I will do some experimenting with the settings. Just to understand them a bit better.
• 

  Gateway doesn't receive any message from node
  13 Aug 2022, 18:22 • ctodor   30 Aug 2022, 15:46

  25
  1
  Votes
  25
  Posts
  141
  Views

  30 Aug 2022, 15:46

  @mfalkvidd multimeter
• 

  Raspberry Pi 3 (RPI 3) gateway initialization loop
  28 Aug 2022, 02:24 • Oumuamua   29 Aug 2022, 02:22

  6
  0
  Votes
  6
  Posts
  27
  Views

  29 Aug 2022, 02:22

  Problem solved: I was using as --my-mqtt-client-id the same name as my previous broker. Thanks for your help all!
• 

  Gateway on RPi zero config.h:39: first defined here
  27 Aug 2022, 04:29 • OldSurferDude   27 Aug 2022, 05:25

  2
  0
  Votes
  2
  Posts
  15
  Views

  27 Aug 2022, 05:25

  I found the answer here. In config.c two lines have to be added and in config.h, one line is modified and two added
• 

  ESP8266Wifi Gateway won't connect
  18 Aug 2022, 19:09 • dpcons   25 Aug 2022, 19:12

  33
  0
  Votes
  33
  Posts
  138
  Views

  25 Aug 2022, 19:12

  @mfalkvidd Yes, totally forgot about that link you put there. Thanks for reminding me.
• 

  VL53L0X with water tanks
  13 Aug 2022, 12:59 • Papari Das   16 Aug 2022, 16:16

  7
  0
  Votes
  7
  Posts
  36
  Views

  16 Aug 2022, 16:16

  @johnnyfp When first read this I was wondering if the signal would be reflected accurately off the surface. Apparently not. I'm currently using float sensors which gives me full and empty. I would like to get a level sensor that was accurate to a centimeter so that I could measure the rate of fill, too. My current endeavor is to take this tank gauge put eight magnetic switches around it, and a magnet on the wheel inside. The magnetic switches would be connected to an Arduino nano and I could tell where the wheel is. Alas, other projects have higher priority.
• 

  Question with regards to NRF24 antenna folding
  1 Aug 2022, 16:01 • naruse   15 Aug 2022, 13:05

  11
  0
  Votes
  11
  Posts
  45
  Views

  15 Aug 2022, 13:05

  @iguaan I have it wrapped as you mentioned and soldered to the ground. Curiously enough I have the PA set to HIGH (had it set to LOW), but from my understanding, by setting it to HIGH the "power" of the antena is better no?, hence the reception should be better. or what am I missing? Thanks for the feedback as well
• 

  RFM69 waking up MCU with IRQ
  13 Aug 2022, 01:37 • Ethan Chua   13 Aug 2022, 13:58

  3
  1
  Votes
  3
  Posts
  17
  Views

  13 Aug 2022, 13:58

  This seems to be a fairly common problem with PIR motion sensors. One trick is to add a short sleep statement before your final one to let all the voltages settle: // Short sleep to let voltages settle (change duration as needed) sleep(500); // Sleep until interrupt comes in on motion sensor. Send update every ten seconds for testing. sleep(digitalPinToInterrupt(DIGITAL_INPUT_SENSOR), CHANGE, 10000); code_text
• 

  Trouble with the JSN SR04T
  21 Jul 2019, 13:43 • Sundeep Goel   13 Aug 2022, 12:53

  23
  0
  Votes
  23
  Posts
  2.5k
  Views

  13 Aug 2022, 12:53

  @Sundeep-Goel did u face any issues due to water vapours or water in general?
• 

  smart sleep inconsistent?
  4 Aug 2022, 18:59 • CrankyCoder   10 Aug 2022, 09:46

  21
  0
  Votes
  21
  Posts
  72
  Views

  10 Aug 2022, 09:46

  @CrankyCoder How far apart are the node and gateway? What is between them? Can you post any photos of of each with the wiring?
• 

  Home Assistant HVAC Serial gateway (fan speed)
  7 Aug 2022, 19:03 • Willie-wortel   7 Aug 2022, 19:03

  1
  0
  Votes
  1
  Posts
  13
  Views

  No one has replied

• 

  Simple door sensor battery node drains 2 x AA in a week due to pin D2
  1 Aug 2022, 12:30 • novicit   4 Aug 2022, 04:53

  6
  0
  Votes
  6
  Posts
  24
  Views

  4 Aug 2022, 04:53

  @novicit @bjacobse Good call!
• 

  BME 280 pinout reversed...
  12 Jul 2022, 20:05 • ueb   17 Jul 2022, 21:16

  6
  0
  Votes
  6
  Posts
  41
  Views

  17 Jul 2022, 21:16

  Maybe they reflowed the chip on backwards (rotated 180 degrees)? You could compare the chips orientation to photos of known good breakout boards, or to the datasheet. If so, you'd definitely have a solid case for a refund if it's worth your time to pursue it with the seller.
• 

  Error compiling mysensors in beaglebone black
  16 Jun 2022, 22:41 • ruben_gr   23 Jun 2022, 15:52

  15
  0
  Votes
  15
  Posts
  47
  Views

  23 Jun 2022, 15:52

  http://learntohackit.com/intro/# it can be useful information ???
• 

  powering Arduino nano from USB and NRF24L01+ from AA batteries. Not working
  15 Jun 2022, 09:41 • garubi   20 Jun 2022, 08:27

  7
  0
  Votes
  7
  Posts
  23
  Views

  20 Jun 2022, 08:27

  Just for others coming here in the future: I changed the connections as suggested by @mfalkvidd , restarted the node and now the radio runs from batteries and the Arduino is powered from USB (phone charger). Unfortunately this doesn't seem to have improved the radio communication, but this is another story... Stefano
• 

  "0" Temp and Pressure readings from BMP280
  bmp280 arduino esp8266 • 11 Jun 2022, 07:46 • Merlotmaker   14 Jun 2022, 15:15

  2
  0
  Votes
  2
  Posts
  13
  Views

  14 Jun 2022, 15:15

  Hi @Merlotmaker, If you want more reactions from members, you should provide more information. what for sensor do you have, because you are speaking about BMP280 and BME280 the lib you are referring to is a specific one for the https://www.sparkfun.com/products/13676 how did you connect your sensor to the UNO? did you follow this guide already? https://learn.sparkfun.com/tutorials/sparkfun-bme280-breakout-hookup-guide
• 

  Newbie: Sensors do not connect
  1 Jun 2022, 13:39 • mariusl   13 Jun 2022, 07:36

  16
  0
  Votes
  16
  Posts
  66
  Views

  13 Jun 2022, 07:36

  @OldSurferDude I have since looked at various modules that are sold on the internet. My conclusion is that they are not all the same. Some seem to be much better than others. The price also shows that. I use this shield for the radio comms NANO V3 Wireless Shield. It has the caps already built in as well as some level shifting for the signal pins.
• 

  Homeassistant in docker dont connect with serial gateway
  6 Jun 2022, 21:55 • badisensors   6 Jun 2022, 21:55

  1
  0
  Votes
  1
  Posts
  27
  Views

  No one has replied

• 

  Sensebender Gateway 1.0 - Init weirdness...
  30 May 2022, 09:03 • tomtastic   6 Jun 2022, 09:48

  4
  0
  Votes
  4
  Posts
  26
  Views

  6 Jun 2022, 09:48

  Hi all, This is what I Simply ended up with to clear the eeprom, // load core modules only #define MY_CORE_ONLY #include <MySensors.h> void before(){ Serial.begin(115200); Serial.println("Started clearing. Please wait..."); for (uint16_t i=0; i<EEPROM_LOCAL_CONFIG_ADDRESS; i++) { hwWriteConfig(i,0xFF); } Serial.println("Clearing done."); } void setup() { Serial.begin(115200); Serial.println("Started clearing. Please wait..."); for (uint16_t i=0; i<EEPROM_LOCAL_CONFIG_ADDRESS; i++) { hwWriteConfig(i,0xFF); Serial.println(i); } Serial.println("Clearing done."); } void loop() { // Nothing to do here... }
• 

  Node can send I_FIND_PARENT_REQUEST but cannot receive I_FIND_PARENT_RESPONSE
  4 Jun 2022, 09:49 • Ethan Chua   5 Jun 2022, 14:55

  4
  0
  Votes
  4
  Posts
  21
  Views

  5 Jun 2022, 14:55

  If you have the wrong modules, it could give you problems yes. Check out the buying guide, there are recommendations for the modules to pick, for example the ebyte ones. The will work very reliable. Big advantage of NRF24 to RFM69 is the throughput and response time.
• 

  signal report functionality 2.2.0 to 2.3.2 changes?
  22 May 2022, 18:12 • Nigel31   22 May 2022, 18:12

  1
  0
  Votes
  1
  Posts
  28
  Views

  No one has replied

• 

  Sudden Dead node, and consequent !TSM:FPAR:NO REPLY
  9 May 2022, 09:16 • Nigel31   22 May 2022, 18:05

  5
  1
  Votes
  5
  Posts
  54
  Views

  22 May 2022, 18:05

  @Nigel31 glad you got a fix
• 

  Arduino sensor does not communicate
  13 May 2022, 16:00 • tutur19   15 May 2022, 18:47

  3
  0
  Votes
  3
  Posts
  24
  Views

  15 May 2022, 18:47

  Hi, thanks you so much for answer. I continue to search and I think I find what is wrong.. . .. It's because I use pin pitch female And the connection is very bad.. Sometime it's work, sometime don't.. . I sold it, and I correctly use 3 NRF now... I continue to compare but now I have a comparaison point... I continue to search but you're right, the parent ID is not setup same way on different sketch. I try it next week.
• 

  1.5.1 to 2.3.2 issues
  30 Apr 2022, 09:45 • epierre   30 Apr 2022, 14:27

  4
  0
  Votes
  4
  Posts
  25
  Views

  30 Apr 2022, 14:27

  intermediary result: I have started a second gateway and now the nodes do communicate... puzzled... I remove the extra gateway... same situation... so reprogram gateway with: #define MY_RF24_PA_LEVEL RF24_PA_LOW so it seems this was the responsible for this ! thanks !
• 

  Ebyte nRF24L01P Wireless rf Transceiver E01-2G4M27D 27dBm SPI 2.4GHz Transmitter
  10 Apr 2022, 18:04 • epierre   24 Apr 2022, 17:24

  12
  0
  Votes
  12
  Posts
  70
  Views

  24 Apr 2022, 17:24

  @epierre Yay, good job!
• 

  How to optimise a code (95% memory used)
  27 Feb 2022, 17:33 • cwiekol   4 Apr 2022, 20:19

  7
  0
  Votes
  7
  Posts
  66
  Views

  4 Apr 2022, 20:19

  I found that timelib.h uses a tremendous amount of memory. You avoid using it by getting time string from the controller. I have also found that when you're using that amount of memory that bad things happen, as you noted. I use global variables to avoid the transient nature of function variables. I'll be looking forward to other comments as, I, too, do not know all the tricks;) OSD
• 

  Sensebenders Gateway Weird Behavior
  1 Apr 2022, 18:51 • ejlane   3 Apr 2022, 19:32

  3
  0
  Votes
  3
  Posts
  20
  Views

  3 Apr 2022, 19:32

  Well done @ejlane, thanks for reporting back.
• 

  Trying to setup a gateway on Orangepi Zero 2..
  23 Mar 2022, 16:23 • kted   28 Mar 2022, 11:15

  3
  0
  Votes
  3
  Posts
  26
  Views

  28 Mar 2022, 11:15

  @electrik Going through the documentation of the Orangepi, I found out that the config should be --my-rfm69-irq-pin=71 --my-rfm69-cs-pin=233 but still no dice. I also get an error: Mar 28 14:11:14 DEBUG MCO:BGN:INIT GW,CP=RPNGL---,FQ=NA,REL=0,VER=2.4.0-alpha Mar 28 14:11:14 DEBUG TSF:LRT:OK Mar 28 14:11:14 DEBUG TSM:INIT Mar 28 14:11:14 DEBUG TSF:WUR:MS=0 Mar 28 14:11:14 DEBUG TSM:INIT:TSP OK Mar 28 14:11:14 DEBUG TSM:INIT:GW MODE Mar 28 14:11:14 ERROR Interrupt handler error: Bad file descriptor Mar 28 14:11:14 DEBUG TSM:READY:ID=0,PAR=0,DIS=0 Mar 28 14:11:14 DEBUG MCO:REG:NOT NEEDED Mar 28 14:11:14 DEBUG Listening for connections on ▒]o:5003 Mar 28 14:11:14 DEBUG MCO:BGN:STP Mar 28 14:11:14 DEBUG MCO:BGN:INIT OK,TSP=1 Mar 28 14:11:14 DEBUG TSM:READY:NWD REQ Mar 28 14:11:16 DEBUG ?TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=OK: The IRQ pin is connected alright, the RFM69 module works perfectly on a RaspberryPi or an OrangePi Zero. It just refuses to receive when used on the OrangePi Zero 2 Something with pin assignements or SPI... It is a a new SOC, so maybe I should wait for someone with more expertise than me to work it out...
• 

  Beginner concept question for serial communication
  17 Mar 2022, 09:33 • hubertus   28 Mar 2022, 06:52

  4
  0
  Votes
  4
  Posts
  54
  Views

  28 Mar 2022, 06:52

  Hi there and thank you for your help. The answers came later than I expected (never mind) and during a period as I am away from my arduinos and raspberry. I will try to make a sketch to show you the set up. But I am not interested to connect the sensor directly to raspberry pi by one-wire. The set up is like this Arduino with Dallas Temperature <> Serial interface <Serial cable> Moxa Serial to IP <Ethernet / virtual serial port> Raspberry pi as gateway with virtual serial port <Ethernet> Home assistant I will try to use SoftwareSerial, which is what I used already without mysensors on pin 00 et 1. What I am struggling with is the mysensors configuration for serial port and the gateway on raspberry with the virtual serial port. Keep you updated.
• 

  MySensors v2.4.0-alpha over PJON transport with a Raspberry PI gateway
  25 Mar 2022, 00:09 • Dragota   25 Mar 2022, 16:33

  2
  0
  Votes
  2
  Posts
  32
  Views

  25 Mar 2022, 16:33

  Yes, the configure script would have to be modified to support PJON. But I'm not sure that's enough. I ran ./configure and then edited Makefile.inc, where I replaced -DMY_RADIO_RF24 with -DMY_PJON. This was the result: g++ -MT build/examples_linux/mysgw.o -MMD -MP -march=armv8-a+crc -mtune=cortex-a72 -mfpu=neon-fp-armv8 -mfloat-abi=hard -DMY_PJON -DMY_GATEWAY_LINUX -DMY_DEBUG -DLINUX_SPI_BCM -DLINUX_ARCH_RASPBERRYPI -Ofast -g -Wall -Wextra -std=c++11 -I. -I./core -I./hal/architecture/Linux/drivers/core -I./hal/architecture/Linux/drivers/BCM -c examples_linux/mysgw.cpp -o build/examples_linux/mysgw.o In file included from ./hal/transport/PJON/driver/PJON.h:62, from ./MySensors.h:390, from examples_linux/mysgw.cpp:82: ./hal/transport/PJON/driver/PJONDefines.h: In static member function ‘static void PJONTools::parse_header(const uint8_t*, PJON_Packet_Info&)’: ./hal/transport/PJON/driver/PJONDefines.h:415:31: warning: ‘void* memset(void*, int, size_t)’ clearing an object of non-trivial type ‘struct PJON_Packet_Info’; use assignment or value-initialization instead [-Wclass-memaccess] memset(&info, 0, sizeof info); ^ ./hal/transport/PJON/driver/PJONDefines.h:207:8: note: ‘struct PJON_Packet_Info’ declared here struct PJON_Packet_Info { ^~~~~~~~~~~~~~~~ In file included from ./MySensors.h:390, from examples_linux/mysgw.cpp:82: ./hal/transport/PJON/driver/PJON.h: At global scope: ./hal/transport/PJON/driver/PJON.h:1043:31: error: ‘A0’ was not declared in this scope uint8_t _random_seed = A0; ^~ ./hal/transport/PJON/driver/PJON.h:1043:31: note: suggested alternative: ‘y0’ uint8_t _random_seed = A0; ^~ y0 ./hal/transport/PJON/driver/PJON.h: In member function ‘void PJON<Strategy>::begin()’: ./hal/transport/PJON/driver/PJON.h:149:20: error: there are no arguments to ‘PJON_ANALOG_READ’ that depend on a template parameter, so a declaration of ‘PJON_ANALOG_READ’ must be available [-fpermissive] PJON_RANDOM_SEED(PJON_ANALOG_READ(_random_seed) + tx.id); ^~~~~~~~~~~~~~~~ ./hal/transport/PJON/driver/PJON.h:149:20: note: (if you use ‘-fpermissive’, G++ will accept your code, but allowing the use of an undeclared name is deprecated) ./hal/transport/PJON/driver/PJON.h: In member function ‘uint16_t PJON<Strategy>::dispatch(const PJON_Packet_Info&, const void*, uint16_t, uint32_t, uint16_t)’: ./hal/transport/PJON/driver/PJON.h:222:31: error: there are no arguments to ‘PJON_MICROS’ that depend on a template parameter, so a declaration of ‘PJON_MICROS’ must be available [-fpermissive] packets[i].registration = PJON_MICROS(); ^~~~~~~~~~~ ./hal/transport/PJON/driver/PJON.h: In member function ‘uint16_t PJON<Strategy>::receive(uint32_t)’: ./hal/transport/PJON/driver/PJON.h:456:19: error: there are no arguments to ‘PJON_MICROS’ that depend on a template parameter, so a declaration of ‘PJON_MICROS’ must be available [-fpermissive] uint32_t time = PJON_MICROS(); ^~~~~~~~~~~ ./hal/transport/PJON/driver/PJON.h:462:19: error: there are no arguments to ‘PJON_MICROS’ that depend on a template parameter, so a declaration of ‘PJON_MICROS’ must be available [-fpermissive] ((uint32_t)(PJON_MICROS() - time) <= duration) ^~~~~~~~~~~ ./hal/transport/PJON/driver/PJON.h: In member function ‘bool PJON<Strategy>::reset_packet(uint16_t)’: ./hal/transport/PJON/driver/PJON.h:506:31: error: there are no arguments to ‘PJON_MICROS’ that depend on a template parameter, so a declaration of ‘PJON_MICROS’ must be available [-fpermissive] packets[id].registration = PJON_MICROS(); ^~~~~~~~~~~ ./hal/transport/PJON/driver/PJON.h: In member function ‘uint16_t PJON<Strategy>::send_packet_blocking(const PJON_Packet_Info&, const void*, uint16_t, uint32_t)’: ./hal/transport/PJON/driver/PJON.h:695:20: error: there are no arguments to ‘PJON_MICROS’ that depend on a template parameter, so a declaration of ‘PJON_MICROS’ must be available [-fpermissive] uint32_t start = PJON_MICROS(); ^~~~~~~~~~~ ./hal/transport/PJON/driver/PJON.h:701:18: error: there are no arguments to ‘PJON_MICROS’ that depend on a template parameter, so a declaration of ‘PJON_MICROS’ must be available [-fpermissive] (uint32_t)(PJON_MICROS() - start) <= timeout ^~~~~~~~~~~ ./hal/transport/PJON/driver/PJON.h:721:5: error: there are no arguments to ‘PJON_DELAY’ that depend on a template parameter, so a declaration of ‘PJON_DELAY’ must be available [-fpermissive] PJON_DELAY((uint32_t)(strategy.back_off(attempts) / 1000)); ^~~~~~~~~~ ./hal/transport/PJON/driver/PJON.h: In member function ‘uint16_t PJON<Strategy>::update()’: ./hal/transport/PJON/driver/PJON.h:932:19: error: there are no arguments to ‘PJON_MICROS’ that depend on a template parameter, so a declaration of ‘PJON_MICROS’ must be available [-fpermissive] (uint32_t)(PJON_MICROS() - packets[i].registration) > ^~~~~~~~~~~ In file included from ./hal/transport/PJON/driver/PJONSoftwareBitBang.h:5, from ./MySensors.h:391, from examples_linux/mysgw.cpp:82: ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h: In member function ‘bool SoftwareBitBang::begin(uint8_t)’: ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:66:14: error: ‘PJON_RANDOM’ was not declared in this scope PJON_DELAY(PJON_RANDOM(SWBB_INITIAL_DELAY) + did); ^~~~~~~~~~~ ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:66:14: note: suggested alternative: ‘PJON_NAK’ PJON_DELAY(PJON_RANDOM(SWBB_INITIAL_DELAY) + did); ^~~~~~~~~~~ PJON_NAK ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:66:3: error: ‘PJON_DELAY’ was not declared in this scope PJON_DELAY(PJON_RANDOM(SWBB_INITIAL_DELAY) + did); ^~~~~~~~~~ ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:66:3: note: suggested alternative: ‘PJON_DEBUG’ PJON_DELAY(PJON_RANDOM(SWBB_INITIAL_DELAY) + did); ^~~~~~~~~~ PJON_DEBUG ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h: In member function ‘bool SoftwareBitBang::can_start()’: ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:76:3: error: ‘PJON_IO_MODE’ was not declared in this scope PJON_IO_MODE(_input_pin, INPUT); ^~~~~~~~~~~~ ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:76:3: note: suggested alternative: ‘PJON_NO_HEADER’ PJON_IO_MODE(_input_pin, INPUT); ^~~~~~~~~~~~ PJON_NO_HEADER ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:78:3: error: ‘PJON_DELAY_MICROSECONDS’ was not declared in this scope PJON_DELAY_MICROSECONDS(SWBB_BIT_SPACER / 2); ^~~~~~~~~~~~~~~~~~~~~~~ ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:79:6: error: ‘PJON_IO_READ’ was not declared in this scope if(PJON_IO_READ(_input_pin)) { ^~~~~~~~~~~~ ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:79:6: note: suggested alternative: ‘PJON_NO_HEADER’ if(PJON_IO_READ(_input_pin)) { ^~~~~~~~~~~~ PJON_NO_HEADER ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:83:6: error: ‘PJON_IO_READ’ was not declared in this scope if(PJON_IO_READ(_input_pin)) { ^~~~~~~~~~~~ ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:83:6: note: suggested alternative: ‘PJON_NO_HEADER’ if(PJON_IO_READ(_input_pin)) { ^~~~~~~~~~~~ PJON_NO_HEADER ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:88:7: error: ‘PJON_IO_READ’ was not declared in this scope if(PJON_IO_READ(_input_pin)) { ^~~~~~~~~~~~ ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:88:7: note: suggested alternative: ‘PJON_NO_HEADER’ if(PJON_IO_READ(_input_pin)) { ^~~~~~~~~~~~ PJON_NO_HEADER ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:93:6: error: ‘PJON_IO_READ’ was not declared in this scope if(PJON_IO_READ(_input_pin)) { ^~~~~~~~~~~~ ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:93:6: note: suggested alternative: ‘PJON_NO_HEADER’ if(PJON_IO_READ(_input_pin)) { ^~~~~~~~~~~~ PJON_NO_HEADER ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:98:6: error: ‘PJON_IO_READ’ was not declared in this scope if(PJON_IO_READ(_input_pin)) { ^~~~~~~~~~~~ ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:98:6: note: suggested alternative: ‘PJON_NO_HEADER’ if(PJON_IO_READ(_input_pin)) { ^~~~~~~~~~~~ PJON_NO_HEADER ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:102:27: error: ‘PJON_RANDOM’ was not declared in this scope PJON_DELAY_MICROSECONDS(PJON_RANDOM(SWBB_COLLISION_DELAY)); ^~~~~~~~~~~ ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:102:27: note: suggested alternative: ‘PJON_NAK’ PJON_DELAY_MICROSECONDS(PJON_RANDOM(SWBB_COLLISION_DELAY)); ^~~~~~~~~~~ PJON_NAK ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:103:6: error: ‘PJON_IO_READ’ was not declared in this scope if(PJON_IO_READ(_input_pin)) { ^~~~~~~~~~~~ ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:103:6: note: suggested alternative: ‘PJON_NO_HEADER’ if(PJON_IO_READ(_input_pin)) { ^~~~~~~~~~~~ PJON_NO_HEADER ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h: In member function ‘void SoftwareBitBang::handle_collision()’: ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:130:27: error: ‘PJON_RANDOM’ was not declared in this scope PJON_DELAY_MICROSECONDS(PJON_RANDOM(SWBB_COLLISION_DELAY)); ^~~~~~~~~~~ ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:130:27: note: suggested alternative: ‘PJON_NAK’ PJON_DELAY_MICROSECONDS(PJON_RANDOM(SWBB_COLLISION_DELAY)); ^~~~~~~~~~~ PJON_NAK ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:130:3: error: ‘PJON_DELAY_MICROSECONDS’ was not declared in this scope PJON_DELAY_MICROSECONDS(PJON_RANDOM(SWBB_COLLISION_DELAY)); ^~~~~~~~~~~~~~~~~~~~~~~ ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h: In member function ‘uint8_t SoftwareBitBang::read_byte()’: ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:140:3: error: ‘PJON_DELAY_MICROSECONDS’ was not declared in this scope PJON_DELAY_MICROSECONDS(SWBB_BIT_WIDTH / 2); ^~~~~~~~~~~~~~~~~~~~~~~ ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:143:18: error: ‘PJON_IO_READ’ was not declared in this scope byte_value += PJON_IO_READ(_input_pin) << i; ^~~~~~~~~~~~ ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:143:18: note: suggested alternative: ‘PJON_NO_HEADER’ byte_value += PJON_IO_READ(_input_pin) << i; ^~~~~~~~~~~~ PJON_NO_HEADER ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:148:17: error: ‘PJON_IO_READ’ was not declared in this scope byte_value += PJON_IO_READ(_input_pin) << 7; ^~~~~~~~~~~~ ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:148:17: note: suggested alternative: ‘PJON_NO_HEADER’ byte_value += PJON_IO_READ(_input_pin) << 7; ^~~~~~~~~~~~ PJON_NO_HEADER ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h: In member function ‘uint16_t SoftwareBitBang::receive_response()’: ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:175:4: error: ‘PJON_IO_WRITE’ was not declared in this scope PJON_IO_WRITE(_output_pin, LOW); ^~~~~~~~~~~~~ ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:175:4: note: suggested alternative: ‘PJON_NO_HEADER’ PJON_IO_WRITE(_output_pin, LOW); ^~~~~~~~~~~~~ PJON_NO_HEADER ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:178:19: error: ‘PJON_MICROS’ was not declared in this scope uint32_t time = PJON_MICROS(); ^~~~~~~~~~~ ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:178:19: note: suggested alternative: ‘MOD_MICRO’ uint32_t time = PJON_MICROS(); ^~~~~~~~~~~ MOD_MICRO ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:180:4: error: ‘PJON_IO_WRITE’ was not declared in this scope PJON_IO_WRITE(_input_pin, LOW); ^~~~~~~~~~~~~ ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:180:4: note: suggested alternative: ‘PJON_NO_HEADER’ PJON_IO_WRITE(_input_pin, LOW); ^~~~~~~~~~~~~ PJON_NO_HEADER ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:185:5: error: ‘PJON_IO_MODE’ was not declared in this scope PJON_IO_MODE(_output_pin, OUTPUT); ^~~~~~~~~~~~ ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:185:5: note: suggested alternative: ‘PJON_NO_HEADER’ PJON_IO_MODE(_output_pin, OUTPUT); ^~~~~~~~~~~~ PJON_NO_HEADER ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:187:5: error: ‘PJON_DELAY_MICROSECONDS’ was not declared in this scope PJON_DELAY_MICROSECONDS(SWBB_BIT_WIDTH / 4); ^~~~~~~~~~~~~~~~~~~~~~~ ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:188:5: error: ‘PJON_IO_PULL_DOWN’ was not declared in this scope PJON_IO_PULL_DOWN(_output_pin); ^~~~~~~~~~~~~~~~~ ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:188:5: note: suggested alternative: ‘PJON_INCLUDE_PORT’ PJON_IO_PULL_DOWN(_output_pin); ^~~~~~~~~~~~~~~~~ PJON_INCLUDE_PORT ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h: In member function ‘uint16_t SoftwareBitBang::receive_frame(uint8_t*, uint16_t)’: ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:203:20: error: ‘PJON_MICROS’ was not declared in this scope uint32_t time = PJON_MICROS(); ^~~~~~~~~~~ ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:203:20: note: suggested alternative: ‘MOD_MICRO’ uint32_t time = PJON_MICROS(); ^~~~~~~~~~~ MOD_MICRO ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h: In member function ‘void SoftwareBitBang::send_byte(uint8_t)’: ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:248:4: error: ‘PJON_IO_WRITE’ was not declared in this scope PJON_IO_WRITE(_output_pin, b & mask); ^~~~~~~~~~~~~ ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:248:4: note: suggested alternative: ‘PJON_NO_HEADER’ PJON_IO_WRITE(_output_pin, b & mask); ^~~~~~~~~~~~~ PJON_NO_HEADER ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:249:4: error: ‘PJON_DELAY_MICROSECONDS’ was not declared in this scope PJON_DELAY_MICROSECONDS(SWBB_BIT_WIDTH); ^~~~~~~~~~~~~~~~~~~~~~~ ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h: In member function ‘void SoftwareBitBang::send_response(uint8_t)’: ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:262:3: error: ‘PJON_IO_PULL_DOWN’ was not declared in this scope PJON_IO_PULL_DOWN(_input_pin); ^~~~~~~~~~~~~~~~~ ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:262:3: note: suggested alternative: ‘PJON_INCLUDE_PORT’ PJON_IO_PULL_DOWN(_input_pin); ^~~~~~~~~~~~~~~~~ PJON_INCLUDE_PORT ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:263:19: error: ‘PJON_MICROS’ was not declared in this scope uint32_t time = PJON_MICROS(); ^~~~~~~~~~~ ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:263:19: note: suggested alternative: ‘MOD_MICRO’ uint32_t time = PJON_MICROS(); ^~~~~~~~~~~ MOD_MICRO ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:266:8: error: ‘PJON_IO_READ’ was not declared in this scope !PJON_IO_READ(_input_pin) ^~~~~~~~~~~~ ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:266:8: note: suggested alternative: ‘PJON_NO_HEADER’ !PJON_IO_READ(_input_pin) ^~~~~~~~~~~~ PJON_NO_HEADER ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:271:7: error: ‘PJON_IO_READ’ was not declared in this scope PJON_IO_READ(_input_pin) ^~~~~~~~~~~~ ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:271:7: note: suggested alternative: ‘PJON_NO_HEADER’ PJON_IO_READ(_input_pin) ^~~~~~~~~~~~ PJON_NO_HEADER ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:273:3: error: ‘PJON_IO_MODE’ was not declared in this scope PJON_IO_MODE(_output_pin, OUTPUT); ^~~~~~~~~~~~ ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:273:3: note: suggested alternative: ‘PJON_NO_HEADER’ PJON_IO_MODE(_output_pin, OUTPUT); ^~~~~~~~~~~~ PJON_NO_HEADER ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h: In member function ‘void SoftwareBitBang::send_frame(uint8_t*, uint16_t)’: ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:296:3: error: ‘PJON_IO_MODE’ was not declared in this scope PJON_IO_MODE(_output_pin, OUTPUT); ^~~~~~~~~~~~ ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:296:3: note: suggested alternative: ‘PJON_NO_HEADER’ PJON_IO_MODE(_output_pin, OUTPUT); ^~~~~~~~~~~~ PJON_NO_HEADER ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:301:3: error: ‘PJON_IO_PULL_DOWN’ was not declared in this scope PJON_IO_PULL_DOWN(_output_pin); ^~~~~~~~~~~~~~~~~ ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:301:3: note: suggested alternative: ‘PJON_INCLUDE_PORT’ PJON_IO_PULL_DOWN(_output_pin); ^~~~~~~~~~~~~~~~~ PJON_INCLUDE_PORT ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h: In member function ‘bool SoftwareBitBang::sync(uint32_t)’: ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:324:3: error: ‘PJON_IO_PULL_DOWN’ was not declared in this scope PJON_IO_PULL_DOWN(_input_pin); ^~~~~~~~~~~~~~~~~ ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:324:3: note: suggested alternative: ‘PJON_INCLUDE_PORT’ PJON_IO_PULL_DOWN(_input_pin); ^~~~~~~~~~~~~~~~~ PJON_INCLUDE_PORT ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:328:19: error: ‘PJON_MICROS’ was not declared in this scope uint32_t time = PJON_MICROS(); ^~~~~~~~~~~ ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:328:19: note: suggested alternative: ‘MOD_MICRO’ uint32_t time = PJON_MICROS(); ^~~~~~~~~~~ MOD_MICRO ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:330:7: error: ‘PJON_IO_READ’ was not declared in this scope PJON_IO_READ(_input_pin) && ^~~~~~~~~~~~ ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:330:7: note: suggested alternative: ‘PJON_NO_HEADER’ PJON_IO_READ(_input_pin) && ^~~~~~~~~~~~ PJON_NO_HEADER ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:337:4: error: ‘PJON_DELAY_MICROSECONDS’ was not declared in this scope PJON_DELAY_MICROSECONDS((SWBB_BIT_WIDTH / 2) - SWBB_READ_DELAY); ^~~~~~~~~~~~~~~~~~~~~~~ ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:338:8: error: ‘PJON_IO_READ’ was not declared in this scope if(!PJON_IO_READ(_input_pin)) { ^~~~~~~~~~~~ ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:338:8: note: suggested alternative: ‘PJON_NO_HEADER’ if(!PJON_IO_READ(_input_pin)) { ^~~~~~~~~~~~ PJON_NO_HEADER ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h: In member function ‘void SoftwareBitBang::pulse(uint8_t)’: ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:371:4: error: ‘PJON_IO_WRITE’ was not declared in this scope PJON_IO_WRITE(_output_pin, HIGH); ^~~~~~~~~~~~~ ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:371:4: note: suggested alternative: ‘PJON_NO_HEADER’ PJON_IO_WRITE(_output_pin, HIGH); ^~~~~~~~~~~~~ PJON_NO_HEADER ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:372:4: error: ‘PJON_DELAY_MICROSECONDS’ was not declared in this scope PJON_DELAY_MICROSECONDS(SWBB_BIT_SPACER); ^~~~~~~~~~~~~~~~~~~~~~~ ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h: In member function ‘void SoftwareBitBang::set_pin(uint8_t)’: ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:382:3: error: ‘PJON_IO_PULL_DOWN’ was not declared in this scope PJON_IO_PULL_DOWN(pin); ^~~~~~~~~~~~~~~~~ ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:382:3: note: suggested alternative: ‘PJON_INCLUDE_PORT’ PJON_IO_PULL_DOWN(pin); ^~~~~~~~~~~~~~~~~ PJON_INCLUDE_PORT ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h: In member function ‘void SoftwareBitBang::set_pins(uint8_t, uint8_t)’: ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:395:3: error: ‘PJON_IO_PULL_DOWN’ was not declared in this scope PJON_IO_PULL_DOWN(input_pin); ^~~~~~~~~~~~~~~~~ ./hal/transport/PJON/driver/strategies/SoftwareBitBang/SoftwareBitBang.h:395:3: note: suggested alternative: ‘PJON_INCLUDE_PORT’ PJON_IO_PULL_DOWN(input_pin); ^~~~~~~~~~~~~~~~~ PJON_INCLUDE_PORT In file included from ./MySensors.h:395, from examples_linux/mysgw.cpp:82: ./hal/transport/PJON/MyTransportPJON.cpp: In function ‘void _receiver_function(uint8_t*, uint16_t, const PJON_Packet_Info&)’: ./hal/transport/PJON/MyTransportPJON.cpp:56:84: warning: unused parameter ‘packet_info’ [-Wunused-parameter] void _receiver_function(uint8_t *payload, uint16_t length, const PJON_Packet_Info &packet_info) ~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~ In file included from ./MySensors.h:390, from examples_linux/mysgw.cpp:82: ./hal/transport/PJON/driver/PJON.h: In instantiation of ‘uint16_t PJON<Strategy>::update() [with Strategy = SoftwareBitBang; uint16_t = short unsigned int]’: ./hal/transport/PJON/MyTransportPJON.cpp:47:13: required from here ./hal/transport/PJON/driver/PJON.h:932:30: error: ‘PJON_MICROS’ was not declared in this scope (uint32_t)(PJON_MICROS() - packets[i].registration) > ~~~~~~~~~~~^~ ./hal/transport/PJON/driver/PJON.h:932:30: note: suggested alternative: ‘MOD_MICRO’ (uint32_t)(PJON_MICROS() - packets[i].registration) > ~~~~~~~~~~~^~ MOD_MICRO ./hal/transport/PJON/driver/PJON.h: In instantiation of ‘void PJON<Strategy>::begin() [with Strategy = SoftwareBitBang]’: ./hal/transport/PJON/MyTransportPJON.cpp:69:12: required from here ./hal/transport/PJON/driver/PJON.h:149:36: error: ‘PJON_ANALOG_READ’ was not declared in this scope PJON_RANDOM_SEED(PJON_ANALOG_READ(_random_seed) + tx.id); ~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~ ./hal/transport/PJON/driver/PJON.h:149:36: note: suggested alternative: ‘PJON_NO_HEADER’ PJON_RANDOM_SEED(PJON_ANALOG_READ(_random_seed) + tx.id); ~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~ PJON_NO_HEADER ./hal/transport/PJON/driver/PJON.h:149:19: error: ‘PJON_RANDOM_SEED’ was not declared in this scope PJON_RANDOM_SEED(PJON_ANALOG_READ(_random_seed) + tx.id); ~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ./hal/transport/PJON/driver/PJON.h:149:19: note: suggested alternative: ‘PJON_NO_HEADER’ PJON_RANDOM_SEED(PJON_ANALOG_READ(_random_seed) + tx.id); ~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ PJON_NO_HEADER ./hal/transport/PJON/driver/PJON.h: In instantiation of ‘uint16_t PJON<Strategy>::receive(uint32_t) [with Strategy = SoftwareBitBang; uint16_t = short unsigned int; uint32_t = unsigned int]’: ./hal/transport/PJON/MyTransportPJON.cpp:88:35: required from here ./hal/transport/PJON/driver/PJON.h:456:30: error: ‘PJON_MICROS’ was not declared in this scope uint32_t time = PJON_MICROS(); ~~~~~~~~~~~^~ ./hal/transport/PJON/driver/PJON.h:456:30: note: suggested alternative: ‘MOD_MICRO’ uint32_t time = PJON_MICROS(); ~~~~~~~~~~~^~ MOD_MICRO ./hal/transport/PJON/driver/PJON.h: In instantiation of ‘uint16_t PJON<Strategy>::dispatch(const PJON_Packet_Info&, const void*, uint16_t, uint32_t, uint16_t) [with Strategy = SoftwareBitBang; uint16_t = short unsigned int; uint32_t = unsigned int]’: ./hal/transport/PJON/driver/PJON.h:552:10: required from ‘uint16_t PJON<Strategy>::send(uint8_t, const void*, uint16_t, uint8_t, uint16_t, uint16_t) [with Strategy = SoftwareBitBang; uint16_t = short unsigned int; uint8_t = unsigned char]’ ./hal/transport/PJON/MyTransportPJON.cpp:46:85: required from here ./hal/transport/PJON/driver/PJON.h:222:42: error: ‘PJON_MICROS’ was not declared in this scope packets[i].registration = PJON_MICROS(); ~~~~~~~~~~~^~ ./hal/transport/PJON/driver/PJON.h:222:42: note: suggested alternative: ‘MOD_MICRO’ packets[i].registration = PJON_MICROS(); ~~~~~~~~~~~^~ MOD_MICRO make: *** [Makefile:99: build/examples_linux/mysgw.o] Error 1 So it seems more changes are needed. Maybe @Giovanni-Blu-Mitolo or @4ib3r have some information.
• 

  ENC28J60 Ethernet Shield HA reporting !GWT:TSA:ETH FAIL
  ethernetgateway enc28j60 homeassistant • 27 Feb 2022, 02:18 • Ethan Chua   7 Mar 2022, 06:55

  5
  0
  Votes
  5
  Posts
  22
  Views

  7 Mar 2022, 06:55

  Great work @Ethan-Chua, thanks for reporting back.
• 

  Measure multiple voltages
  1 Mar 2022, 20:46 • MasMat   4 Mar 2022, 07:54

  5
  0
  Votes
  5
  Posts
  31
  Views

  4 Mar 2022, 07:54

  Check. Gotta redesign. I'll get optos on the AC-voltages and power the Rpi from the 48/12V ground source. Thanks for confirming my doubts.
• 

  Merging 2 or 3 sketches to one (relays & binary buttons)
  30 Jan 2022, 20:52 • Roschkovsky   12 Feb 2022, 13:33

  4
  0
  Votes
  4
  Posts
  54
  Views

  12 Feb 2022, 13:33

  I modified the code, so the relay status is sent to the HA only at the beginning. I also changed the child id numbers (those for relays now correspond to the pin numbers). The good news is the sensor part for the pushbuttons is now working, but the relays still not. They do not register to the HA in any way. // Enable debug prints to serial monitor #define MY_DEBUG // Enable and select radio type attached //#define MY_RADIO_RF24 //#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 60 // 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 <SPI.h> #include <MySensors.h> #include <Bounce2.h> #define RELAY_22 22 // Arduino Digital I/O pin number for first relay (second on pin+1 etc) #define NUMBER_OF_RELAYS 16 // Total number of attached relays: 4 // Opto Relay Module I was using Active Low - Low (0):ON, High (1): OFF #define RELAY_ON 0 // GPIO value to write to turn on attached relay #define RELAY_OFF 1 // GPIO value to write to turn off attached relay #define FIRST_PIR_ID 1 #define MAX_PIRS 16 const uint8_t pirPin[] = {A0,A1,A2,A3,A4,A5,A6,A7,A8,A9,A10,A11,A12,A13,A14,A15}; // switch around pins to your desire Bounce debouncer[MAX_PIRS]; MyMessage pirMsg(0, V_TRIPPED); bool oldPir[MAX_PIRS] = {false}; bool initialValueSent = false; //Init MyMessage for Each Child ID MyMessage msg22(22, V_LIGHT); MyMessage msg23(23, V_LIGHT); MyMessage msg24(24, V_LIGHT); MyMessage msg25(25, V_LIGHT); MyMessage msg26(26, V_LIGHT); MyMessage msg27(27, V_LIGHT); MyMessage msg28(28, V_LIGHT); MyMessage msg29(29, V_LIGHT); MyMessage msg30(30, V_LIGHT); MyMessage msg31(31, V_LIGHT); MyMessage msg32(32, V_LIGHT); MyMessage msg33(33, V_LIGHT); MyMessage msg34(34, V_LIGHT); MyMessage msg35(35, V_LIGHT); MyMessage msg36(36, V_LIGHT); MyMessage msg37(37, V_LIGHT); void before() { for (int sensor=22, pin=RELAY_22; sensor<=NUMBER_OF_RELAYS;sensor++, pin++) { // Then set relay pins in output mode pinMode(pin, OUTPUT); // Set relay to last known state (using eeprom storage) digitalWrite(pin, loadState(sensor)?RELAY_ON:RELAY_OFF); } } void setup() { for (uint8_t i = 0; i < MAX_PIRS; i++) { debouncer[i] = Bounce(); // initialize debouncer debouncer[i].attach(pirPin[i], INPUT_PULLUP); debouncer[i].interval(5); oldPir[i] = debouncer[i].read(); } wait(5000); Serial.println("Sending initial value"); send(msg22.set(loadState(22)?RELAY_OFF:RELAY_ON),true); wait(1000); send(msg23.set(loadState(23)?RELAY_OFF:RELAY_ON),true); wait(1000); send(msg24.set(loadState(24)?RELAY_OFF:RELAY_ON),true); wait(1000); send(msg25.set(loadState(25)?RELAY_OFF:RELAY_ON),true); wait(1000); send(msg26.set(loadState(26)?RELAY_OFF:RELAY_ON),true); wait(1000); send(msg27.set(loadState(27)?RELAY_OFF:RELAY_ON),true); wait(1000); send(msg28.set(loadState(28)?RELAY_OFF:RELAY_ON),true); wait(1000); send(msg29.set(loadState(29)?RELAY_OFF:RELAY_ON),true); wait(1000); send(msg30.set(loadState(30)?RELAY_OFF:RELAY_ON),true); wait(1000); send(msg31.set(loadState(31)?RELAY_OFF:RELAY_ON),true); wait(1000); send(msg32.set(loadState(32)?RELAY_OFF:RELAY_ON),true); wait(1000); send(msg33.set(loadState(33)?RELAY_OFF:RELAY_ON),true); wait(1000); send(msg34.set(loadState(34)?RELAY_OFF:RELAY_ON),true); wait(1000); send(msg35.set(loadState(35)?RELAY_OFF:RELAY_ON),true); wait(1000); send(msg36.set(loadState(36)?RELAY_OFF:RELAY_ON),true); wait(1000); send(msg37.set(loadState(37)?RELAY_OFF:RELAY_ON),true); wait(1000); Serial.println("Sending initial value: Completed"); wait(5000); } void presentation() { // Send the sketch version information to the gateway and Controller sendSketchInfo("Combo_22-37_i_A0-A15", "1.0"); for (int sensor=22, pin=RELAY_22; sensor<=NUMBER_OF_RELAYS;sensor++, pin++) { // Register all sensors to gw (they will be created as child devices) present(sensor, S_LIGHT); for (int i = 0; i < MAX_PIRS; i++) { //i < numSensors && present(FIRST_PIR_ID + i, S_MOTION); } } } void loop() { bool pir[MAX_PIRS]; for (uint8_t i = 0; i < MAX_PIRS; i++) { debouncer[i].update(); pir[i] = debouncer[i].read(); if (pir[i] != oldPir[i]) { send(pirMsg.setSensor(FIRST_PIR_ID + i).set( pir[i])); // Send tripped value to gw oldPir[i] = pir[i]; } } } void receive(const MyMessage &message) { Serial.println("=============== Receive Start ======================="); if (message.isAck()) { Serial.println(">>>>> ACK <<<<<"); Serial.println("This is an ack from gateway"); Serial.println("<<<<<< ACK >>>>>>"); } // We only expect one type of message from controller. But we better check anyway. if (message.type==V_LIGHT) { Serial.println(">>>>> V_LIGHT <<<<<"); if (!initialValueSent) { Serial.println("Receiving initial value from controller"); initialValueSent = true; } // Update relay state to HA digitalWrite(message.sensor-1+RELAY_22, message.getBool()?RELAY_ON:RELAY_OFF); switch (message.sensor) { case 22: Serial.print("Incoming change for sensor 1"); send(msg22.set(message.getBool()?RELAY_OFF:RELAY_ON)); break; case 23: Serial.print("Incoming change for sensor 2"); send(msg23.set(message.getBool()?RELAY_OFF:RELAY_ON)); break; case 24: Serial.print("Incoming change for sensor 3"); send(msg24.set(message.getBool()?RELAY_OFF:RELAY_ON)); break; case 25: Serial.print("Incoming change for sensor 4"); send(msg25.set(message.getBool()?RELAY_OFF:RELAY_ON)); break; case 26: Serial.print("Incoming change for sensor 5"); send(msg26.set(message.getBool()?RELAY_OFF:RELAY_ON)); break; case 27: Serial.print("Incoming change for sensor 6"); send(msg27.set(message.getBool()?RELAY_OFF:RELAY_ON)); break; case 28: Serial.print("Incoming change for sensor 7"); send(msg28.set(message.getBool()?RELAY_OFF:RELAY_ON)); break; case 29: Serial.print("Incoming change for sensor 8"); send(msg29.set(message.getBool()?RELAY_OFF:RELAY_ON)); break; case 30: Serial.print("Incoming change for sensor 9"); send(msg30.set(message.getBool()?RELAY_OFF:RELAY_ON)); break; case 31: Serial.print("Incoming change for sensor 10"); send(msg31.set(message.getBool()?RELAY_OFF:RELAY_ON)); break; case 32: Serial.print("Incoming change for sensor 11"); send(msg32.set(message.getBool()?RELAY_OFF:RELAY_ON)); break; case 33: Serial.print("Incoming change for sensor 12"); send(msg33.set(message.getBool()?RELAY_OFF:RELAY_ON)); break; case 34: Serial.print("Incoming change for sensor 13"); send(msg34.set(message.getBool()?RELAY_OFF:RELAY_ON)); break; case 35: Serial.print("Incoming change for sensor 14"); send(msg35.set(message.getBool()?RELAY_OFF:RELAY_ON)); break; case 36: Serial.print("Incoming change for sensor 15"); send(msg36.set(message.getBool()?RELAY_OFF:RELAY_ON)); break; case 37: Serial.print("Incoming change for sensor 16"); send(msg37.set(message.getBool()?RELAY_OFF:RELAY_ON)); break; default: Serial.println("Default Case: Receiving Other Sensor Child ID"); break; } // Store state in Arduino eeprom saveState(message.sensor, message.getBool()); Serial.print("Saved State for sensor: "); Serial.print( message.sensor); Serial.print(", New status: "); Serial.println(message.getBool()); Serial.println("<<<<<< V_LIGHT >>>>>>"); } Serial.println("=============== Receive END ======================="); } No error logs in HA, not a sign of relay entities in the json file.
• 

  USB Serial missing on Maple Mini
  stm32 usb serial • 11 Feb 2022, 20:56 • canyouhearmenow   11 Feb 2022, 20:56

  1
  0
  Votes
  1
  Posts
  15
  Views

  No one has replied

• 

  Can a sensor "get lost" between a GW and a repeater?
  repeater • 4 Feb 2022, 15:53 • bgunnarb   5 Feb 2022, 08:39

  4
  0
  Votes
  4
  Posts
  24
  Views

  5 Feb 2022, 08:39

  Thanks to @electrik and @mfalkvidd for your answers. I will try next time I have the opportunity. Currently the sensor is 400 km away from home.
• 

  [SOLVED] RFM95 Node with gateway no parents found (But looks like messages are being sent)
  21 Jan 2022, 19:49 • VonJoost   31 Jan 2022, 12:44

  8
  0
  Votes
  8
  Posts
  66
  Views

  31 Jan 2022, 12:44

  @VonJoost Yes, naturally. Bad code will result in bad result. I'm trying to understand where the bad code came from.
• 

  Having problems with RFM69HW in Raspberry Pi
  6 Jun 2021, 19:11 • frapell   25 Jan 2022, 05:54

  3
  0
  Votes
  3
  Posts
  46
  Views

  25 Jan 2022, 05:54

  @frapell I am having the same issue with Raspberry PI zero W, I get an awful range (less than 2 meters) with the default build values. It seems the default power setting for RFM69HCW are 5dB. Also, for RPI Zero W it seems the 3.3V pin supplies only 50mA and I have also added an extra 3.3V regulator (should not be the case for RPI3+). I have now compiled the gateway using the following and got a better range indoors: ./configure --my-transport=rfm69 --my-rfm69-frequency=915 --my-is-rfm69hcw --my-gateway=mqtt --my-controller-ip-address=192.168.1.41 --my-mqtt-publish-topic-prefix=mysensors-out --my-mqtt-subscribe-topic-prefix=mysensors-in --my-mqtt-client-id=mygateway1 --extra-cxxflags="-DMY_RFM69_MAX_POWER_LEVEL_DBM=20 -DMY_RFM69_TX_POWER_DBM=20 -DMY_DEBUG_VERBOSE_RFM69" Look for "LEVEL" in the logs to check that the power level is the correct one. I don't know how mysensors handles the power range (expected to see it increasing it by itself no answers, but I could not get it working otherwise). Maybe it helps. Best Regards, Costa
• 

  Sketch seemingly "hangs" while executing
  stepper motor scover hanging • 28 Nov 2021, 03:46 • Ethan Chua   20 Jan 2022, 11:06

  4
  0
  Votes
  4
  Posts
  36
  Views

  20 Jan 2022, 11:06

  Hi there, Thanks for the replies! It seemed that the culprit was my stupidity. I forgot that the AccelStepper library's stepper.moveTo() function's argument was the absolute rather than the relative position of the stepper motor. As such my code would end up trying to push the stepper motor to extreme values (because I thought I needed to input a negative to move to the left etc) and this caused weird things to happen, most likely this crashing as well. In any case I'm glad the issue has been resolved. @electrik the programme takes up 72% of storage space and 64% of dynamic memory, so I will definitely cut out the Serial logs once I am done debugging. @mfalkvidd yikes you're right it seems I had forgotten to include the function to run the steppers. Anyways for reference sake I'll drop my final code here (from the last I tested it is working but with the minor issue of the motors having to travel to the end of their move before it can reverse direction, which I have no clue why it happens but I don't mind it): #include <AccelStepper.h> const byte dirPin1 = A0; const byte stepPin1 = A1; const byte enPin1 = A2; const byte dirPin2 = A3; const byte stepPin2 = A4; const byte enPin2 = A5; const byte dirPin3 = 4; const byte stepPin3 = 3; const byte enPin3 = 8; const byte dirPin4 = 7; const byte stepPin4 = 6; const byte enPin4 = 5; const bool enOne = true, enTwo = true, enThree = true, enFour = true; const bool dirOne = true, dirTwo = true, dirThree = true, dirFour = true; const int stepmmOne = 160, stepmmTwo = 160, stepmmThree = 160, stepmmFour = 160; const byte endstopup = A6, endstopdown = A7; //long timer = 0; #define motorInterfaceType 1 AccelStepper stepperOne(motorInterfaceType, stepPin1, dirPin1); AccelStepper stepperTwo(motorInterfaceType, stepPin2, dirPin2); AccelStepper stepperThree(motorInterfaceType, stepPin3, dirPin3); AccelStepper stepperFour(motorInterfaceType, stepPin4, dirPin4); #define MY_DEBUG #define MY_RADIO_RF24 #include <MySensors.h> #define CHILD_ID 0 //#define MY_TRANSPORT_WAIT_READY_MS 1000 int currentShutterLevel = 0, desiredShutterLevel = 0; enum currentState { STOP, UP, DOWN, }; static int currentState = STOP; //the initial state is STOP because it is not moving boolean requested = false; boolean isAlrMoving = false; boolean initialValueSent = false; boolean receivedStop = false; int totalDist = 150; //in mm int stepsPerMM = 160; int currentSteps = 0; int desiredSteps = 0; int stepsToMove = 0, oldStepsToMove = 0; int levelsToMove = 0; int levelsToGo = 0; int savedShutterLevel = 0; int stepSpeed = 50; int stepAccel = 1000; MyMessage upMessage(CHILD_ID, V_UP); MyMessage downMessage(CHILD_ID, V_DOWN); MyMessage stopMessage(CHILD_ID, V_STOP); MyMessage percMessage(CHILD_ID, V_PERCENTAGE); void sendState(){ #ifdef MY_DEBUG Serial.println("Sending states: "); Serial.print("UP: "); Serial.println(currentState == UP); Serial.print("DOWN: "); Serial.println(currentState == DOWN); Serial.print("STOP: "); Serial.println(currentState == STOP); Serial.print("PERC: "); Serial.println(currentShutterLevel); #endif send(upMessage.set(currentState == UP)); send(downMessage.set(currentState == DOWN)); send(stopMessage.set(currentState == STOP)); send(percMessage.set(desiredShutterLevel)); } void setup() { Serial.begin(115200); stepperOne.setEnablePin(enPin1); stepperOne.setPinsInverted(dirOne,false,enOne); stepperOne.setMaxSpeed(stepSpeed); stepperOne.setAcceleration(stepAccel); //stepperOne.setSpeed(50); stepperTwo.setEnablePin(enPin2); stepperTwo.setPinsInverted(dirTwo,false,enTwo); stepperTwo.setMaxSpeed(stepSpeed); stepperTwo.setAcceleration(stepAccel); //stepperTwo.setSpeed(50); stepperThree.setEnablePin(enPin3); stepperThree.setPinsInverted(dirThree,false,enThree); stepperThree.setMaxSpeed(stepSpeed); stepperThree.setAcceleration(stepAccel); //stepperThree.setSpeed(50);; stepperFour.setEnablePin(enPin4); stepperFour.setPinsInverted(dirFour,false,enFour); stepperFour.setMaxSpeed(stepSpeed); stepperFour.setAcceleration(stepAccel); //stepperFour.setSpeed(50); pinMode(endstopup, INPUT_PULLUP); pinMode(endstopdown, INPUT_PULLUP); } void presentation() { sendSketchInfo("Hydroponics Stepper Motors", "1.0"); wait(1000); present(CHILD_ID, S_COVER); } void loop() { /*if(!initialValueSent){ #ifdef MY_DEBUG Serial.println("Sending initial values!"); #endif sendState(); initialValueSent = true; } */ //requesting percentage of height if(!requested){ request(CHILD_ID, V_PERCENTAGE); #ifdef MY_DEBUG Serial.println("Requesting initial position of lights"); #endif } if(currentShutterLevel != desiredShutterLevel || receivedStop){ //allow the setting of new positions if a STOP is called //currentShutterLevel and desiredShutterLevel are used to detect the change in parameters if(!isAlrMoving){ //this ensures the following code is only executed once enableAllSteppers(); stepsToMove = map(desiredShutterLevel,0,100,0,totalDist*stepsPerMM); Serial.print("Moving to: "); Serial.println(stepsToMove); moveAllSteppers(stepsToMove); isAlrMoving = true; sendState(); } if(stepperOne.distanceToGo() != 0){ } else{ currentShutterLevel = desiredShutterLevel; currentState = STOP; sendState(); disableAllSteppers(); } receivedStop = false; }else{ //if desired and current are the same - either because there is no movement or when we call STOP, then check to see //if there was a change in the state of STOP. If there was then send the state. if(receivedStop){ sendState(); receivedStop = false; } disableAllSteppers(); } runAllSteppers(); if(analogRead(endstopup)>10 && currentState == UP){ //if the top endstop is triggered and the shutter was moving up #ifdef MY_DEBUG Serial.println("Top Endstop has been activated!"); #endif receivedStop = true; setCurrentPositionofAll(100); desiredShutterLevel = 100; currentShutterLevel = 100; currentState = STOP; } else if(analogRead(endstopdown)>10 && currentState == DOWN){ //if the bottom endstop is triggered and the shutter was moving down #ifdef MY_DEBUG Serial.println("Bottom Endstop has been activated!"); #endif receivedStop = true; setCurrentPositionofAll(0); desiredShutterLevel = 0; currentShutterLevel = 0; currentState = STOP; } } void receive(const MyMessage &message) { #ifdef MY_DEBUG Serial.print("Received a message from sensor: "); Serial.println(String(message.sensor)); Serial.print("Message type: "); Serial.println(String(message.type)); #endif isAlrMoving = false; //since if we receive a message it means that we need to do something, we can allow the position to be reset if(message.sensor == CHILD_ID){ switch(message.type){ case V_UP: desiredShutterLevel = 100; currentState = UP; #ifdef MY_DEBUG Serial.println("Shutter State is UP"); Serial.print("currentShutterLevel = "); Serial.println(currentShutterLevel); Serial.print("desiredShutterLevel = "); Serial.println(desiredShutterLevel); #endif break; case V_DOWN: desiredShutterLevel = 0; currentState = DOWN; #ifdef MY_DEBUG Serial.println("Shutter State is DOWN"); Serial.print("currentShutterLevel = "); Serial.println(currentShutterLevel); Serial.print("desiredShutterLevel = "); Serial.println(desiredShutterLevel); #endif break; case V_STOP: receivedStop = true; //allow the loop to send states once currentShutterLevel = map(stepperOne.currentPosition(),-totalDist*stepsPerMM,totalDist*stepsPerMM,-100,100); //update the current state with the state that the stepper is actually at desiredShutterLevel = currentShutterLevel; //stop the steppers currentState = STOP; #ifdef MY_DEBUG Serial.print("Halt called! Stopping all motors at pos: "); Serial.println(currentShutterLevel); #endif break; case V_PERCENTAGE: int pos = message.getInt(); if(pos > 100) pos = 100; if(pos < 0) pos = 0; if(!requested){ currentShutterLevel = pos; desiredShutterLevel = pos; setCurrentPositionofAll(map(pos,0,100,0,totalDist*stepsPerMM)); #ifdef MY_DEBUG Serial.print("Initialized! Current Shutter Level Set to: "); Serial.println(currentShutterLevel); #endif requested = true; } else{ desiredShutterLevel = pos; } currentState = (desiredShutterLevel > currentShutterLevel)?UP:DOWN; #ifdef MY_DEBUG Serial.print("Shutter State is PERC = "); Serial.println(desiredShutterLevel); Serial.print("currentShutterLevel = "); Serial.println(currentShutterLevel); Serial.print("desiredShutterLevel = "); Serial.println(desiredShutterLevel); #endif break; } } #ifdef MY_DEBUG Serial.print("Exiting this message with currentState = "); Serial.println(currentState); #endif } void enableAllSteppers(void){ stepperOne.enableOutputs(); stepperTwo.enableOutputs(); stepperThree.enableOutputs(); stepperFour.enableOutputs(); } void moveAllSteppers(int steps){ stepperOne.moveTo(steps); stepperTwo.moveTo(steps); stepperThree.moveTo(steps); stepperFour.moveTo(steps); } void runAllSteppers(void){ stepperOne.run(); stepperTwo.run(); stepperThree.run(); stepperFour.run(); } void disableAllSteppers(void){ stepperOne.disableOutputs(); stepperTwo.disableOutputs(); stepperThree.disableOutputs(); stepperFour.disableOutputs(); } void setCurrentPositionofAll(int pos){ stepperOne.setCurrentPosition(pos); stepperTwo.setCurrentPosition(pos); stepperThree.setCurrentPosition(pos); stepperFour.setCurrentPosition(pos); } Thanks so much for your patience and suggestions!
• 

  Sporadic issues finding parent gateway
  4 Sept 2021, 09:19 • Ethan Chua   20 Jan 2022, 10:43

  3
  1
  Votes
  3
  Posts
  32
  Views

  20 Jan 2022, 10:43

  Hi there, Thanks for your response! It turns out I needed a better 3.3V power supply because I was powering the NRF24L01 from the Nano's 3.3V pin which is derived from the CH340 USB-Serial converter and is not ideal. Upgrading the supply to an AMS1117 3.3V supply solved the issue completely! Sorry for the late reply and thanks so much for your tips! Will try them out if issues crop up in the future.
• 

  Adafruit RFM69 Bonnet not working
  25 Feb 2020, 03:46 • paulsp   12 Jan 2022, 11:09

  14
  0
  Votes
  14
  Posts
  138
  Views

  12 Jan 2022, 11:09

  @FlyingSaucrDude What great timing (for me anyway), only this week I purchased the Adafruit RFM95 Bonnet version, and this thread is the only thing returned in a quick search. Your solution works for RFM95 also. I didn't need to comment out the code that prevented toggling the CS_PIN, but I'm using the development version as the main branch dose not seem to build on Pi OS Bullseye. ./configure --my-transport=rfm95 --my-rfm95-frequency=868 --my-gateway=ethernet --my-port=5003 --my-rfm95-cs-pin=26 --my-rfm95-irq-pin=15 --extra-cxxflags="-DMY_RFM95_RST_PIN=22" --spi-spidev-device=/dev/spidev0.1 --spi-driver=SPIDEV Thanks to your post I got this working in a few min of trying, would have taken me much longer otherwise, so thank you for posting to an ancient thread.
• 

  Gateway stopped "seeing" the sensors
  4 Jan 2022, 23:14 • skom   10 Jan 2022, 00:27

  3
  0
  Votes
  3
  Posts
  34
  Views

  10 Jan 2022, 00:27

  I have an almost identical issue with me ESP MQTT gateway no longer connecting to nodes. Similar issues to start with in that it was good for a number of months then would stop, restart ok, then multiple restarts to begin working. I have now resorted to changing out the 24RF01 module and the ESP to try and locate the issue. Will let you know how I get on.
• 

  Multiple messages often fail
  27 Dec 2021, 21:42 • BlueArrow   28 Dec 2021, 10:36

  4
  1
  Votes
  4
  Posts
  53
  Views

  28 Dec 2021, 10:36

  Thank you for swift reply. Given the problem takes place in ~20% of cases it seems the problem is really caused by forcing echo. Since MySensors can cope with 80% of triple messages I believe cutting the number of messages by half would solve the problem. I do not observe issues during presentation though my heaviest node has 9 children. It also seems to be a better way than engaging in multicast feature. So the problem becomes more Home Assistant related... Given the ack (Enhaced Shockburst) mechanism, forcing echo seems to be redundant. Instead, the failure of message sending should be reported by the gateway - is there any mechanism possible? I only noticed the send() function returns bool as an advice but did not notice an equivalent returning feedback from gateway via ehternet/serial/mqtt. The documentation says there is an 'optimistic' option, where "Home Assistant will assume any requested changes (turn on light, open cover) are applied immediately without waiting for feedback from the node", so I believe HA does not require echo. Unfortunately when trying to set that nothing really changes , and I get the following HA log: optimistic option for mysensors is deprecated. Please remove optimistic from your configuration file I will post a suggestion to HA forum to restore this option, unless you know a (good) reason for removing optimistic from HA?
• 

  can't get D1 mini gateway sketch to work
  27 Dec 2021, 13:29 • maddhin   27 Dec 2021, 14:38

  4
  0
  Votes
  4
  Posts
  13
  Views

  27 Dec 2021, 14:38

  I fixed the issue by using the ESP8266 2.7.4 board software and installing https://github.com/espressif/esptool/archive/v3.0.zip and https://github.com/pyserial/pyserial/archive/v3.4.zip and replacing the esptool and pyserial folders in ~/Library/Arduino15/packages/esp8266/hardware/esp8266/2.7.4/tools/ If anybody has a fix for 3.0.2, it would be very much welcome!
• 

  Gateway fails with `!TSF:MSG:SIGN VERIFY FAIL` after period of time
  17 Dec 2021, 16:04 • Elin Angelow   22 Dec 2021, 15:52

  3
  0
  Votes
  3
  Posts
  58
  Views

  22 Dec 2021, 15:52

  another update: another (same) board found, and tested... problem persists. "Verify fail" starts between 670 and 690 message received ... it looks like something get full and nonce is not included in hmac generation.
• 

  This topic is deleted!
  17 Dec 2021, 15:51 • Elin Angelow   17 Dec 2021, 15:51

  1
  0
  Votes
  1
  Posts
  6
  Views

  No one has replied

• 

  Unable to read data from my (Linky) electricity meter
  20 Nov 2021, 23:58 • Encrypt   28 Nov 2021, 22:42

  3
  0
  Votes
  3
  Posts
  51
  Views

  28 Nov 2021, 22:42

  Hello everyone! Thank you @mfalkvidd for your answer. I finally found the issue... Timing is particularly critical when reading UART and using the internal RC oscillator isn't a good idea... at all. Especially knowing that its frequency varies (quite a lot in my opinion) with temperature: (Page 274 of the ATMEGA328P datasheet available here: https://ww1.microchip.com/downloads/en/DeviceDoc/Atmel-7810-Automotive-Microcontrollers-ATmega328P_Datasheet.pdf) So, I changed the fuses of the ATMEGA328P to use an external 8 MHz crystal oscillator and now everything works perfectly! Regarding the code, I've initialized the "Serial" object with the configuration SERIAL_7E1, it works as expected! Cheers! Encrypt
• 

  This topic is deleted!
  20 Nov 2021, 23:00 • perIpI   20 Nov 2021, 23:00

  1
  0
  Votes
  1
  Posts
  1
  Views

  No one has replied

• 

  send many variables in one messages
  13 Nov 2021, 08:55 • Marcin   13 Nov 2021, 08:55

  1
  0
  Votes
  1
  Posts
  26
  Views

  No one has replied

• 

  Problems ethernet GW with ESP8266- NodeMcu V3.4
  30 Oct 2021, 21:42 • perIpI   7 Nov 2021, 09:47

  11
  0
  Votes
  11
  Posts
  102
  Views

  7 Nov 2021, 09:47

  I also edited according to @Yveaux 's workaround and it works! I found however that in order to get the MQTT GW to listen to messages and forward them to the broker, I had to set wait(2000); in the void loop() If I set wait(0) the GW started but did not listen to messages. If I set wait(100); the GW started spamming the broker with the presentation message. Again, a big thank you to everybody involved. "Now we are cooking with gas again!"
• 

  MYSBootloader does not work
  29 Oct 2021, 12:20 • nexus1212   1 Nov 2021, 16:55

  6
  0
  Votes
  6
  Posts
  53
  Views

  1 Nov 2021, 16:55

  @nexus1212 You're using a 3V Arduino. It looks like all the patterns are correct, but it's just not getting things right. A lot of the unprintable characters in ASCII are at the start of the table, so I'm thinking maybe you have a serial connection that is expecting 5V as the 'high' voltage and what it's actually seeing is so borderline that it's not always registering correctly. So look if there's a setting on whatever you're using to read the serial data to set it to be 3V compatible. (Maybe a physical jumper on the board?) It's so close to getting it that I bet it's something super simple like that and your Arduino is really doing it's job pretty well.
• 

  Node doesn't recieve message from gateway
  23 Oct 2021, 17:54 • keczejo   28 Oct 2021, 14:51

  12
  0
  Votes
  12
  Posts
  80
  Views

  28 Oct 2021, 14:51

  I changed node arduino to mega and it worked first try. Thanks for help
• 

  Problem with Recursive calls on signed node (Solved)
  12 Oct 2021, 12:41 • Nigel31   27 Oct 2021, 21:40

  7
  1
  Votes
  7
  Posts
  84
  Views

  27 Oct 2021, 21:40

  @Nigel31 Maybe it's best to use the wait outside a while loop. With this I mean. Right now you're calling a function that does the resends within the same while loop - so basically it blocks the main loop. The only thing I can think of, is that MySensors doesn't get time to execute all it needs to do before you call the next request. So if you'd rewrite the code a little bit so it does all the requests in different execution of the main loop() method. It might work much better. As I do it in a MessageQueue I've written and don't have the problems you have. Also sometimes it takes a while before a node starts using the repeater. If it's close enough to the gateway to get some responses. Than - if understand correctly - it will not start using the repeater until the repeater sees x-time of failures.
• 

  problem with button and mqtt after restart gateway
  12 Oct 2021, 14:52 • jax123   12 Oct 2021, 14:52

  2
  0
  Votes
  2
  Posts
  18
  Views

  No one has replied

• 

  can use delay() on an ESP32 gateway ?
  24 Sept 2021, 14:25 • rumoldus   25 Sept 2021, 15:06

  3
  0
  Votes
  3
  Posts
  26
  Views

  25 Sept 2021, 15:06

  One approach would be to create a separate task on the ESP32 that takes care of testing this sensor, than the gateway is not affected.
• 

  How to get non mysensor node (mqtt/ethernet) info to a my sensor node.
  15 Sept 2021, 09:44 • gav   19 Sept 2021, 18:22

  3
  0
  Votes
  3
  Posts
  47
  Views

  19 Sept 2021, 18:22

  @BearWithBeard Thanks. That sounds like what I was thinking. Makes it clearer though.
• 

  My rPi gateway suddenly stopped working, no idea what else to try...
  5 Sept 2021, 00:46 • frapell   11 Sept 2021, 21:15

  20
  0
  Votes
  20
  Posts
  107
  Views

  11 Sept 2021, 21:15

  mfalkvidd gave you a great link, but if you ever need to see any possible choices, you can run ./configure --help and it will show you. The extra flags section is one thing (of many) that it says. Actually, this is very timely for me, as I'm trying to troubleshoot my own radio issues, so I'll use those extra two flags that you mentioned and see what they say. Thank you!
• 

  Is there a timing issue with "faster" platforms?
  18 Aug 2021, 09:36 • Nigel31   25 Aug 2021, 10:29

  8
  0
  Votes
  8
  Posts
  81
  Views

  25 Aug 2021, 10:29

  @Njwyborn sorry, I don't know. If the stack is called recursively, something is seriously wrong and behavior is undefined I guess.
• 

  WeMos D1 Mini Gateway + Relay
  22 Aug 2021, 14:27 • anderBAKE   24 Aug 2021, 16:14

  10
  0
  Votes
  10
  Posts
  58
  Views

  24 Aug 2021, 16:14

  Also posting the wiring helps others to help you. Fitzing is easy for this task
• 

  Node doesn't receive data from RPI MQTT Gateway
  4 Aug 2021, 22:08 • cvdenzen   22 Aug 2021, 11:46

  15
  0
  Votes
  15
  Posts
  123
  Views

  22 Aug 2021, 11:46

  @mfalkvidd Thank you!
• 

  RFID and NRF24L01 Wireless Network Coding Issues
  11 Apr 2016, 20:57 • codergirl56   22 Aug 2021, 07:15

  23
  0
  Votes
  23
  Posts
  9.3k
  Views

  22 Aug 2021, 07:15

  @Ispandy, let resume some things because I'm lost You copied the sketch code from node 3 (= correctly running node with cardscans and remote control from openhab) to node 50 and you adapted the node id. This same sketch on node 50 is running correctly with cardscans but not with openhab? Correct? If above is correct: somewhere your openhab configuration for this node 50 is not correct. You say that node 50 is never receiving the openhab command, so there is a problem with your openhab configuration for node 50.
• 

  Node can't reconnect after reset
  8 Aug 2021, 23:38 • TheStaticTurtle   15 Aug 2021, 17:11

  4
  0
  Votes
  4
  Posts
  40
  Views

  15 Aug 2021, 17:11

  I am using the TMRh20 libraries (not the MySensors library) and have the same problem. I'm pretty sure that there are interrupts that are not being reset. One of my other symptoms is that when I try to load or reload a program, the program doesn't start. I have a program program that I run that works most of the time and gets me to the point of being able to reprogram the Arduino //cli(); // disable all interrupts WDTCSR = B00011000; // set watchdog timer into configuration mode WDTCSR = 0; // turn off watchdog time interrupt. //sei(); // allow interupts I use this technique to load the program: write program use Tool-->port and set the port on the device, press and hold reset button <ctl>+u or click on upload icon when compiling gas gauge is almost complete, release the reset button. You may have to do 3)-5) several times. You could put: Serial.begin(9600); Serial.println("WDT reset"); at the end of the program to know that the device got reset. I hope this helps you. I, too, would like something a little more controllable. OSD
• 

  Unable to add node - more than 2
  14 Aug 2021, 15:27 • pw44   15 Aug 2021, 06:10

  7
  0
  Votes
  7
  Posts
  22
  Views

  15 Aug 2021, 06:10

  @pw44 MY_DEBUG is usually enough. https://www.mysensors.org/build/debug#enabling-debug-and-monitoring-the-logs and https://forum.mysensors.org/topic/666/read-this-first-it-could-save-you-a-lot-of-time/ can be useful.
• 

  Help or advice on getting node to RECEIVE data for text child objects
  14 Aug 2021, 12:53 • Nigel31   14 Aug 2021, 12:56

  4
  0
  Votes
  4
  Posts
  27
  Views

  14 Aug 2021, 12:56

  Upgrading to 2.3.2 has helped somewhat
• 

  This topic is deleted!
  13 Aug 2021, 12:02 • benhub   13 Aug 2021, 12:02

  1
  0
  Votes
  1
  Posts
  1
  Views

  No one has replied

• 

  Node inclusion problem.
  1 Aug 2021, 14:48 • pw44   12 Aug 2021, 20:34

  17
  0
  Votes
  17
  Posts
  122
  Views

  12 Aug 2021, 20:34

  @mfalkvidd may this problem be related with eeprom stored vars? i will clear the eeproms and flash gatewayand nodes again.
• 

  !TSF vs ?TSF - what do they represent?
  12 Aug 2021, 10:15 • bcdaus   12 Aug 2021, 17:09

  2
  0
  Votes
  2
  Posts
  29
  Views

  12 Aug 2021, 17:09

  @bcdaus from what I understand, ! means failed while ? means unknown. Unknown is used when the radio hardware does not support ack at all (so there is no way to know whether the message was received by the next node) https://www.mysensors.org/apidocs-beta/group__MyTransportgrp.html has some documentation.
• 

  Problem with running MySensors gateway on NanoPi NEO with Armbian
  rs485 nanopi armbian • 27 Jul 2021, 22:59 • mariuszjozala   11 Aug 2021, 08:05

  4
  0
  Votes
  4
  Posts
  53
  Views

  11 Aug 2021, 08:05

  Hi @mariuszjozala , Thank you for reporting back. Glad that it works now! In my eyes, the good documentation (and availability of LTS options) is one of the really big plus points of the NanoPi/FriendlyARM products. I did save a local copy of their wiki, just in case it ever disappeared, because these references are really helpful. Best regards pragtich
• 

  Radio stops working
  10 Aug 2021, 15:48 • jlb   10 Aug 2021, 18:23

  2
  0
  Votes
  2
  Posts
  18
  Views

  10 Aug 2021, 18:23

  @jlb said in Radio stops working: How to make the node detect this radio problem ? I don't think there is a function to do this, but maybe someone else can help with that. How do I get my sketch to do a cold restart of the radio ? It would be good to see how you wired this all up - a hand drawn sketch or fritzing would do. I suspect that by modifying the way power is applied may need arjusting and come capacitors may need adding - You can reboot by using a hardware watchdog circuit (web search for it).
• 

  Compile RooDe software with PlatfromIO
  6 Aug 2021, 08:04 • Mie Miee   6 Aug 2021, 08:04

  1
  0
  Votes
  1
  Posts
  13
  Views

  No one has replied

• 

  Sensebender. Still same problems with NEW board and radio
  10 Jun 2021, 15:01 • Nigel31   3 Aug 2021, 08:55

  7
  0
  Votes
  7
  Posts
  60
  Views

  3 Aug 2021, 08:55

  Question. Would using the "ClearEepromConfig" sketch, do anything nasty to the sencebender gateway eeprom?
• 

  Is there a "standard" way to terminate a sleep time, after waking by an interrupt?
  28 Jul 2021, 09:16 • Nigel31   1 Aug 2021, 21:38

  15
  0
  Votes
  15
  Posts
  118
  Views

  1 Aug 2021, 21:38

  @Yveaux Yes, that is what the sencebender gateway was for, so I could start with an easily swappable item, and the core of the network, however you might remember that I am having issues with sencebender gateway.. with no solution in sight. link text
• 

  Will serial gateway work with 3.3 V Arduino Pro Mini?
  gateway rfm69 pro mini • 21 May 2021, 08:16 • Thomas433   27 Jul 2021, 18:33

  5
  0
  Votes
  5
  Posts
  59
  Views

  27 Jul 2021, 18:33

  @TheoL Thanks for responding and sorry for my late reply. I finally got an Arduino Nano working as a gateway with RFM69. It required new/different logic converters as the ones I had apparently were not working correctly. I can give the RFM69 3.3V power from the Nano, but as the Nano has 5V logic and the RFM69 cannot handle 5V logic as input (NSS, SCK, MOSI) , the logic converters are needed to protect the RFM69 module as also stated in the MySensors radio guide. I must say that using NRF24 was much easier than using RFM69, but I will stick with RFM69 (433 MHz) for range reasons.
• 

  RS485, no communication
  12 Jul 2021, 10:17 • vdomos   22 Jul 2021, 08:45

  9
  0
  Votes
  9
  Posts
  105
  Views

  22 Jul 2021, 08:45

  This solved my issue!! Thank you!!
• 

  Mysensors libray error - esp8266
  14 Jul 2021, 14:07 • pw44   14 Jul 2021, 18:24

  2
  0
  Votes
  2
  Posts
  27
  Views

  14 Jul 2021, 18:24

  @pw44 downgraded ESP from 3.0.1 to 2.7.4 and issue is gone.
• 

  Cannot find parent when USB plugged in, Works when NOT plugged in!
  10 Jun 2021, 09:46 • Nigel31   12 Jun 2021, 14:48

  11
  0
  Votes
  11
  Posts
  73
  Views

  12 Jun 2021, 14:48

  Update: The issue seems to be with the Mega Mini board. I managed to remove the Adafruit RFM69HW daughter board from the verroboard, and wired this to a Nano, and a Teensy 3.2. Both worked with the same PSU. The USB converter however is still giving garbage , no matter which of the three sources above. So I am in the belated process of porting code to the teensy as the target. Many thanks for the help to you all. Now, if I can only sort out my sensebender gateway problem....
• 

  Novice user with serial gateway issues!
  4 Jun 2021, 17:25 • mrmuszynski   9 Jun 2021, 08:53

  11
  0
  Votes
  11
  Posts
  76
  Views

  9 Jun 2021, 08:53

  @skywatch Just to add to your points on 254 max children, definitions, presentation, etc., which may help @mrmuszynski at some stage. I've an array in a sketch with 14 DS18B20 addresses, all paged in turn using the one wire protocol on a single pin, so it is entirely possible to hit the 254 children limit before looking at I2C devices. The beauty of the DS18B20 array is individual chips are "defined" sequentially, hence making presentation and fetching values available to a FOR loop, which makes for a highly compact sketch.
• 

  ESP8266 Gateway
  20 May 2021, 08:33 • MathieuMdejong   8 Jun 2021, 18:05

  6
  0
  Votes
  6
  Posts
  69
  Views

  8 Jun 2021, 18:05

  @djdehaan as soon as somebody spends enough time to figure out how to do it (if it can be done) and submits a working solution.
• 

  Corrupted serial debug output
  4 Jun 2021, 07:09 • Max Kurilov   4 Jun 2021, 19:11

  5
  0
  Votes
  5
  Posts
  39
  Views

  4 Jun 2021, 19:11

  @skywatch that helped! resolved, thank you!
• 

  How to compile MySensors on Platformio for Blue Pill
  10 May 2020, 13:56 • novicit   4 Jun 2021, 17:42

  24
  0
  Votes
  24
  Posts
  272
  Views

  4 Jun 2021, 17:42

  Maybe diggin a topic a bit, but as for June 2021 : In library file MyHwSTM32.h one line seems to be lost : #ifndef MyHwSTM32_h #define MyHwSTM32_h #include <IWatchdog.h> #include <itoa.h> #include <SPI.h> #include <EEPROM.h> <<--- this is necessary to compile agains BluePill and something like this in platformio.ini [env:bluepill_f103c8] platform = ststm32 board = bluepill_f103c8 framework = arduino upload_protocol = stlink debug_port = stlink debug_tool = stlink monitor_speed = 115200 monitor_filters = time, default Just to keep you entertained. Cheerz.
• 

  requesting data from controller (Domoticz)
  3 Jun 2021, 19:39 • Nigel31   3 Jun 2021, 19:39

  1
  0
  Votes
  1
  Posts
  20
  Views

  No one has replied

• 

  OTA not working in my current setup (CRC Error)
  mycontroller error problems over the air • 5 Feb 2020, 13:24 • VonJoost   1 Jun 2021, 15:51

  14
  2
  Votes
  14
  Posts
  101
  Views

  1 Jun 2021, 15:51

  I want to share an interesting case about updating the firmware over FOTA.. I have several nodes on a RS485 bus with memory chips. Recently I decided to update the firmware on several at once and ran into an unexpected problem - repeated attempts to update constantly ended up with a checksum error !OTA:FWP:CRC FAIL. At the same time, I usually test all new nodes for FOTA firmware updates before installing. I tried to understand what the problem might be and came to an unexpected result - in my case, disabling the directive OTA_EXTRA_FLASH_DEBUG, which I had been using for a long time, when I first tested updates, helped. After disabling this directive, all firmwares were updated the first time. Very strange, but nevertheless ...
• 

  [SOLVED] Relay Sketch doesn't work every single time !
  26 May 2021, 14:50 • bonamin   27 May 2021, 15:38

  6
  0
  Votes
  6
  Posts
  49
  Views

  27 May 2021, 15:38

  @bonamin thanks for reporting back!
• 

  RFM95 RFM95:SWR:NACK
  14 May 2021, 12:19 • smilvert   17 May 2021, 18:47

  3
  0
  Votes
  3
  Posts
  46
  Views

  17 May 2021, 18:47

  @lood29 When I use TTGO LORA as a dummy sensor (Node 10 in the above log) it always works without any nacks. The NACK only appears when I connect my own sensor (Node 140 in the log above). So Scenario 1 Dummy sensor (TTGO LORA) <-> MQTT gateway (TTGO LORA) -> Works Scenario 2 My sensor <-> MQTT gateway (TTGO LORA) -> NACK in the Gateway.
• 

  Node to Node ACK
  13 May 2021, 01:53 • anderBAKE   13 May 2021, 20:24

  5
  0
  Votes
  5
  Posts
  48
  Views

  13 May 2021, 20:24

  @BearWithBeard Making the change that you suggested returns the expected results! Thanks for suggestion.
• 

  Node doesn’t seem to reconnect
  9 May 2021, 06:11 • CrankyCoder   10 May 2021, 15:09

  5
  0
  Votes
  5
  Posts
  40
  Views

  10 May 2021, 15:09

  I suppose you are using a arduino pro mini when you speak of a newbie board. So effectively it is not easy to connect a laptop to the serial output. I don't think the arduino will reset when connecting, but it's not convenient. So to detect if it is the relayboard, can you deconnect it from the newbie board and let run the node like this. If it works now for some time, we are sure it is the relayboard somehow influencing the arduino. If it still freeze, it is not the relayboard and we must continue to debug...
• 

  Poor RSSI on RFM69 with RaspberryPi SPI
  22 Apr 2021, 10:41 • alexelite   4 May 2021, 20:51

  7
  0
  Votes
  7
  Posts
  78
  Views

  4 May 2021, 20:51

  I found the proximate cause for this problem and posted it in an already opened issue. https://github.com/mysensors/MySensors/issues/1077#issuecomment-832228721
• 

  understanding mysbootloader background to get working FOTA
  1 May 2021, 19:27 • uwe taz   1 May 2021, 19:27

  1
  0
  Votes
  1
  Posts
  23
  Views

  No one has replied

• 

  while (!sensor.begin()) error
  29 Apr 2021, 16:31 • maddhin   30 Apr 2021, 09:22

  7
  0
  Votes
  7
  Posts
  33
  Views

  30 Apr 2021, 09:22

  @maddhin FWIW I always use the adafruit library for htu21D and it has a similar test in setup that does not give me any errors - might be worth a try?
• 

  GWT:TPC:CONNECTING
  26 Apr 2021, 17:56 • DenisJ   30 Apr 2021, 07:57

  24
  0
  Votes
  24
  Posts
  109
  Views

  30 Apr 2021, 07:57

  @smilvert said in GWT:TPC:CONNECTING: A ticket is raised quite long time ago Thanks a lot... I put my case there also, maybe can help. That gui use same ESP32 DevKit V1 like me. Strange that I didn't fount that page in this 2 days of research. Thanks a lot Denis
• 

  Wemos Di Mini v3 not connecting to wifi but classic D1 Mini does...
  28 Apr 2021, 10:29 • maddhin   29 Apr 2021, 15:14

  3
  0
  Votes
  3
  Posts
  21
  Views

  29 Apr 2021, 15:14

  it seems like I got a bad batch of D1 Mini v3.0.0s. I ran the sample wifi connect and wifi scan sketches on all 5 purchased boards and all had issues connecting or showing all/most available wifis. One was plain broken and wouldn't even cooperate with Win10... Some Wemos D1 Mini v2 and PROs ran the same sketches just fine. So it seems to be a manufacturer error rather than a problem with the v3 of the D1 Mini... So, if you have the choice, stick with the v2 "classic" D1 Mini. Although I didn't buy from a dodgy source, there still seem to be issues with producing the new versions reliably...
• 

  transmission and reception problems with stm32f103c8 and nrf24 library
  20 Apr 2021, 04:01 • Croma Nnon   25 Apr 2021, 20:09

  3
  0
  Votes
  3
  Posts
  28
  Views

  25 Apr 2021, 20:09

  @Croma-Nnon You know this forum is for MySensors right?
• 

  Feather m0 (SAMD) sleep and interrupt
  23 Apr 2021, 09:32 • Alpoy   25 Apr 2021, 20:03

  6
  0
  Votes
  6
  Posts
  59
  Views

  25 Apr 2021, 20:03

  @Alpoy Well done! - That is interesting! - I never used a SAMD, but at least you have a way to make it work! Maybe I should try one someday....
• 

  MY_GATEWAY_MQTT_CLIENT
  20 Apr 2021, 19:57 • keithJ   21 Apr 2021, 08:13

  4
  0
  Votes
  4
  Posts
  45
  Views

  21 Apr 2021, 08:13

  This is a good tip to add to the build instructions. Check if you plugged the cable
• 

  MQTT gateway sends duplicate messages to controller?
  25 Sept 2020, 13:30 • willemx   18 Apr 2021, 17:09

  16
  0
  Votes
  16
  Posts
  124
  Views

  18 Apr 2021, 17:09

  @hlehoux BTW, in my case this seems to be related to the battery being very low.
• 

  problems with RFM69_RFM95_ATC_SignalReport example
  14 Apr 2021, 18:53 • uwe taz   16 Apr 2021, 18:13

  3
  0
  Votes
  3
  Posts
  44
  Views

  16 Apr 2021, 18:13

  Great, that was the right hint. Now I get values. Thanks!!! But should it included in the example code? I had a look in the development branch. There it was fixed. But in the development -3.0.0 branch not.
• 

  [SOLVED]Atmega 328P reset to start
  atmega328p reset starting • 11 Apr 2021, 11:35 • barrydou   14 Apr 2021, 20:18

  12
  0
  Votes
  12
  Posts
  75
  Views

  14 Apr 2021, 20:18

  @barrydou https://electronics.stackexchange.com/questions/2262/decoupling-capacitors-what-size-and-how-many
• 

  I cannot add new nodes, After I get support in Home Assistant,
  25 Mar 2021, 17:46 • emre299   3 Apr 2021, 20:56

  5
  0
  Votes
  5
  Posts
  96
  Views

  3 Apr 2021, 20:56

  I added a new node(ralay id:50), again home assistant(HA) was not added. How can I send a new value from the Relay? You need to send a message at least once for it to appear in Home Assistant. Use something like this: bool initialMessageSent = false; void loop() { if (!initialMessageSent) { send(msgRelay.set(currentRelayState)); initialMessageSent = true; } } After you manually injected a message via MYSController, Home Assistant started to list the new entity in the UI. So yes, that's exactly what Home Assistant required. If you take care of that within the sketch as shown above, you don't need to do it manually. But It seems to be disconnected from the network every time a command comes from HA. do you think this is normal? No, I wouldn't consider that normal. What do you mean by "disconnected"? Does the node stop working completely after receiving a message from HA? Doesn't it respond to consecutive commands? Does the debug output (using #define MY_DEBUG in the relay node sketch) hint at something? Sharing your sketch may help us find the issue.
• 

  SP32 GW and RFM69HCW radio pinout
  rfm69hcw • 29 Mar 2021, 19:55 • DenisJ   30 Mar 2021, 03:55

  3
  0
  Votes
  3
  Posts
  25
  Views

  30 Mar 2021, 03:55

  It's work Thanks a lot
• 

  How do I change the default units for the MQTT gateway?
  23 Mar 2021, 20:41 • fixjunk   25 Mar 2021, 11:39

  2
  0
  Votes
  2
  Posts
  35
  Views

  25 Mar 2021, 11:39

  @fixjunk this configuration will be supplied to your gateway from a controller. Source: https://www.mysensors.org/download/serial_api_20 When your MySesnors node boots up, sends a I_CONFIG request to your controller, your controller has to respond to this request [response can be either (M)etric or (I)mperal ] AFAIK, This metric change will not affect your sensor measurement units. You have to convert yourself in your sketch. @mfalkvidd can confirm this.
• 

  How to change Radio ID on Raspberry Pi Gateway with NRF24
  23 Mar 2021, 11:44 • jacmika   24 Mar 2021, 14:09

  4
  0
  Votes
  4
  Posts
  30
  Views

  24 Mar 2021, 14:09

  @jacmika it would need shell escaping and it is missing the initial D. I would try something like --extra-cxxflags="-DMY_RF24_BASE_RADIO_ID=0x00,0xFC,0xE1,0xA8,0xA8 If I recall correctly, the output of make will show which defines are activated, and what values they have. That's what I usually use to check if I got it right.
• 

  config.h:39 : first defined here
  13 Nov 2020, 20:24 • suspendfunction   19 Mar 2021, 23:36

  4
  1
  Votes
  4
  Posts
  73
  Views

  19 Mar 2021, 23:36

  https://github.com/mysensors/MySensors/pull/1454
• 

  Feather M0 RFM60HCW (433Mhz) - can't connect to gw
  12 Mar 2021, 13:45 • Alpoy   14 Mar 2021, 09:54

  8
  0
  Votes
  8
  Posts
  66
  Views

  14 Mar 2021, 09:54

  I think I've narrowed it down to encryption, disabling it on the GW and the feather seems to make everything work ok. I've double checked that the key is identical but still won't work. Encryption works when I use the ESP32 as "client" instead of the Feather M0. I thought the AES encryption was done in the radio (rfm69) and not the microcontroller (ie. ESP32/Arduino etc.). Also, there's really no log message that indicates wrong encryption key or anything related to an encryption problem in the communication?
• 

  Relay Actuator with momentary (pulse) action
  23 Jan 2017, 22:03 • drradkin   11 Mar 2021, 14:30

  7
  0
  Votes
  7
  Posts
  2.1k
  Views

  11 Mar 2021, 14:30

  @BearWithBeard said in Relay Actuator with momentary (pulse) action: digitalWrite(relayPin[message.getSensor()-7], RELAY_ON) Many thanks for coming back @BearWithBeard, its a huge help. So my logic for correcting the State problem at the bottom would be to do the same calculation to get them in to 0 and 1. saveState(message.getSensor()-7, message.getBool()); Compiled correctly and then uploaded and it works! Fantastic. The following sketch has 3 dimmers, 4 buttons and 2 relay outputs. Thank you very much - I'm learning /** * 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. * ******************************* * * REVISION HISTORY * Version 1.0 - February 15, 2014 - Bruce Lacey * Version 1.1 - August 13, 2014 - Converted to 1.4 (hek) * * DESCRIPTION * This sketch provides a Dimmable LED Light using PWM and based Henrik Ekblad * <henrik.ekblad@gmail.com> Vera Arduino Sensor project. * Developed by Bruce Lacey, inspired by Hek's MySensor's example sketches. * * The circuit uses a MOSFET for Pulse-Wave-Modulation to dim the attached LED or LED strip. * The MOSFET Gate pin is connected to Arduino pin 3 (LED_PIN), the MOSFET Drain pin is connected * to the LED negative terminal and the MOSFET Source pin is connected to ground. * */ // Button // The below includes 4 buttons using code examples from here: https://forum.mysensors.org/topic/9538/multiple-switch-inputs/8 // Button // Relay // The below includes 2 relays from https://www.mysensors.org/build/relay // https://forum.mysensors.org/topic/5906/relay-actuator-with-momentary-pulse-action/2 // Relay // Enable debug prints to serial monitor #define MY_DEBUG // Enable and select radio type attached //#define MY_RADIO_RF24 //#define MY_RADIO_NRF5_ESB //#define MY_RADIO_RFM69 //#define MY_RADIO_RFM95 // Enable RS485 transport layer #define MY_RS485 // Define this to enables DE-pin management on defined pin #define MY_RS485_DE_PIN 2 // Set RS485 baud rate to use #define MY_RS485_BAUD_RATE 9600 #define MY_NODE_ID 4 #include <SPI.h> #include <MySensors.h> // Button #include <Bounce2.h> // #define SN "N004" #define SV "1.0" #define noLEDs 2 const int LED_Pin[] = {5, 6}; #define FADE_DELAY 10 // Delay in ms for each percentage fade up/down (10ms = 1s full-range dim) static int currentLevel1 = 0; // Current dim level... static int currentLevel2 = 0; // Current dim level... MyMessage dimmer1Msg(1, V_DIMMER); MyMessage light1Msg(1, V_LIGHT); MyMessage dimmer2Msg(2, V_DIMMER); MyMessage light2Msg(2, V_LIGHT); // Button #define FIRST_BUTTON_ID 3 #define MAX_BUTTON 4 const uint8_t buttonPin[] = {4, 10, 11, 12}; // switch around pins to your desire Bounce debouncer[MAX_BUTTON]; MyMessage buttonMsg(0, V_TRIPPED); bool oldButton[MAX_BUTTON] = {false}; // Button // Relay #define FIRST_RELAY_ID 7 #define MAX_RELAY 2 const uint8_t relayPin[] = {3, 7}; // Pins of relays MyMessage relayMsg(0, V_STATUS); #define RELAY_ON 1 #define RELAY_OFF 0 // Relay void before() { } /*** * Dimmable LED initialization method */ void setup() { // LEDS // Pull the gateway's current dim level - restore light level upon sendor node power-up for (int sensor=1; sensor<=noLEDs; sensor++){ request( sensor, V_DIMMER ); } // Button for (uint8_t i = 0; i < MAX_BUTTON; i++) { debouncer[i] = Bounce(); // initialize debouncer debouncer[i].attach(buttonPin[i], INPUT_PULLUP); debouncer[i].interval(5); oldButton[i] = debouncer[i].read(); } // Button // Relay for (uint8_t i = 0; i < MAX_RELAY; i++) { pinMode(relayPin[i], OUTPUT); //digitalWrite(relayPin, loadState(i)?RELAY_ON:RELAY_OFF); if (loadState(i) == RELAY_ON) { digitalWrite(relayPin, RELAY_ON); wait(500); digitalWrite(relayPin, RELAY_OFF); } } // Relay } void presentation() { // Register the LED Dimmable Light with the gateway for (int sensor=1; sensor<=noLEDs; sensor++){ present(sensor, S_DIMMER); wait(2); } // Button for (int i = 0; i < MAX_BUTTON; i++) { //i < numSensors && present(FIRST_BUTTON_ID + i, S_DOOR); } // Button // Relay for (int i = 0; i < MAX_RELAY; i++) { present(FIRST_RELAY_ID + i, S_BINARY); } // Relay sendSketchInfo(SN, SV); } /*** * Dimmable LED main processing loop */ void loop() { // Button bool button[MAX_BUTTON]; for (uint8_t i = 0; i < MAX_BUTTON; i++) { debouncer[i].update(); button[i] = debouncer[i].read(); if (button[i] != oldButton[i]) { send(buttonMsg.setSensor(FIRST_BUTTON_ID + i).set( button[i])); // Send tripped value to gw oldButton[i] = button[i]; } } // Button } void receive(const MyMessage &message) { if (message.type == V_LIGHT || message.type == V_DIMMER) { if (message.sensor == 1) { // Retrieve the power or dim level from the incoming request message int requestedLevel1 = atoi( message.data ); // Adjust incoming level if this is a V_LIGHT variable update [0 == off, 1 == on] requestedLevel1 *= ( message.type == V_LIGHT ? 100 : 1 ); // Clip incoming level to valid range of 0 to 100 requestedLevel1 = requestedLevel1 > 100 ? 100 : requestedLevel1; requestedLevel1 = requestedLevel1 < 0 ? 0 : requestedLevel1; fadeToLevel1( requestedLevel1, message.sensor ); send(light1Msg.set(currentLevel1 > 0 ? 1 : 0)); send(dimmer1Msg.set(currentLevel1) );} if (message.sensor == 2) { // Retrieve the power or dim level from the incoming request message int requestedLevel2 = atoi( message.data ); // Adjust incoming level if this is a V_LIGHT variable update [0 == off, 1 == on] requestedLevel2 *= ( message.type == V_LIGHT ? 100 : 1 ); // Clip incoming level to valid range of 0 to 100 requestedLevel2 = requestedLevel2 > 100 ? 100 : requestedLevel2; requestedLevel2 = requestedLevel2 < 0 ? 0 : requestedLevel2; fadeToLevel2( requestedLevel2, message.sensor ); send(light2Msg.set(currentLevel2 > 0 ? 1 : 0)); send(dimmer2Msg.set(currentLevel2) );} } // Relay if (message.type == V_STATUS) { if (message.sensor == 7) { if (message.getBool() == RELAY_ON) { //digitalWrite(message.getSensor()-1+relayPin, RELAY_ON); digitalWrite(relayPin[message.getSensor()-7], RELAY_ON); wait(500); //digitalWrite(message.getSensor()-1+relayPin, RELAY_OFF); digitalWrite(relayPin[message.getSensor()-7], RELAY_OFF); } saveState(message.getSensor()-7, message.getBool()); } if (message.sensor == 8) { if (message.getBool() == RELAY_ON) { //digitalWrite(message.getSensor()-1+relayPin, RELAY_ON); digitalWrite(relayPin[message.getSensor()-7], RELAY_ON); wait(500); //digitalWrite(message.getSensor()-1+relayPin, RELAY_OFF); digitalWrite(relayPin[message.getSensor()-7], RELAY_OFF); } saveState(message.getSensor()-7, message.getBool()); } } // Relay } /*** * This method provides a graceful fade up/down effect */ void fadeToLevel1( int toLevel1, int ledid1 ) { int delta1 = ( toLevel1 - currentLevel1 ) < 0 ? -1 : 1; while ( currentLevel1 != toLevel1 ) { currentLevel1 += delta1; analogWrite(LED_Pin[ledid1-1], (int)(currentLevel1 / 100. * 255) ); wait( FADE_DELAY ); } } void fadeToLevel2( int toLevel2, int ledid2 ) { int delta2 = ( toLevel2 - currentLevel2 ) < 0 ? -1 : 1; while ( currentLevel2 != toLevel2 ) { currentLevel2 += delta2; analogWrite(LED_Pin[ledid2-1], (int)(currentLevel2 / 100. * 255) ); wait( FADE_DELAY ); } }
• 

  Sending sensor data from arduino pro mini via NRF24L01+ to raspberry pi 4
  4 Mar 2021, 12:29 • Leon   8 Mar 2021, 09:16

  5
  1
  Votes
  5
  Posts
  49
  Views

  8 Mar 2021, 09:16

  @haloway13 Hey, as I said below, I have found a solution to the problem. I have made use of two other tutorials. (Attention German language!) https://draeger-it.blog/arduino-lektion-48-temperatursensor-ds18b20/ https://tutorials-raspberrypi.de/funkkommunikation-zwischen-raspberry-pis-und-arduinos-2-4-ghz/ If you look at the wiring, I can send you my code so far: #include <SPI.h> #include "printf.h" #include "RF24.h" #include <OneWire.h> #include <DallasTemperature.h> #define ONE_WIRE_BUS 2 //Sensor DS18B20 at digital pin 2 RF24 radio(7, 8); // using pin 7 for the CE pin, and pin 8 for the CSN pin OneWire oneWire(ONE_WIRE_BUS); DallasTemperature sensors(&oneWire); // Transfer of the OnewWire reference to communicate with the sensor. uint8_t address[][6] = {"1Node", "2Node"}; // Let these addresses be used for the pair bool radioNumber = 1; //to use different addresses on a pair of radios, we need a variable to uniquely identify which address this radio will use to transmit int sensorCount; float payload = 0.0; int ID = 0; float temperature = 0.0; float battery = 0.0; void setup() { Serial.begin(115200); while (!Serial) { // some boards need to wait to ensure access to serial over USB } // initialize the transceiver on the SPI bus if (!radio.begin()) { Serial.println(F("radio hardware is not responding!!")); while (1) {} // hold in infinite loop } // Set the PA Level low to try preventing power supply related problems // because these examples are likely run with nodes in close proximity to // each other. radio.setPALevel(RF24_PA_LOW); // RF24_PA_MAX is default. sensors.begin(); // Start communication with the sensor sensorCount = sensors.getDS18Count(); // Reading the number of connected // save on transmission time by setting the radio to only transmit the // number of bytes we need to transmit a float radio.setPayloadSize(sizeof(payload)); // float datatype occupies 4 bytes // set the TX address of the RX node into the TX pipe radio.openWritingPipe(address[radioNumber]); // always uses pipe 0 // set the RX address of the TX node into a RX pipe radio.openReadingPipe(1, address[!radioNumber]); // using pipe 1 radio.stopListening(); // put radio in TX mode } // setup void loop() { if(sensorCount ==0){ Serial.println("No temperature sensors found"); Serial.println("Please check your circuit!"); } sensors.requestTemperatures(); // This device is a TX node payload = sensors.getTempCByIndex(0); unsigned long start_timer = micros(); // start the timer bool report = radio.write(&payload, sizeof(float)); // transmit & save the report unsigned long end_timer = micros(); // end the timer if (report) { Serial.print(F("Transmission successful! ")); // payload was delivered Serial.print(F("Time to transmit = ")); Serial.print(end_timer - start_timer); // print the timer result Serial.print(F(" us. Sent: ")); Serial.println(payload); // print payload sent } else { Serial.println(F("Transmission failed or timed out")); // payload was not delivered } // to make this example readable in the serial monitor delay(1000); // slow transmissions down by 1 second } // loop
• 

  cant add two relays in the Home assistant
  6 Mar 2021, 14:46 • alpha0101   7 Mar 2021, 15:38

  3
  0
  Votes
  3
  Posts
  41
  Views

  7 Mar 2021, 15:38

  I believe you have to send a state also, to have it show up in home assistant. https://www.home-assistant.io/integrations/mysensors/
• 

  Led Rx,Tx,Err for ESP8266 Wifi gateway not working.
  1 Mar 2021, 10:16 • Gerard_Tlse   1 Mar 2021, 10:16

  1
  0
  Votes
  1
  Posts
  16
  Views

  No one has replied

• 

  RFM69hcw (arduino pro mini) not finding parent (esp8266)
  10 Feb 2021, 20:54 • lvw   27 Feb 2021, 13:54

  8
  0
  Votes
  8
  Posts
  72
  Views

  27 Feb 2021, 13:54

  No luck so far. Thanks for all the advice! For now I have decided to try something else end keep using nRF24 but switch from a ESP8266 gateway to one running on a Raspberry Pi.
• 

  [SOLVED] BH1750 Light level sensor not reading after sleep
  24 Feb 2021, 17:41 • Steve Parsons   26 Feb 2021, 19:17

  5
  0
  Votes
  5
  Posts
  55
  Views

  26 Feb 2021, 19:17

  Hi @Steve-Parsons, short question: do you have applied the external pull-up resistors for the two I2C bus lines? Some modules have them built-in but others not. E.g. the Lolin Wemos shield has them already connected to power with two 4.7k resistors. See schematic for it: sch_bh1750_v1.0.0.pdf If not, you should try this. May be your first module is not defect, but only the resistors are missing?
• 

  (homeassistant) mysensors.notify does nothing, (alternatives?)
  20 Jun 2019, 14:26 • zen85   22 Feb 2021, 18:58

  8
  0
  Votes
  8
  Posts
  786
  Views

  22 Feb 2021, 18:58

  I faced same issue and was able to solve it by doing a proper presentation of S_INFO widget, as described in sample sketch: https://www.home-assistant.io/integrations/notify.mysensors/ The error message is quite misleading.
• 

  RFM69 Range issues
  29 Dec 2020, 19:31 • bjornhallberg   22 Feb 2021, 03:19

  35
  0
  Votes
  35
  Posts
  286
  Views

  22 Feb 2021, 03:19

  @bjornhallberg said in RFM69 Range issues: Gateway (rfm69hw) initialization: #define MY_IS_RFM69HW #define MY_RFM69_FREQUENCY RFM69_868MHZ #define MY_RFM69_NEW_DRIVER Maybe I missed someone pointing this out, but the original poster's gateway initialization looks like it's missing something. These defines are not at all obvious, especially with the HW version. Strange things can happen, including unexpectedly low power. Check the API docs and also another thread. With the HW version of the RFM69 on the gateway, and the RFM69 new driver, in addition to what you list, you need to also include: #define MY_RADIO_RFM69 #define MY_RFM69HW true https://www.mysensors.org/apidocs/group__RFM69SettingGrpPub.html#gaf1455cd3427c9dc4c4564542c3dafc16 https://forum.mysensors.org/topic/11316/rfm69hw-atc-not-working
• 

  Trouble with Sensebender gateway initialisation
  16 Feb 2021, 12:38 • Nigel31   20 Feb 2021, 19:05

  11
  0
  Votes
  11
  Posts
  101
  Views

  20 Feb 2021, 19:05

  Sorry, but I'm afraid I can't help you any further. If the tests in the sketch do not go any further, there is something wrong with the board itself...
• 

  Node changed ID
  8 Aug 2018, 21:40 • Strixx   18 Feb 2021, 06:19

  11
  0
  Votes
  11
  Posts
  1.3k
  Views

  18 Feb 2021, 06:19

  @Flyer Sorry, but I can't remember if I had any more problems after I manually fixed the database. And just a couple months after I had this problem I switched to Home Assistant instead.
• 

  automating old device with a momentary push button
  9 Feb 2021, 22:43 • pioneer_shahid   10 Feb 2021, 12:35

  2
  0
  Votes
  2
  Posts
  47
  Views

  10 Feb 2021, 12:35

  Here is the schematics diagram.. thanks to @petewill for his original post and diagram.
• 

  Signing and mysterious !MCO:PRO:RC=1
  signing recursive call mcoprorc1 • 3 Feb 2021, 19:54 • Geelbuik   3 Feb 2021, 21:14

  2
  0
  Votes
  2
  Posts
  28
  Views

  3 Feb 2021, 21:14

  @Geelbuik it is a known issue, see https://github.com/mysensors/MySensors/issues/1458
• 

  Node can present to gateway, but not pass data?
  myscontroller hardware iobroker ebyte • 25 Jan 2021, 12:19 • bcdaus   1 Feb 2021, 07:15

  6
  1
  Votes
  6
  Posts
  63
  Views

  1 Feb 2021, 07:15

  I am going to rework the system so it uses an Easy Pcb and a Pro Mini rather than the Leonardo board. I think I might be seeing a voltage drop in my point to point dupont wiring from the Arduino to the Radio. I'll update you all once I get a chance to make the change. Bill
• 

  Lack of service continutity after power failure
  27 Jan 2021, 14:53 • halo6   28 Jan 2021, 14:34

  6
  0
  Votes
  6
  Posts
  51
  Views

  28 Jan 2021, 14:34

  @skywatch Perhaps of interest, this possibility (lots of power cuts here in the early days) led me not only interface serial but power for the Gateway from the Pi header rather than separately, the current draw is tiny. The power cuts I later solved with a UPS but even before that it rebooted and went to work without issues, since the two reboot in sequence under the control of the Pi. As @Yveaux however has highlighted all my Nodes are fixed IDs.
• 

  I need to measure microamper current with low noise
  @electronic @circuit • 21 Jan 2021, 05:28 • metceyn   22 Jan 2021, 20:52

  3
  0
  Votes
  3
  Posts
  48
  Views

  22 Jan 2021, 20:52

  I have both the uCurrent gold as suggested by @evb and also the "current ranger" https://lowpowerlab.com/shop/product/152 which is my first choice. It has a small display which makes it easier to use. But both are great products based on the same ideas from Evblog. Then to measure transient current you can hook up an oscilloscope to the output of any of the two.