If you want to hire someone to make one of these, it would probably be bad investment. If you want to make several or to sell them, that is possible. A little modification of your requirements would help.
The basic device could consist of a WiFi-capable Arduino and a sensor. This could be an Arduino with WiFi on it such as Yun, or any Arduino with a WiFi shield or any of many clones.
To use the device for the first time, the user would need to set it up. The procedure is spelled out for Yun. For some other solutions, there may be a little bit of programming. The idea is that the Arduino starts out as its own network. The user connects to it as if it were another router. Then the user enters into a web page, the name and password for a local router. This procedure only needs to be done once as long as the device and the router don't go away.
The sketch on the device would read the sensor periodically. It would periodically report the results by sending a message as an internet web client containing a report.
Another program, running on a web server would receive the report, store it and send out email as appropriate. You would probably want some other programs running on the server to present the data in a user-friendly form.
How would you get there?
- Find the sensor.
- Have a programmer write a sketch to display the values it reads from the sensor in Arduino IDE. The programmer may need to emulate the sensor rather than buy and install an actual sensor.
- You will then need to duplicate whatever a programmer produces for you, running on actual sensor connected to an Arduino.
- Once the sensor checks out, the next step is for the programmer to write the web client part. Of course to check out the web client, the programmer will need to write a little bit of server-side code to store values.
- At this point, you will have the Arduino part coded. Before deploying it, you may want to make an enclosure with properly mounted connectors, possibly a pilot light.
- If you want a low-power solution, you may want to have your own PCB with one of the low-power processors. Then you want the programmer to add code to make the processor go to sleep between readings.
-Finally, have a programmer add to the server-side code the email alerts and whatever data viewing mechanisms are useful.
I'm interested in knowing how this would satisfy the requirements of vilasalvas.
I'm also interested in learning how others would solve the problem based on what has been said.