The third field of keywords.txt is used to provide Arduino Language
Reference links, which are accessed from the Arduino IDE by
highlighting the keyword and then selecting "Find in Reference"
from the Help or right click menu. Adding values to this field that
do not match any existing reference pages results in a "Could not
open the URL" error.
A while ago, MySensors changed to use int32_t
instead of long int (and similar for other data
types). This change was not applied to all examples,
causing some examples to fail compilation for
ESP8266 with the following message:
call of overloaded 'set(long int)' is ambiguous
This update changes the casts to match the new style.
This fixes
https://github.com/mysensors/MySensors/issues/1129
Thanks to https://github.com/henfri for reporting.
The Butler is a more polite and helpful replacement to the
grumpy old Gitler.
The Butler will do his utmost to assist new (and old)
contributors to the MySensors cause.
For battery powered sensors which wake up by the RST Pin its useful
to sleep the cpu forever. When using this command:
sleep(INTERRUPT_NOT_DEFINED, MODE_NOT_DEFINED, 0, false);
the code will be stripped down to hwSleep(0);.
But this will not sleep the cpu forever.
This fixes
https://github.com/mysensors/MySensors/issues/1089
and also adds Doxygen and syntax highlighting
for the following keywords:
MY_GATEWAY_MQTT_CLIENT
MY_GATEWAY_SERIAL
MY_IP_GATEWAY_ADDRESS
MY_IP_SUBNET_ADDRESS
MY_MQTT_CLIENT_ID
MY_MQTT_PUBLISH_TOPIC_PREFIX
MY_MQTT_SUBSCRIBE_TOPIC_PREFIX
* Add missing keywords and blacklist
These keywords already exist in Doxygen and should be highlighted
in the Arduino IDE.
Some keywords should not be highlighed and are therefore added
to the blacklists at end of keywords.txt
* Sort keywords in each section
* Add blacklist of MY_MQTT_TOPIC_PREFIX
- The following settings can be use on the config file:
- verbose=[debug,info,notice,warn,err] - Logging verbosity.
- log_file[0|1] - Enable logging to a file.
- log_filepath=(FILE) - Log file path.
- log_pipe=[0|1] - Enable logging to a named pipe(aka fifo).
Use this option to view your gateway's log messages from the
log_pipe_file (defined below).
To do so, run the following command on another terminal:
- $ cat "log_pipe_file"
- log_pipe_file=(FILE)
- syslog=[0|1] - Enable logging to syslog.
- eeprom_file=[/etc/mysensors.eeprom]
- eeprom_size=[1024]
- Change some mysgw parameters:
- Added:
- -q, --quiet: for quiet mode, disable log messages written to the
terminal.
- Removed:
- -d, --debug: removed, log messages are now enabled by default.
- Replaced:
- -b, --background: replaced by --daemon
- isatty() is no longer used, log messages by default are printed to
stderr unless the gateway is started with --quiet (#1022)
- MY_LINUX_CONFIG_FILE: no longer holds the path to the eeprom file,
but to the configuration file
A blacklist is available at the end of keywords.txt
I decided to blacklist all the LINUX keywords. I guess people
could use the Arduino IDE to edit the sketch for the raspberry
pi gateway, but I'm not sure we should encourage that.
I'll add gitler support for auto-detecting missing keywords
in a separate PR.
* Derive default interrupt from configured instead of default pin
Derive DEFAULT_RFM69_IRQ_NUM from MY_RFM69_IRQ_PIN instead of
DEFAULT_RFM69_IRQ_PIN so that _NUM does not have to be defined
if _PIN is redefined
* Change default IRQ pin for RFM69/95 on ESP8266 to GPIO5=D1
The originally defined pin GPIO2 prevent ESP8266 from booting,
since it has to be pulled high for booting and DIO0 from the
RFM69 is defaul low.
For this reason, it is improbably that anyone is using the default
and would be affected by this change.
The message hook validates that the c ommit message follows
the MySensors requirements.
More specifically, it checks that
- Commit message does not exceed a line length of 72 characters
- Commit title start with an uppercase character
- Commit title does not end with a period ('.')
Fixes#672
* New Firmware OTA for NVM/mcuboot (nRF5)
- Support for mcuboot (nRF5)
- Support for run length encoded data
- Support for smaller FIRMWARE_BLOCK_SIZE, if required
* Update NVM
* New MY_LOCK_MCU for NRF5
* Test with Sensebender GW + Sensebender Micro was successful
The comment for inclusion mode pin and the definition of
MY_INCLUSION_MODE_BUTTON_PIN did not match.
GPIO5 should be safe to use, while GPIO3 is used for the
UART which might result in conflict.
This fixes
https://github.com/mysensors/MySensors/issues/993
matzman
Patrick Fallberg
Marcelo Aquino
seeers
tekka
per1234
Mikael Falkvidd
Avamander
Marco Bakera
Martin Hjelmare
Tombula
flopp999
thucar
kvoit
d00616