7 replies to this topic

[YvesGoeleven]

Not sure if it qualifies as a 'project', but I played around using my Netduino Plus 2 to turn on/off a lamp using an RF transmitter and a smart socket

 

I bought the following Kit: http://iprototype.be...first-rf434-kit, which consists of a 434Mhz RF transmitter and DIO smart sockets, and ported the arduino code for  the protocol of DIO to netduino.

 

If I got it right this protocol should be similar or equal for multiple vendors including DIO, KAKU & Home-Easy as they all use the same hardware (signal length may vary though)

 

The source code for the protocol is available on github

 

Enjoy turning on/off your lamps or other stuff at home

[hanzibal]

Sure it counts as a project, more than well!

I've done a fair deal of similar RF control stuff too and found it very rewarding.

Very interesting and great news!

I actually didn't think Netduino was fast enough for bit-banging this (not even Netduino 2) and thought you had at least use SPI for this.

The natural next step would be adding a webbserver so that you can use a smartphone as a remote control but I guess you already thought of that.

[YvesGoeleven]

Yes, that crossed my mind

 

But I won't be using a webserver, from a security & manageability point of view I don't want anyone to call into my devices. Instead I want them to call out, to an internet hosted (and well known) servicebus. Trusted apps can than send messages to that isecured endpoint.

 

PS: I will be releasing that bus to the public in a few days or weeks as well...

[hanzibal]

One would think you were in control of what devices are accessing your local network?

At least I think I am - of mine, not yours, that is :-)

[Paul Newton]

I agree with Hanz - that counts as a great "project".

 

Its always worrying connecting things up to the internet - I have held back so far.

 

Even without the internet, the idea of anything remote controlled from where the user can't supervise it, is a hazard. Even the simplest of devices could burn you're house down.

For example, the cat knocks over the desk lamp and when it is remotely turned on the bulb gets hot and burns the carpet....

 

I wonder if insurance companies will start to add rules about this sort of thing.

 

Paul

[hanzibal]

Aha, I thought we were talking about remote controlling from within the LAN only.

I wouldn't have my gear connected to the internet accessible from the outside world.

In some home automation product broshures, manufacturers push for things like being able to control the lighting in your home from away on vacation in another country or perhaps starting your sauna from the car on the way home. Dangerous madness.

[YvesGoeleven]

I'm monitoring my chilli seedlings remotely, the netduino is monitoring soil temp and sending the temp info to my phone (remotely). Now I'm adding capability to remotely turn on the illuminescent light. (I don't have a cat).

 

It's good feedback though that you guys are hesitant to hook devices up to the internet. I'm pretty confident it's safe for telemetry information, maybe commands that change your devices' state may be a bit different, I guess it depends on what you want to turn on/off.

[hanzibal]

Exactly, I see no hazards in what you're doing and naturally telemetry is harmless.

In my home, I got a networked IR gateway (iTach) for controlling all my A/V gear and built an RF bridge for controlling wall oulets like the ones you're using. I'm using my iPhone/iPad as a WLAN remote control but it only works within the domestic LAN.

http://www.avsforum....for-itach-irule