@alexsh1 re-personalize the node that lost the checksum. Each node (including gw) has a unique personalization and checksum (possibly). Just because one node looses the checksum or gets a mismatch does not mean any other node has the same problem. Everything is stored in eeprom locally.
Hello, can you, on the basis of the principle of this scanner, realize the work of the loader with any radio channel? I think it might work. https://forum.mysensors.org/topic/8748/mys-network-scanner-4-sec
How is the upcoming bootloader release (1.3S) going?
I may be wrong but think I need this to push signed firmware to a node. I have a node with soft signing required. The node works but I cannot update it OTA is this 1.3S to support this?
To use the FTDI connection:
You need a ceramic cap (not polarised).
RTS - CAP - RESET pin of ATMEGA
RESET pin needs a pull up resistor of 10K, connect as follows: VCC - 10K resistor - RESET pin of ATMEGA
@Yveaux said in ESP8266 WiFi gateway port for MySensors:
@Mark-Swift that issue apparently addressed an issue in the vs1053 library, which surfaced because the esp8266 doesn't support interrupts on spi transfers.
The issue was closed because the vs1053 library was modified to support esp8266, unfortunately not because esp interrupt support for spi was implemented...
@Yveaux You're right, should have read more before jumping to conclusions
Damn, I thought I could finally dump my serial gateway!
@mfalkvidd said in Request Value from Node:
@soloam looks like you should be able to use mGetCommand and check for C_SET / C_REQ.
Is this mGetCommand is official API ? because it does not look like. I wouldn't use undocumented methods, because they may disapear in new releases.
@gertsanders yes that's correct. From the documentation:
First free address for sketch static configuration.
But whenever a new version of the MySensors library needs more eeprom, EEPROM_LOCAL_CONFIG_ADDRESS will be changed. So be careful when upgrading the library.
https://github.com/mysensors/MySensors/issues/379 has been created to make the address more permanent.
I am not sure which addresses saveState/loadState uses. Maybe that function is more resilient.
EDIT: saveState uses EEPROM_LOCAL_CONFIG_ADDRESS internally, so saveState will be broken as well if the library changes EEPROM_LOCAL_CONFIG_ADDRESS. But do use saveState instead of writing directly to the eeprom.
henrikekblad created this issue in mysensors/MySensors
Move EEPROM_LOCAL_CONFIG_ADDRESS to end of EEPROM
Instead of making a different script for each sensor to change the delay, you can either use a random value or make node id * xxx ms and a fixed value if node id is not yet set.
@d-smes said in transportPowerDown() with v2.2.0:
Thanks guys; that worked! And if anyone else is interested, the radio automatically re-enables when you send a message.
@gohan - I monitor several temperatures, water levels, and flow rates associated with a duck pond and filtration system. Things can get out of whack fairly quickly due to pump inlet blockages, full filters, equipment failures, and weather induced surprises. Need quick updates so if there's a problem, I can intervene before a pump runs dry or I lose too much water.
Maybe off-topic, but those that don't know about Finite State Machines could have a look at these links for a start...