You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently mailbox ID is compiled in on the sender side. The idea would be for a sender to provide some unique ID instead (probably derived from ESP MAC) and then allow remapping this on the receiver side to an ID=1,2 etc.
To get a reasonably unique ID one would likely need to modify the protocol to send a long string, which would not only be incompatible change, but could easily double the packet size. So the feature to be taken with caution.
The text was updated successfully, but these errors were encountered:
Another option would be to use a separate sketch to ask the ID from the user and write it to EEPROM. The sketch would need to be run once after module assembly. This would not require modification of the protocol. In absence of configuration a digit from ESP MAC could be taken, which would give some - poor, but not zero - probability to distinguish the units by default. The sketch could be potentially combined with the sketch used for battery calibration (see feature #47).
Currently mailbox ID is compiled in on the sender side. The idea would be for a sender to provide some unique ID instead (probably derived from ESP MAC) and then allow remapping this on the receiver side to an ID=1,2 etc.
To get a reasonably unique ID one would likely need to modify the protocol to send a long string, which would not only be incompatible change, but could easily double the packet size. So the feature to be taken with caution.
The text was updated successfully, but these errors were encountered: