IoT with Raspberry Pi and FEZ Cream

Today we’d like to highlight brandtbridges’ project on Codeshare:

Raspberry Pi Sensor Client - HTML5, CSS3, JavaScript, WCF Web Service

Live demo:

It uses our FEZ Cream HAT with Raspberry Pi 2. This project was inspired by his personal interest in Home Automation. Now that it’s all working, he wants to share his project, so others can learn from it.

Go to his website’s Projects to learn more about him and his projects.

Products used in this project available in our catalog:
Raspberry Pi 2 -
FEZ Cream -
TempHumid SI70 -
GasSense Module -



This seems like a nice platform in addition to the Fez Spider ii. I have a couple of questions:

1.) How would one connect to GPRS from this platform (IoT with Raspberry Pi and FEZ Cream). The Fez Spider ii has a GPRS module that is supported but I cannot find any documentation around IoT with Raspberry Pi and FEZ Cream module and GPRS.

2.) For a pure Iot project, one that sits in box on some farm some where in the ethos with only power and little human intervention, what is a better approach (Reliability, downtime etc.) - Cream with sensors on top of RPi or Fez spider with all the modules supported?


Riaan Mastenbroek

For #1, you’d have to see if there is already code for the GPRS module (do you mean Cellular?) for FEZ Cream (I haven’t looked, so I can’t say, but you can check at [url][/url]). If not, you could go find the module driver code on GHI’s Bitbucket ([url][/url]) and port it for IoT Core, which is not too difficult.

For #2, I’d probably recommend sticking with Spider II, as I’m pretty sure that RPi is more power-hungry than a Spider II, probably by a fair amount, so particularly if the application requires remote installation where it would rely on either battery or solar, you’d want a lower-power brain for your device. If it’s plugged in, you could probably use either, but if your preference is for Gadgeteer modules with full driver support, again, Spider II might be the better course.

The FEZ Cream makes for a very useful HAT if you already have a bunch of modules and really want to use RPi rather than a Gadgeteer mainboard, but in terms of low-friction git-r-dun development, going all Gadgeteer is probably still the better way to go.

Hope that helps.


Makes sense!!

Glad I chose right then!

Thanks for the feedback.


My pleasure!

Welcome to the forums!