io_guy

Getting status back and additional humidity control

You can control via the network module. If you want additional functionality, check out VenLink.

I'm writing a program (that runs on a separate computer or Pi) that will link a GEM to the ISY.

MWareman, In your config we'll either need the DB to send data out more generically, or you'll need to add Ethernet to GEM. ppitkin, My current app can decode either ASCII or SEG format and then re-encode to send up to SEG. If the DB allows it (I have no idea how it actually communicate/authenticates with the GEM) I could easily re-encode to HTTP GET as well and send to the DB.

Fair enough. Then we can see if being a middle man would work. GEM can send to Dashbox via TCP/IP (HTTP Get Brultech Packet Type 3). If the Dashbox allows it, I could decode this format for ISY data and then mirror it through to the Dashbox.

If it'll send out SEG I can likely get it to work. That's what I'm running right now.

My program talks directly to the GEM. I also plan on handling the GEM data in SEG format so that I can forward the data along to SEG (Right now it appears the GEM will not support sending to SEG locally and still allowing me to connect for push data). Unfortunately I can't find any documentation on the Dashbox or it's communication capabilities.

Progressing well, will be released once V5 stabilizes.

All channels will have the info you show in main, accessible in programs. I'm not terribly keen on keeping separate counters within the node server - you miss data if it's not running for some reason.

Yes to all.

1. See my post in V5 as an example. I have a Venstar thermostat showing up as if it was a native stat. The creator of the node server has a lot of flexibility here. 2. These would all show up as native ISY nodes, similar to devices or weather info, etc. They can be used in scenes, programs, whatever.

Not trying to be difficult, but I still have no idea what you're asking in the first paragraph of your post above.

I have no idea what you're asking. I've told you what the app will do, if you want info on node servers read the V5 forum and docs.

Multiple GEMs is no problem. I'll have to investigate Dash support once things are up and running.

Got my GEM late last week and started playing. Should be no problem getting this running. I'll be making an ISY V5 node server for this that will make all energy channels, counters and temperatures available. I'll support a few data formats so that data can be sent to SEG at the same time (for example).

You can't find a close enough weather station? It may not be exact but should be good enough for thermostat play.

So I have a GEM coming my way. My program will use the standard Ethernet module (not the Dash Box or Zigbee) and provide all data to the ISY. This should include channels, counters and one-wire temperature as well.

The Python link you supplied appears to scrape the TC Site, not access a proper API. Honeywell have been less than helpful thus far. I use a Venstar.

Sorry, I have no intention of scraping their website. If they can't provide a decent API they shouldn't be in home automation.

I've tried three times to apply on their stupid website without success. If they ever let me in I'll write an app.

I've been chatting with Brultech on getting a GEM. If things work out I'll be writing a V5 node server to integrate via Serial/Ethernet.

Standard Cat5e here, star pattern (home run), about 1000' and counting.

Not as difficult as you mention here. - Headless - no HDMI, KB or Mouse required. I've never connected a monitor to a Pi. - Install Wheezy per guide in forum. - Configure OWFS and one-wire board per Sheepwalk's info. - Install OWLInk. - Done, no programming or Phython required.

The WC uses the GPIO bus to big-bang (software) its one-wire. This is why the distance is poor. Grab a hardware one-wire chip for the Rasp Pi and you'll have no issues. It also supports unlimited temp and humidity sensors.

About $300 by the time I get it. Looks like I'll be waiting a while.