Home automation: In need of a developer (it should be rather easy)

[Moskus]

Now, then! I'm finally back from vacation.

I've had some development.

I'm now using the computer name and it shows as "VALID". So now I get the option to enter the port number. It's already got 10990 filled in, but when I try to close the dialog it states that the data is not valid.

10990 is the port I use in HomeSeer. And I can send text messages from HomeSeer to SageTV.

[lamanmi]

Moskus,

Originally Posted by Moskus

Now, then! I'm finally back from vacation.

I've had some development.

I'm now using the computer name and it shows as "VALID". So now I get the option to enter the port number. It's already got 10990 filled in, but when I try to close the dialog it states that the data is not valid.

10990 is the port I use in HomeSeer. And I can send text messages from HomeSeer to SageTV.

Welcome back. Can you send me a screenshot of what you are seeing?

[Moskus]

Yes, sorry for the delay, my 30 day trial was up so I had to renew the license. This is what I see, and it's the same on the Client, the HD200 and the PlaceShifters.




Another question: Do I need to have a separate port for each client/extender/placeshifter I intend to use with InConrol? I wouldn't think so, but I have to ask.

[Moskus]

Hello?

[lamanmi]

Moskus,

Did you try to Clear All Settings?

Any way you can enable debugging on both HomeSeer (InControl Settings Log Level=3) and Sage then restart both and get to this screen?

Also, been busy working on version 1.3 which will provide a System Info screen that will also help me debug connectivity problems. This version will also allow HomeSeer to control Sage .

[Moskus]

Here's something strange. If I (re)start the SageTV service AFTER HomeSeer has (re)started, my IP or computer name will show up as invalid. BUT if I start SageTV BEFORE HomeSeer, I can set the port number. Go figure...

See the attached logs.


PS! Looking forward to control Sage from HomeSeer!
(And to use this plugin at all! )

[exdirtfarmer]

Originally Posted by lamanmi

Moskus,

<snip>
Also, been busy working on version 1.3 which will provide a System Info screen that will also help me debug connectivity problems. This version will also allow HomeSeer to control Sage .

I finally updated SageTV to 7.x. I got incontrol software purchase, installed and working on sage whs install with placeshifter and hd200 as clients.

Thanks for all the work on this, I'm looking forward to your updates.

Now if only somebody nails down the Sonos integration, my houses core media/control functions will all be available from SageTV. I will see what I can hack together through homeseer control and homeseer Sonos scripts.

[lamanmi]

Moskos,

Originally Posted by Moskus

Here's something strange. If I (re)start the SageTV service AFTER HomeSeer has (re)started, my IP or computer name will show up as invalid. BUT if I start SageTV BEFORE HomeSeer, I can set the port number. Go figure...

See the attached logs.


PS! Looking forward to control Sage from HomeSeer!
(And to use this plugin at all! )

Thanks for the logs, this will definitly head me in the right direction. The first thing to check is if there is a copy of an old JAR in any of your Sage (server or client) JARs directory. Specifically look for "InControl_1.0.10.jar". If you find it, please shut down sage and then delete it. You should only have one InControl jar and it should be InControl_1.2.0.jar.

Let me know how that goes first......

[lamanmi]

exdirtfarmer,

Originally Posted by exdirtfarmer

I finally updated SageTV to 7.x. I got incontrol software purchase, installed and working on sage whs install with placeshifter and hd200 as clients.

Thanks for all the work on this, I'm looking forward to your updates.

Now if only somebody nails down the Sonos integration, my houses core media/control functions will all be available from SageTV. I will see what I can hack together through homeseer control and homeseer Sonos scripts.

That is great to here.....working hard on the new version with the ability to control sage...watch for it in the next 2 weeks.

[lamanmi]

Kent,

Originally Posted by PosterBoy

Hi Lamanmi.

I still can't get anything to work. The only time the I can ever get the server settings to say valid is if I have the sage client running on my laptop and start homeseer. As homeseer goes through its startup, the server settings on my laptop change from invalid to valid. From then on if I click to validate it stays valid. If I exit sage and restart it on my latop, it goes back to invalid, and wont go valid again until I stop Homeseer and start it up again.

Aside from that I can no longer get it to ever accept the username/password

Thanks

Kent

Were you ever able to get this working. Did you try version 1.2.0?

[Moskus]

Originally Posted by lamanmi

Thanks for the logs, this will definitly head me in the right direction. The first thing to check is if there is a copy of an old JAR in any of your Sage (server or client) JARs directory. Specifically look for "InControl_1.0.10.jar". If you find it, please shut down sage and then delete it. You should only have one InControl jar and it should be InControl_1.2.0.jar.

Let me know how that goes first......

AAARGH! Success! (As far as I can tell at work, the placeshifter here reports that it's able to log in, and the login credentials are correct, but so far no devices show up, even if they're marked as "controlable" in HomeSeer)

If this works when I get home (and it seems like it should), then you have yourself a new customer!

[PosterBoy]

Work/Sickness and Vacation have all played a part in me not digging into this lately.

I spent some time tonight and did have success.

I got it to work after a combination of proper resetting, turning off firewalls, and finding and removing the InControl_1.0.10.jar on my laptop and server. It now works on my laptop, server and at least one of my extenders.

Some caveats though:
I can only get it to work if my servers firewall is turned off. I tried a variety of settings including making sure HSPro has outbound access and allowing incoming connections on port 10990 (both UDP and TCP). Based on log info, it looked like HS was getting info from port 10990, but packets might not have been getting out. If you have any suggestions please do tell, and I will continue to dig into this as I have time. I am running server 2008.

It could not report my HSM100s temperature setting. It would only report ON or OFF

It could not report the current status of my schlage front door lock. The status was reported as unknown.

I got it running pretty late, so I could very well be doing something boneheaded.

I am very glad to get it working. I had it running for a bit, and it was very slick, then went through a long period where something that work and seemed simple to get to work just didn't no matter what I tried. I was getting very frustrated. I will experiment a bit more over the next few days

Thanks

Kent

[Moskus]

It's almost a success. I've configured several devices to show up in InControl, but so far only my kitchen device ("Kjokken") is present.

It seems like it should work based on the HomeSeer log:

10.08.2010 13:46:36 InControl_Sage modMain_ProcessMessage: Message=INIT;SAGE;Server;001d6a4cf53aFROM=JAVA;;JAVA
10.08.2010 13:46:36 InControl_Sage modMain_SendCommandTCP: Message=INIT;5741;Ekstra Soverom skjerm;Ekstra;Soverom skjerm;Off;09.08.2010 07:43;-1;light;N;Y;light_off.gif;0;3;;END
10.08.2010 13:46:36 InControl_Sage modMain_SendCommandTCP: Message=INIT;9195;Ekstra Ekstra lampe;Ekstra;Ekstra lampe;Off;07.08.2010 15:29;-1;light;Y;Y;light_off.gif;0;3;;END
10.08.2010 13:46:36 InControl_Sage modMain_SendCommandTCP: Message=INIT;4087;Kontroll Ovn i stue;Kontroll;Ovn i stue;Off;07.08.2010 15:28;-1;temperature;N;Y;temperature_off.gif;0;3;;END
10.08.2010 13:46:36 InControl_Sage modMain_SendCommandTCP: Message=INIT;751;Kontroll Utelys;Kontroll;Utelys;Off;09.08.2010 22:56;-1;light;N;Y;light_off.gif;0;3;;END
10.08.2010 13:46:36 InControl_Sage modMain_SendCommandTCP: Message=INIT;3450;Kontroll Stue;Kontroll;Stue;Off;09.08.2010 17:37;-1;light;Y;Y;light_off.gif;0;3;;END
10.08.2010 13:46:36 InControl_Sage modMain_SendCommandTCP: Message=INIT;8820;Kontroll Soverom;Kontroll;Soverom;Off;10.08.2010 07:50;-1;light;Y;Y;light_off.gif;0;3;;END
10.08.2010 13:46:36 InControl_Sage modMain_SendCommandTCP: Message=INIT;5998;Kontroll Gang;Kontroll;Gang;On;10.08.2010 12:48;-1;light;N;Y;light_on.gif;100;2;;END
10.08.2010 13:46:36 InControl_Sage modMain_SendCommandTCP: Message=INIT;1434;Kontroll Gjesterom;Kontroll;Gjesterom;Off;07.08.2010 15:28;-1;light;N;Y;light_off.gif;0;3;;END
10.08.2010 13:46:36 InControl_Sage modMain_SendCommandTCP: Message=INIT;209;Kontroll Kjokken;Kontroll;Kjokken;Off;10.08.2010 13:44;-1;light;Y;Y;light_off.gif;0;3;;END
10.08.2010 13:46:36 InControl_Sage modMain_SendCommandTCP: Message=INIT;909;Kontroll Teknisk rom;Kontroll;Teknisk rom;On;10.08.2010 13:24;-1;light;N;Y;light_on.gif;100;2;;END

... but only "Kjokken" shows up.

[Moskus]

OK, I've found the problem. Only devices that are actually trigged (turned on, off or dimmed) after the setup procedure will show up in InControl on the Extenders.

The same is true when I press "Refresh", I have to retrigger the devices to make them show up in SageTV.

[lamanmi]

Moskus,

Originally Posted by Moskus

OK, I've found the problem. Only devices that are actually trigged (turned on, off or dimmed) after the setup procedure will show up in InControl on the Extenders.

The same is true when I press "Refresh", I have to retrigger the devices to make them show up in SageTV.

Does that happen just the first time you set up the devices or each time you restart Sage?

[lamanmi]

PosterBoy,

Originally Posted by PosterBoy

Some caveats though:
I can only get it to work if my servers firewall is turned off. I tried a variety of settings including making sure HSPro has outbound access and allowing incoming connections on port 10990 (both UDP and TCP). Based on log info, it looked like HS was getting info from port 10990, but packets might not have been getting out. If you have any suggestions please do tell, and I will continue to dig into this as I have time. I am running server 2008.

It could not report my HSM100s temperature setting. It would only report ON or OFF

It could not report the current status of my schlage front door lock. The status was reported as unknown.

On the firewall, I haven't tried it with the firewall, but will certainly do that and come out with more formal information. In the mean time on the HomeSeer side, you should allow TCP port 10990 incoming and to be on the safe side TCP port 10991-10993 outgoing. Then on the Sage Server (if you have a firewall running) you should do the opposite -- 10990 outgoing and 10991-10993 incoming.

On the devices, I have found that each device type stores its configuration parameters and capabilities differently, so I need to begin building a support library. To help me do this, I have created a export utility, where you can export all of your device's configuration into a file and send it to me so that I can import it and build in the compatability. To do this, please go to each of the devices you listed, click on "InControl Device Information" link, enter a file path (which is on your HomeSeer server) and click Export. Then just post the file. I have a few already pending, but will certainly add it to the list and let you know when it is supported.

Thanks!

[Moskus]

Originally Posted by lamanmi

Moskus,
Does that happen just the first time you set up the devices or each time you restart Sage?

Each time I restart Sage or the extenders or hit refresh...

[lamanmi]

Moskos,

Originally Posted by Moskus

Each time I restart Sage or the extenders or hit refresh...

I have not been able to replicate this problem yet. Can you try the following:

- Check the Sage log to make sure it received the same number of messages as Homeseer sent....check around there for any errors. It is possible that one of your devices has a status or some other setting I have not properly handled.

- Try just enabling 1 device and see if it works for that.

- If you can drop me the logs again, that should be able to let me find the exact problem.

Thanks.....