User Tools

Site Tools


конфигурирование

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

конфигурирование [2019/01/09 02:37]
farlake создано
конфигурирование [2019/02/17 15:02] (current)
admin
Line 1: Line 1:
 # Boot sequence: # Boot sequence:
 +
 * Trying to load JSON config from NVRAM. If config is valid JSON structure - start to operating (to avoid dependance from network and allow local control) * Trying to load JSON config from NVRAM. If config is valid JSON structure - start to operating (to avoid dependance from network and allow local control)
 * Trying to retrieve MAC address, stored in NVRAM. If ok - using retrieved MAC. If not - using CUSTOM_FIRMWARE_MAC (see compilers directives). If not configured - using hardcoded DEFAULT_FIRMWARE_MAC = {0xDE, 0xAD, 0xBE, 0xEF, 0xFE, 0} * Trying to retrieve MAC address, stored in NVRAM. If ok - using retrieved MAC. If not - using CUSTOM_FIRMWARE_MAC (see compilers directives). If not configured - using hardcoded DEFAULT_FIRMWARE_MAC = {0xDE, 0xAD, 0xBE, 0xEF, 0xFE, 0}
Line 11: Line 12:
 # Operation # Operation
 During normal operation, controller: During normal operation, controller:
 +
 * Accepting incoming MQTT message flow and retrieving item name from topic name. For example, /​myhome/​in/​item1 will control "​item1"​ * Accepting incoming MQTT message flow and retrieving item name from topic name. For example, /​myhome/​in/​item1 will control "​item1"​
 * Controlling items. * Controlling items.
Line 17: Line 19:
  
 # Useful CLI commands: # Useful CLI commands:
 +
 * mac 11:​22:​33:​44:​55:​66 ​ - writing custom MAC address to NVRAM * mac 11:​22:​33:​44:​55:​66 ​ - writing custom MAC address to NVRAM
 * save - writing currently loaded config from RAM to NVRAM * save - writing currently loaded config from RAM to NVRAM
конфигурирование.txt · Last modified: 2019/02/17 15:02 by admin