Sonoff Zigbee Bridge not connecting to WiFi

[Brian A]

I flashed a Sonoff Zigbee Bridge with 'tasmota-zbbridge.bin'. I was able to access the flashed bridge on 192.168.4.1. I scanned for networks and chose my network for the configuration. My SSID is only 8 characters long. I set the WiFi password such that it consisted only of number and letters - no white spaces etc. The secondary network was not set. After saving the configuration I used nmap to look for the IP on my network (Huawei EG8145V5 router), it was not there.  I also checked the password as sent in the Firefox browser history - perfectly fine. I have reset the Bridge several times by the fast power cycle method (other methods did not work) and tried again, plus rebooting etc. etc. - all to no avail. I should add that I have a Sonoff Basic switch running Tasmota on the same network and that works perfectly well, even with 'special' characters in the WiFi password.
Is there anything I can do now please?  Advice gratefully received.

[Philip Knowles]

If you can access it via serial you can use something like ESPlorer to read the ipaddress and the log as it boots (or use backlog ipaddress1 x.x.x.x; restart 1 to set a static IP). Any terminal programme will also read it.

Having said that I normally just log into my router to find new devices in the DHCP list.

 

Regards

 

Phil K

 

Sent from Mail for Windows 10

--
You received this message because you are subscribed to the Google Groups "TasmotaUsers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sonoffusers...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/sonoffusers/fb249745-74a7-48c6-bebf-db705a9c5abcn%40googlegroups.com.

 

[Brian A]

Thank you for your reply but the issue isn't inadequate software to detect the hosts on the network, as nmap does a good job of this and, indeed, I can also check my router. No, it is the fact that the Zigbee bridge simply doesn't connect to the network. So I am lost on what to do.

[Lark Box]

Afaik the only way to debug would be to re-establish the serial connection used to flash and use a serial monitor tool or terminal emulator like putty to monitor the serial output while the system starts up for any errors.. there are a couple of issues that can result in a 'boot loop'  which are generally resolved by a reflash,

[Philip Knowles]

As I said

If you can access it via serial you can use something like ESPlorer to read the ipaddress and the log as it boots (or use backlog ipaddress1 x.x.x.x; restart 1 to set a static IP). Any terminal programme will also read it.

Having said that I normally just log into my router to find new devices in the DHCP list.

 

 

Sent from Mail for Windows 10

To view this discussion on the web, visit https://groups.google.com/d/msgid/sonoffusers/ac952829-ea2b-499f-bf4f-2f1b07266eabn%40googlegroups.com.

 

[ryan...@gmail.com]

Not convinced you can read serial data from this device: the Blakadder page suggests "you cannot configure the device over serial with this binary". Perhaps serial is tied to the ZigBee chip?

Anyway, I had the exact same issue after entering my WiFi details, which itself took a couple of attempts because it was unstable. What resolved it for me was desoldering the wires used for flashing, something the Blakadder pages strongly recommends. I also reflashed before doing that to start afresh.

Good luck!

[benjam...@t-online.de]

Since I had to complie anyway for suport of expressions and IF statements, I also added SSID, password and IP's of device, gateway and MQTT-Host in user_config_override. Entirely trouble free.