And here is the serial output once I put the gateway into configure mode (holding down the red reset button until the led blinks blue).
Note that, this time, when I view the Devices tab in the gateway web config, I do indeed see the temp/humidity sensor! This is the first time it has appeared automatically without me needing to restart the sensor. But, no telemetry update sent to Ubidots.
ets Jun 8 2016 00:22:57
rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:1100
load:0x40078000,len:9232
load:0x40080400,len:6412
entry 0x400806a8
A8:03:2A:57:E0:9C
Seconds since last loop: 11.51
{"type":"IOT Gateway","model":7,"buzzer":0,"ssid":[{"ssid":"Harriman","rssi":-54,"encryption_type":true,"bssid":"E4:90:7E:F9:D1:C4","channel":1,"selected":true},{"ssid":"Spacfx","rssi":-79,"encryption_type":true,"bssid":"30:57:8E:14:BE:46","channel":1},{"ssid":"Fanaika","rssi":-82,"encryption_type":true,"bssid":"30:57:8E:93:C4:26","channel":1},{"ssid":"Go Beavs!","rssi":-84,"encryption_type":true,"bssid":"F0:9F:C2:D4:F2:0A","channel":6},{"ssid":"GoBeavs2","rssi":-84,"encryption_type":true,"bssid":"FA:9F:C2:D4:F2:0A","channel":6},{"ssid":"M Go Blue","rssi":-93,"encryption_type":true,"bssid":"14:91:82:96:19:08","channel":3}],"ssid_password":"__SET__","interval":5000,"azure_enabled":1,"http_enabled":false,"serial_print_enabled":false,"apPass":"__SET__","apSSID":"WiFi_Micro_Gateway","dhcp_enabled":1,"static_ip":[192,168,1,2],"default_gateway":[192,168,1,1],"subnet_mask":[255,255,255,255],"dns_primary":[8,8,8,8],"dns_secondary":[8,8,4,4],"update_available":false,"update":false,"update_path":"","firmware_version":"1.0.1","wifi_enterprise_username":"","wifi_enterprise_identity":"","mac":"","local_ip":"","cloud":{"host":"industrial.api.ubidots.com","host_ip":[0,0,0,0],"host_port":1883,"tls":0,"client_id":"yong_home","user_name":"XXXX-private","user_topic_format":"/v1.6/devices/::Sensor_ID::","user_gateway_topic_format":"/v1.6/devices/::Gateway_ID::","custom_ids":{},"message_format":"::Sensor_Data::","gateway_message_format":"::Gateway_Data::","node_receive_topic":"endnodereceive","node_transmit_topic":"endnodetransmit"},"nodeConfig":false}
Configured Devices: {}
# ...
Configured Devices: {}
ets Jun 8 2016 00:22:57
rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:1100
load:0x40078000,len:9232
load:0x40080400,len:6412
entry 0x400806a8
A8:03:2A:57:E0:9C
Not updating
settings.update is false
update path is blank
Seconds since last loop: 5.03
Pass is null
I put a # ... where it repeatedly displays Configured Devices: {} about fifty or so times. This is surprising, because the list here is empty, but I do see the sensor listed in the gateway’s web-based config Devices list. (!)
The last bit at the end is displayed after the config mode times out and the device resets into run mode.
