MySensors.h error when compiling: "No forward link or gateway feature activated"

[chippey5]

@mfalkvidd Thanks for your reply!

I can't find the example including "Temp" nor DS18B20 in the example folder. Is it called something else? Thanks in advance

[mfalkvidd]

@chippey5 oh, sorry about that. All examples that require external libraries (like the DallasTemperature library) now need to be downloaded separately. https://github.com/mysensors/MySensorsArduinoExamples/archive/master.zip

[chippey5]

Splendid, that did the trick! I received the good ol' millisWaitForConversion error, but using the "DallasTemperature" library included in the Github link fixed the problem.

Thanks a bunch!

[mfalkvidd]

Great @chippey5 ! Thanks for reporting back.

[ninkasi]

Thanks for the suggestions @mfalkvidd, and @chippey5 - thanks for the update - I had exactly the same issue, and could not work out why I was getting that 'millisWait' error. All good now!

[TheoL]

Just adding this for people who come here by looking for the error "No forward link or gateway feature activated". Since you've to configure MySensors 2.0 before you include the library. You'll need to configure the radio you're using.

I got this message when I didn't. So just for people who queury for the same error message. Configure you're radio and other options before you include the library. @mfalkvidd do we have a topic with MySensors 2.0 troubleshooting? Might be handy to put this one. I came across this one when I was teaching my colleagues tonight. Not a biggy, put took me a while to sort it out.

/** 
 * Set configuration options for MySensors 
 */
#define MY_RADIO_NRF24  
#define MY_DEBUG // uncomment when compiling for production

/**
 * Include necessary libraries
 */
#include <MySensors.h> // include MySensors library
#include <SPI.h>       // include SPI needed for the MySensors Radio

[chippey5]

@TheoL Bump. That's exactly where I'm stuck at the moment. A link here to the future thread would be awesome for other users encountering the same issue

[Nca78]

What about changing the message text also ? I guess the programmers get it quickly, but for the common folk this message is a bit cryptic ;)

What about changing "#error No forward link or gateway feature activated. This means nowhere to send messages! Pretty pointless."
to something like :
"#error No forward link or gateway feature activated. Please define radio type (ex: #define MY_RADIO_NRF24) or gateway type (ex: #define MY_GATEWAY_SERIAL) at the beginning of your sketch" ?

[TheoL]

@Nca78 Good suggestion. But I'm not sure if the reason for this error is always missing configuration. That's something @hek might know more about.

[Nca78]

@TheoL it is.
When you define a radio, it defines MY_RADIO_FEATURE

// Enable radio "feature" if one of the radio types was enabled
#if defined(MY_RADIO_NRF24) || defined(MY_RADIO_RFM69) || defined(MY_RS485)
	#define MY_RADIO_FEATURE
#endif

Same thing when you define a gateway :

#if defined(MY_GATEWAY_SERIAL) || defined(MY_GATEWAY_W5100) || defined(MY_GATEWAY_ENC28J60) || defined(MY_GATEWAY_ESP8266) || defined(MY_GATEWAY_MQTT_CLIENT)
	#define MY_GATEWAY_FEATURE

Then at the end if MY_RADIO_FEATURE and MY_GATEWAY_FEATURE are not defined it generates this compilation error

	#if !defined(MY_GATEWAY_FEATURE) && !defined(MY_RADIO_FEATURE)
		#error No forward link or gateway feature activated. This means nowhere to send messages! Pretty pointless.
	#endif