Plugwise Homeseer Plugin

Post by **TANE** » Sun Feb 08, 2009 11:11 pm

Thanks,
I have also send some messages to other HS developers.

Post by **Rene** » Sun Feb 08, 2009 11:13 pm

In general I am not getting very enthousiastic of the support with regards to development from the HS forum.

Rene.

Post by **Rene** » Mon Feb 09, 2009 12:11 am

In Homeseer there are 3 type of devices, X10, IO and IR. X10 must be used for X10 devices, IR for infrared devices and IO for all other devices like RFXCom sensors or Plugwise devices. This is all according to the SDK documentation. So if HSTouch only provides a toggle option for X10 devices, this is a clearly shortcoming of HSTouch.

Rene.

Post by **RdP** » Mon Feb 09, 2009 12:16 am

I'm not blaming anyone or anything. I'm jut trying to find out why this is(or wll not be) not working....
IO devices can have multiple values, Like "arm away", "arm stay" and "disarm" (or maybe even more), so a toggle option is not appropriate is such cases....

To find a solution we clearly need to explain and give a much as information as possible....

Post by **Rene** » Mon Feb 09, 2009 12:24 am

Rien, I think uou hit the nail on its head (or what is the English expression). To be precize an IO device can have only one value but several states, while the states of an X10 appliance are limited to on and off (while this is not exactly true for a lamp device which can be on, off or dimmed). However, a toggle option could still be valid for an IO device when this device only has 2 states, like the plugwise devices, or when you can specify between which states should be toggled.

Rene.

Post by **RdP** » Mon Feb 09, 2009 1:04 am

<blockquote id="quote">quote:<hr height="1" noshade id="quote">Originally posted by rklootwijk
 I will take a note of all feature requests but do not promise anything. I do not think I will implement this feature. What do you want to do with this feature or is it just to have an overview?

Rene.
<hr height="1" noshade id="quote"></blockquote id="quote">

Rene, I just want to know if a device is on or running for overview reasons. (HStouch for example) I know I can do this by checking the Plugwise usage, but it's more nice to have a status (including icons)
It's even more nice if I could device ranges of power usage, so maybe I can tell in what stage my dryer is.....

Post by **VanDavid** » Tue Feb 10, 2009 1:20 pm

Hi people!

We're exchange students from Barcelona. We're doing our final project here in The Netherlands (Groningen).

We bought the plugwise home basic to make some experiments. We'd like to take samples avery 10sec or something like this.
The problem is that we're not familiarized with .XML and .MDB.

We tried to acces to the http://localhost:8080/ but we can't go there. Anyone knows why? Something about firewalls?

We're really interested in all that stuff and this is the perfect place for us! Thanks for writting in english

Post by **RdP** » Mon Feb 23, 2009 11:09 pm

Hi,

I scanned quickly to this posts, to see i this has been reported earlier, but it isn't...
I have several HS log entries like this:
23-2-2009 21:56:38 - Warning - Plug-in Plugwise not responding, #32 callbacks cancelled
23-2-2009 21:56:38 - Warning - Plug-in Plugwise not responding, #32 callbacks cancelled
23-2-2009 21:56:38 - Warning - Plug-in Plugwise not responding, #32 callbacks cancelled
23-2-2009 21:56:31 - Warning - Plug-in Plugwise not responding, #32 callbacks cancelled
23-2-2009 21:56:28 - Warning - Plug-in Plugwise not responding, #32 callbacks cancelled
23-2-2009 21:56:28 - Warning - Plug-in Plugwise not responding, #32 callbacks cancelled

This happens when I am configuring/creating HS devices in general. I know it's a warning. But what does it mean and can it harm the plugin stability ?

Thx...

Post by **Rene** » Mon Feb 23, 2009 11:28 pm

Rien,

I've seen it to but did not have time to look into it. I will do shortly and get back with an answer.

Rene.

Post by **TANE** » Mon Feb 23, 2009 11:28 pm

I have also scanned the log files and found few.
All the warnings are when new devices are created or when something is saved to Db...like events

Post by **RdP** » Mon Feb 23, 2009 11:35 pm

Okay, take your time....

For the device status of the plugwise devices in HStouch I created dummy HS devices and connected them using BLmapper. Some extra work but now I can see the real status on the touchscreen...
The only problem will be as I have to upgrade the plug-in and the devices must be recreated(then I have to do it all over again....)
But for now I'm quiet happy with the functionality....

Post by **Rene** » Mon Feb 23, 2009 11:47 pm

I still do not understand why you cannot use the devicestatus in HSTouch to determine the status of a device. What exactly do you do with the dummy devices?

Rene.

Post by **RdP** » Mon Feb 23, 2009 11:55 pm

I create the dummy device as a applicance module (0=off, 100=on) The plugwise device is mapped to this. If the plugwise device changes state it will also changed the state of the dummy.

Post by **Rene** » Tue Feb 24, 2009 12:11 am

As I mentioned before the devicevalue should not be used to determine the status of a device. This is definitely a bug or a design error in HSTouch.

Rene.

Post by **Rene** » Tue Feb 24, 2009 12:35 am

I found and fixed the problem causing the "Plug-in Plugwise not responding, #32 callbacks cancelled" warning. Because it is not a critical error I wait releasing a new version of the plugin so I can include more bug fixes.

Rene.