There had been an issue with TCPClient in the Electron that fully stopped this integration from working, but the new 0.5.0-rc.2 release from Particle now allows them to work great together! If you would like to see how to upgrade your Electron to this version, please see here: https://github.com/spark/firmware/releases/tag/v0.5.0-rc.2
One note, the Electron uses a new version of protocol to talk to the spark cloud based on UDP instead of TCP. Bluz, on the other hand, still uses the same TCP protocol that the Photon and Core use. Therefore, it sends a heartbeat to the cloud every 15 seconds and this will absolutely eat up a lot of your data plan on the Electron if you leave this running round the clock.
The long term solution is to switch bluz to UDP, but that may be far off. There is one good side, and that is that bluz already uses a hidden feature on the TCP side that allows these heartbeats to not happen, but the cloud still reports it as online. Normally with a Core/Photon, if it doesn’t get the heartbeat after X iterations, the cloud says it is offline. But bluz can turn that off, and the only way the cloud thinks it is offline is if the TCP socket actually closes.
So, a feature we need to get in place quickly is the ability to turn off the heartbeats in bluz. We will try and get this done quickly, and it will be optional. The other option, and more immediate solution, could be to throttle the traffic at the gateway for now. The Electron knows when a device connects, and knows how big the heartbeat packet is. So some simple filtering in the Electron could stop the traffic from going through, but still allow important traffic (function calls, publishes, etc.). This is a hack, for sure, but it could work in the immediate term if someone needs to get this working quickly and doesn’t want to pay a bunch for data.