A user recently posted a copy of the old firmware and downgrade/restore instructions on github.
WARNING: this is not for the faint of heart/technically challenged. The brief steps are: run an SSL webserver, redirect the requests for some greenwavereality.com domains to your webserver, serve the old firmware.
More details: https://github.com/hypergolic/greeenwave_firmware
I was able to use this to de-brick a hub that I brought online a few weeks ago for the first time since before the firmware fiasco.
I now successfully have a restored hub and my lights are all working again. Investment recouped. Getting it integrated with ST… is the next challenge.
Looking now for a local integration for the old-style firmware, but would be interested/willing to upgrade/run a local proxy if it means smoother/more reliable integration.
Also, not sure how much effort has been put into it, but in poking around on the firmware for -the tcp device- it seems to be a Jennic 5618 zigbee radio, so it shouldnt be too unpossible to figure out how to speak directly with these units now that we have access to the device…
studio:~ adam$ ssh root@tcp-hub The authenticity of host 'tcp-hub (192.168.1.7)' can't be established. ECDSA key fingerprint is SHA256:DDPLwW889ZCIzPdc/iOl2m/ZqjsJdFl5riEbc9uPHcI. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'tcp-hub,192.168.1.7' (ECDSA) to the list of known hosts. root@tcp-hub's password: ~ # pwd /root ~ # uname -a Linux lighting 3.5.3 #1 PREEMPT Tue Dec 3 10:44:29 CET 2013 ppc GNU/Linux ~ # date Wed Dec 31 16:31:28 PST 1969 ~ # Connection to tcp-hub closed. studio:~ adam$ date Mon Aug 8 23:30:44 PDT 2016 studio:~ adam$