Piface binding

[GoogleCodeExporter]

My request might point in direction of a generic communication binding rather 
than making changes to the Piface binding. Let me know what you think.

I have been looking at Ben's excelent Piface binding, and came to the 
conclusion that it could do what I need for 95%. My usage is a Raspberry Pi 
without a Piface board. On my Raspberry I am using Pi4j to monitor pin 0. 
Since it is the state of a smokedetector I need some sort of watchdog mechanism 
on the connection.
I have also ordered a DHT22 humidity sensor. It is not a Dallas 1-Wire sensor, 
so it needs its own pin and its own software. There are some samples on how to 
read out the sensor. For transmitting data from my Raspberry to OpenHAB  I 
there need something more flexible than a byte. I need something that will fit 
values between 0 and 100. 

I don't know if you think this points in a completely wrong direction of the 
Piface binding. I can argue for both that it does and also that it doesn't.

Please let me know if the above is possible to do in the piface binding or I 
have to start another binding?

/Martin

Original issue reported on code.google.com by mr.eskil...@gmail.com on 24 Sep 2013 at 7:51

[GoogleCodeExporter]

Besides from having something that could values in the range 0 to 100, I 
completely forgot about the temperature part of DHT22. So a string would be 
nice....

Original comment by mr.eskil...@gmail.com on 24 Sep 2013 at 8:18

[GoogleCodeExporter]

I would suggest doing the DHT22 monitoring in a separate script (calling the 
software you mentioned) and use the openHAB REST API for sending data back. No 
need to complicate the PiFace binding for this I don't think. 

The watch dog idea is a good one however, it has been on my TODO list for a 
while. I will hopefully get a chance to implement this soon.

Original comment by ben.jone...@gmail.com on 25 Sep 2013 at 2:09

[GoogleCodeExporter]

Using the OpenHAB REST API for more complex data sounds like a great idea. I 
also like to keep stuff uncomplicated ;-)

Doing the watchdog would be fine. 

/Martin

Original comment by mr.eskil...@gmail.com on 25 Sep 2013 at 5:57

[GoogleCodeExporter]

Watchdog has been implemented and pushed to my fork 
(https://github.com/sumnerboy12/openhab/commit/3b3e9fafc266436f8c818d64f4549bddf
459bea9).

Original comment by ben.jone...@gmail.com on 25 Sep 2013 at 11:00

[GoogleCodeExporter]

Original comment by teichsta on 5 Nov 2013 at 10:53

• Added labels: To-Github

[GoogleCodeExporter]

This issue has been migrated to Github. If this issue id is greater than103 its 
id has been preserved on Github. You can open your issue by calling the URL 
https://github.com/openhab/openhab/issues/<issueid>. Issues with ids less or 
equal 103 new ids were created.

Original comment by teichsta on 17 Nov 2013 at 8:08

• Added labels: Migrated-To-Github

[GoogleCodeExporter]

Set status to "invalid" to show that these issues are not tracked here anymore 
- please refer to GitHub instead!

Original comment by kai.openhab on 2 Dec 2013 at 7:12

• Changed state: Invalid