Here is the completely redesigned Ruuvi Gateway circuit board with ethernet connectivity:
Trying to think of size, and scaling from the ports, it looks a little bigger than 2 RPis side by side. Is that right? Can you give some dimensions?
The PCB is about 10 x 6cm
Nice that ethernet made its way to the gateway. PoE would be a nice improvement for maybe a next revision.
Is there a further roadmap of this project available?
PoE can be supported with an external splitter, we do not have plans of supporting internal PoE at least yet.
Hey everyone! It’s time for a Gateway update.
Lately, we’ve been working with mechanics, firmware, configuration user interface, backend, antenna simulations, custom antenna manufacturing and other tasks that have to be taken care of in prior the mass production. Selected beta testers will get their hardware pieces starting from next week. Everything is moving forward nicely.
Here is the latest mechanics design for your comments:
And the circuit board:
The Gateway will be easy to use and quick to set up, but we’ve also designed the the mechanics (and software) to be hacker friendly. Ruuvi Connector flex cables are supported and a large sized expansion board will fit nicely inside the enclosure. More in-depth info and expansion board template KiCad project(s) will be shared later.
Questions, comments? Yes, please!
Looks terrific. Does the firmware currently limit ‘harvesting’ to only Ruuvi tags?
The current firmware listens in to all Bluetooth transmissions, so you can use it with iBeacons, Eddystone beacons and even to check e.g. Windows PC beaconing messages. Currently only limitation is that data has to be in advertisement and at 1 MBit / s, BLE 5.0 features such as long range or extended payload secondary advertisements are being worked on.
Any ETA when this will be out?
What options there are to connect this to the mobile network?
ETA to start mass production is currently not later than Q1 2021. We work hard to get everything ready asap, and more early access devices will be available earlier than that.
This is the Rev.A1 circuit board prototype:
and this is the mechanics status:
You can use pretty much any internet access point that offers WiFi or Ethernet connectivity. We have also reserved room for internal expansion shields and wireless connectivity circuit boards (for example LoRaWAN and NB-IoT) are planned for the future.
Does this mean that Ruuvi Node is dead? Are there any plans for a device with direct mobile network connection?
Not dead but postponed. We do have plans, yes. And we’re continuously prototyping with direct mobile connectivity, too. But currently, I cannot give you promises about exact production schedules. You can find some open source code here:
Thanks for the update and clarifications.
We are working on a project where we would send an alarm message to a mobile phone a) whenever a reading (e.g. temperature) from a monitored Ruuvi tag is out of the allowed range and b) whenever too long time has passed since data has been received from a monitored Ruuvi tag (tag dead or out of range).
We think that the coming Ruuvi Gateway would be a good starting point, but how to implement the rest? It would be nice to find something as compact as a Raspberry Pi but with much better support for a mobile network connection and messaging such as SMS or Telegram.
I think here’s two different problems, a gateway with mobile connection and alerting. There are routers with mobile connectivity options, and the alerting can be done with e.g. server on the cloud, InfluxDB and Grafana.
We’re also working on our own backend for tag data, https://github.com/ruuvi/ruuvi-network-serverless
Thanks for your input. Are you saying that there are no devices that could handle both the mobile network connection and the alerting directly to a mobile phone?
I’m sure there are plenty of devices which could handle the mobile connection and alerting, simplest choice is a mobile phone. Mobile phones aren’t too reliable long-term though. Some GPS trackers for example have Bluetooth scanning and alerting features.
Thanks. One of the best features of the Ruuvi tags is that they provide useful data without any effort from the user. When the Gateway becomes available, what will it do “out of the box”? For example, could we connect it to a PC through Ethernet and collect the tag data that way?
Out of the box the data will be sent to Ruuvi’s backend, but you can configure your own server such as LAN IP address. [EDIT]: There’s no fixed release date, I’d estimate GW is available Q4/2020 or Q1/2021. There’s always some risks in product development which may cause delays.
It would be very handy if the Gateway would have more modes than just one and they could be selected by pressing buttons just like in the tags.
There’s too much configuration options to select one with button presses, that’s why Gateway has a WiFi hotspot for browser-based configuration