That’s fine, but I believe that “HOST: …” is being sent to iTach, which may be harmless in this particular case, but is generally undesirable.
Yeah… NC is showing it is. Ok… I’ll pull that and use deviceNetworkId.
So how are you specifying a port? In the DNI or the ip var?
I was setting ip to “10.0.0.41:4998”. It has always worked, but I was always sending to an http server. So now I’ll just pop ‘0A000029:1386’ into the DNI and lose the HOST param.
Seems to work fine.
what about using this device with eventGhost?
Unfortunately my device is a serial version (not USB), so I’m kinda SOL… wish I could test. but my machine is to old.
However, if it works with EventGhost, you could do everything relatively simply (not serious programming involved).
Anyone want to trade a USB version for my serial version?
Great job. I, too, have developed an x10 integration solution, and I’m sure you realized as I did that it wasn’t easy.
Question: Let’s say you have x10 switches for codes A1, A2 and A3. Do you have to write a custom device type for each one with the housecode embedded in the custom device? I have not found a way to have one custom device that can be used for multiple X10 devices as separate instances.
I’m dealing with the fact that I have to create a separate device type for each housecode. If you know a better way, I’d love to see it!
ps. I approached x10 integration through a custom hardware solution using *duino, a cm11a and a smartshield (X10 working! Requires about $115 in hardware, but is fully self-contained!). It’s good to have multiple ways of skinning this cat.
No, there’s only one device type for all X10 switches. Device instances are created dynamically by the service manager app.
It’s good to have multiple ways of skinning this cat.
I agree. Both solutions have their advantages and disadvantages.
Will this X10 bridge program become intergrated into the SmartThings App one day?
I’m now using Insteon(sorry for using this name in this forum) to power my X10 bedroom light.
If SmartThings intergrates this program into their mobile app, it will open a lot of possibilities.
I’m planning to release it to the “shared” apps section soon, but installing a shared app is not a particularly smooth process. Hopefully, ST will make it easier in the future.
what about my question above ?
Sorry, I’m not familiar with EventGhost.
you should check it out… might solve some or more challenges.
in an effort to make things simpler, I have discovered X10 commander, which spits out a friendly web server where you can simply access your X10 devices using the CM19A via an “app”, a web server or (because of the web server), UBI, SmartThings, or anything that can do a httpGET.
This has just made things a WHOLE lot easier! It’s stupid easy!
Did you mean this http://melloware.com/x10commander/ ?
If not, would you mind posting a link?
yup. exactly. I have to use it in conjunction with firecracker running (Win 7 machine)… I use my *nix machines for other stuff… but in setting those two things up, it works GREAT! Simple GUI… I get all my codes… really liking the simplicity and ability to use it anywhere since its’ a mini server.
Oh, and you may be VERY interested in what EventGhost has to offer for extra explosive and dynamic functionality.
X10 commander uses raw sockets API on port 1033 or something, as far as I remember. I looked at it long time ago. And on Linux, it’s implemented as a shell script on top of Heyu, which does not support USB adapters (CM15 and CM19). I don’t see how it could solve the problem here.
Sorry, I wasn’t seeing a problem, rather an additional solution to the subject of the thread… getting X10 to work on SmartThings.
That is exactly what I’m trying to do now - to get SmartThings to talk to X10 Commander server. I have a number of scripts etc. that I already use X10 Commander for. However, I’m a total noob to SmartThings so don’t really know where to start coding-wise, in terms of constructing a suitable httpGET for it. Do you have any examples you would be prepared to share please?
It would seem like there’s an opportunity to create a generic ST to X10 gateway via HTTP using either mochad or X10 Commander though.
For those that have dedicated Windows hardware doing home automation stuff already, or that use serial port devices, X10 Commander seems like a logical choice.
For those that have Linux hardware then running mochad would work best, but hopefully with the same SmartApp that handles interfacing with the bridges.
I am using mochad on a qnap nas, installs as a qpkg, not very advanced, but works. Plug in the cm19 and use the ST X10 gateway.