* 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
- The symlink name for the PTY device is set using --my-serial-port
making --my-serial-pty deprecated
- Replace MY_LINUX_IS_SERIAL_PTY with MY_LINUX_SERIAL_IS_PTY
- MY_DEBUGDEVICE can be used to print debug messages from MySensors
(as it is currently in the other architectures)
- Rename SerialSimulator class to StdInOutStream
- Remove old deprecated option --my-radio
MY_SIGNING_SIMPLE_PASSWD is now
called MY_SECURITY_SIMPLE_PASSWD.
MY_SIGNING_SIMPLE_PASSWD only affects signing,
and a new flag, MY_ENCRYPTION_SIMPLE_PASSWD
only affects encryption.
MY_SECURITY_SIMPLE_PASSWD enable both these flags.
The rPi port has been improved to support more
security settings and it is now also possible to
enable encryption for RFM69 transport.
Documentation has been improved to provide a
"Security" section under "Library customisation"
which has a table that summarize all security
related configuration flags, and the corresponding
rPi configuration flags.
The signing personalization documentation has been
updated to include the procedure for rPi.
Fixes#1055
* Let Gitler produce a changelog for release builds
* Fix bug in publishing release documentation
* Fix bug in labeling documentation
(now uses tag data for better tracability)
* Update copyright in documentation
* Fix cppcheck issues
Fixes the following cppcheck issues:
examples/SecretKnockSensor/SecretKnockSensor.ino
305 variableScope 398 style
The scope of the variable 'timeDiff' can be reduced.
examples/SensebenderGatewaySerial/SensebenderGatewaySerial.ino
127 variableScope 398 style
The scope of the variable 'led_state' can be reduced.
* Doxygenize MyMessage / Message manipulation
This should replace the static documentation at
http://korturl.nu/stupid
I have enabled existing comments and added new comments where
necessary. Feedback on syntax and contents is welcome.
Fixes the following cppcheck issues:
examples/SecretKnockSensor/SecretKnockSensor.ino
305 variableScope 398 style
The scope of the variable 'timeDiff' can be reduced.
examples/SensebenderGatewaySerial/SensebenderGatewaySerial.ino
127 variableScope 398 style
The scope of the variable 'led_state' can be reduced.
The guide we are referring to
( https://chris.beams.io/posts/git-commit/ )
says:
shoot for 50 characters, but consider 72 the hard limit
so let Gitler consider 72 the hard limit (instead of 50).
This log message makes the Serial gateway print the serial port path,
similar to how the Ethernet gateway prints IP and port.
Example log output:
mysgw: Serial port /dev/MyCoolTTY (115200 baud) created
As mentioned by per1234 in
https://github.com/mysensors/MySensors/pull/1008
we should make it easier to find the full code contribution
guidelines.
Since we have multiple git repos, we don't want to duplicate the
guidelines in each repo. Instead, we link to the canonical source
on mysensors.org.
Mikael Falkvidd
tekka
Marcelo Aquino
thucar
kvoit
Patrick Fallberg
d00616
Miloslav Kazda
Kartik Arora
Mikael Falkvidd git@mjo.se
rejoe2