ZBBridge: IKEA bulb losing connectivity after Tasmota restart

s-hadinger commented 4 years ago

PROBLEM DESCRIPTION

A clear and concise description of what the problem is.

Sonoff ZBBridge: IKEA bulb loses connectivity after a Tasmota restart.

REQUESTED INFORMATION

Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!

[x] Read the Contributing Guide and Policy and the Code of Conduct
[x] Searched the problem in issues
[x] Searched the problem in the docs
[x] Searched the problem in the forum
[x] Searched the problem in the chat
[x] Device used (e.g., Sonoff Basic): Sonoff ZBBridge
[x] Tasmota binary firmware version number used: 8.4.0
- [x] Pre-compiled
- [ ] Self-compiled
- [ ] IDE / Compiler used: _____
[x] Flashing tools used: esptool.py

[x] Provide the output of command: Backlog Template; Module; GPIO 255:

16:56:54 MQT: stat/tasmota/ZBBridge/RESULT = {"NAME":"Sonoff ZBBridge","GPIO":[56,208,0,209,21,22,0,0,6,158,5,0,17],"FLAG":0,"BASE":18}
16:56:54 MQT: stat/tasmota/ZBBridge/RESULT = {"Module":{"75":"Sonoff ZbBridge"}}
16:56:55 MQT: stat/tasmota/ZBBridge/RESULT = {"GPIO0":{"56":"Led1i"},"GPIO1":{"165":"Zigbee Tx"},"GPIO2":{"0":"None"},"GPIO3":{"166":"Zigbee Rx"},"GPIO4":{"215":"Zigbee Rst"},"GPIO5":{"0":"None"},"GPIO9":{"0":"None"},"GPIO10":{"0":"None"},"GPIO12":{"6":"I2C SDA"},"GPIO13":{"158":"LedLinki"},"GPIO14":{"5":"I2C SCL"},"GPIO15":{"0":"None"},"GPIO16":{"17":"Button1"}}

[ ] If using rules, provide the output of this command: Backlog Rule1; Rule2; Rule3:

16:57:27 MQT: stat/tasmota/ZBBridge/RESULT = {"Rule1":"ON","Once":"OFF","StopOnError":"OFF","Length":78,"Free":433,"Rules":"on zbstate#status==0 do backlog zblisten1 0; zblisten2 99; zblisten3 100 endon"}
16:57:27 MQT: stat/tasmota/ZBBridge/RESULT = {"Rule2":"OFF","Once":"OFF","StopOnError":"OFF","Length":0,"Free":511,"Rules":""}
16:57:28 MQT: stat/tasmota/ZBBridge/RESULT = {"Rule3":"OFF","Once":"OFF","StopOnError":"OFF","Length":0,"Free":511,"Rules":""}

[ ] Provide the output of this command: Status 0:

16:58:22 MQT: stat/tasmota/ZBBridge/STATUS1 = {"StatusPRM":{"Baudrate":115200,"SerialConfig":"8N1","GroupTopic":"tasmotas","OtaUrl":"http://thehackbox.org/tasmota/release/tasmota.bin","RestartReason":"Power On","Uptime":"0T00:04:44","StartupUTC":"2020-08-01T15:53:38","Sleep":50,"CfgHolder":4617,"BootCount":578,"BCResetTime":"2020-06-11T18:29:13","SaveCount":1327,"SaveAddress":"F7000"}}
16:58:22 MQT: stat/tasmota/ZBBridge/STATUS2 = {"StatusFWR":{"Version":"8.4.0.1(tasmota)","BuildDateTime":"2020-08-01T09:47:37","Boot":31,"Core":"2_7_3_2","SDK":"2.2.2-dev(38a443e)","CpuFrequency":160,"Hardware":"ESP8266EX","CR":"424/699"}}
16:58:50 MQT: stat/tasmota/ZBBridge/STATUS3 = {"StatusLOG":{"SerialLog":0,"WebLog":2,"MqttLog":0,"SysLog":0,"LogHost":"","LogPort":514,"SSId":["Tasmota",""],"TelePeriod":300,"Resolution":"55C180C0","SetOption":["00C08009","2805C8000100060000005A00000000000000","00000000","00046002"]}}
16:58:50 MQT: stat/tasmota/ZBBridge/STATUS4 = {"StatusMEM":{"ProgramSize":567,"Free":436,"Heap":21,"ProgramFlashSize":1024,"FlashSize":2048,"FlashChipId":"1540A1","FlashFrequency":40,"FlashMode":3,"Features":["00000809","0F0007C6","04500001","00000002","00000000","00000000","00020000"],"Drivers":"1,2,4,9,10,20,21,23,41","Sensors":""}}
16:58:50 MQT: stat/tasmota/ZBBridge/STATUS5 = {"StatusNET":{"Hostname":"tasmota/ZBBridge-0879","IPAddress":"192.168.1.92","Gateway":"192.168.1.1","Subnetmask":"255.255.255.0","DNSServer":"192.168.1.1","Mac":"B4:E6:2D:7F:C3:6F","Webserver":2,"WifiConfig":4,"WifiPower":17.0}}
16:58:50 MQT: stat/tasmota/ZBBridge/STATUS6 = {"StatusMQT":{"MqttHost":"a3pa4ktnq87yfu-ats.iot.eu-central-1.amazonaws.com","MqttPort":8883,"MqttClientMask":"DVES_%06X","MqttClient":"DVES_7FC36F","MqttUser":"DVES_USER","MqttCount":1,"MAX_PACKET_SIZE":1200,"KEEPALIVE":30}}
16:58:50 MQT: stat/tasmota/ZBBridge/STATUS7 = {"StatusTIM":{"UTC":"2020-08-01T15:58:50","Local":"2020-08-01T16:58:50","StartDST":"2020-03-29T02:00:00","EndDST":"2020-10-25T03:00:00","Timezone":"+01:00","Sunrise":"05:25","Sunset":"20:28"}}
16:58:50 MQT: stat/tasmota/ZBBridge/STATUS10 = {"StatusSNS":{"Time":"2020-08-01T16:58:50"}}
16:58:50 MQT: stat/tasmota/ZBBridge/STATUS11 = {"StatusSTS":{"Time":"2020-08-01T16:58:50","Uptime":"0T00:05:12","UptimeSec":312,"Vcc":3.504,"Heap":21,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Wifi":{"AP":1,"SSId":"Tasmota","BSSId":"76:83:C2:90:D6:15","Channel":1,"RSSI":88,"Signal":-56,"LinkCount":1,"Downtime":"0T00:00:03"}}}

[ ] Provide the output of the Console log output when you experience your issue; if applicable: (Please use weblog 4 for more debug information)

TO REPRODUCE

_Steps to reproduce the behavior:

I paired an IKEA white/CT bulb to Z2T. The bulb acts as a Zigbee router. When I reboot Tasmota/coordinator, the IKEA bulb does not respond to commands anymore. I checked with a Zigbee sniffer, the commands are correctly sent in the air, but for an unknown reason the IKEA buld ignores the packets. The bulb still send 'Link status' packets as required by a router. When I power off/on the IKEA bulb, it reconnects to the coordinator (Device announcement...) and everything works fine again.

EXPECTED BEHAVIOUR

A clear and concise description of what you expected to happen.

Using CC2530 the issue does not happen. There is something wrong with routing on ZBBridge maybe linked to Zigbee V3.

SCREENSHOTS

If applicable, add screenshots to help explain your problem.

ADDITIONAL CONTEXT

Add any other context about the problem here.

This is a follow up from #8583 to have an issue dedicated to this problem.

(Please, remember to close the issue when the problem has been addressed)

MattWestb commented 4 years ago

Not importing was only curious if it was easy way to getting the information but its also working the "mechanical" way (Main power for the apartment off and on) and having the laptop running on battery ;-)))

Adminiuga commented 4 years ago

And I do call setInitialSecurityState at each reboot - maybe I shouldn't.

@s-hadinger I don't think there's real need to "form" network each time you reboot, i.e. setInitialSecurityState. EmberZNet does a decent job storing those in NVRAM. You could call networkInit and then check StackStatus and nodeType and form if the network is not there or the node type is not coordinator.

MattWestb commented 4 years ago

@Adminiuga I some time having problems that the NCP have stored bad things in the NVRAM (SimEEv2 I think its on the 1 gen geckos for storing tokens) in HA and then i moving between host applications. Normally the Ikeas new motion sensor (ZB3) can paring one time and after that its not possible its only leaving the mesh (for the moment its working in tasmota reparinga and rejoining). Then erasing the flash and flashing bootloaders and NCP its working normal. Do you knowing if its some easy way "resetting / erasing" the NVR / SimEEv2 (master reset / token cleaning) ? Silab is recommending first erasing the internal flash before flashing the NCP with EZSP then using it with there demo GW (then the EZSP is making one new clean SimEEv2 in the upper free flash). I have not testing going from HA to current tasmota then I have the problem and resetting the devices and repairing them in tasmota (for see if Tasmota can fixing the problem in the NVR then rewriting the tokens). For my its no big problem in alpha / beta test phase but later for users that don't have SWD programming available (loading one flash size(minus BL size) GBL file with "FF" and then the EZSP with Xmodem can being one workaround for user). What i have reading is that TI having similar problems and need reflashing the NCP from time 2 time (from Z2M forum).

Adminiuga commented 4 years ago

This may be related to the keys NCP stores for ZB3 devices. If you reset the device, you should remove the key from the NCP

MattWestb commented 4 years ago

Sounds more than likely. I keep watching if its coming back. I think tasmota is making it right now but was problem before the maior ZB3 fix. Bellows with 6.6.4.0 looks ok but have not testing so much. For the moment is being one mess with 6.7.4.0 if mowing from tasmota and not erasing the flash and flashing bl and EZSP.

s-hadinger commented 4 years ago

@Adminiuga I'm now doing what you mention. I call initNetwork then check parameters and call formNetwork only if I need to change parameters (ex PanID)

arendst / Tasmota