Homeseer plugin developers gather!

Homeseer 3 changes for plugin developers

Awaiting HS3 goodies

The first Homeseer 3 gossip in 2012!

My first week with Vera

A first experience with my MiOS Vera V3 Z-Wave Home Control Box

 

Homeseer plugin developers gather!

April 13, 2012 in C#, Home Automation, HomeSeer

Rich “rjh” over at HomeSeer has posted a survey for plugin developers revealing some nifty (technical) information regarding the upcoming HomeSeer 3.

API functions removed from HS3
AddAction
AddCondtion
CAPIHandleStatus
ClearConditions
ClearLastX10
ControlThermostat
DeviceStatus
DialInternetConnection
DisconnectInternetConnection
ExecX10ByName
ExecX10NoLog
ExecX10 (CAPI interface should be used instead)
GetEventEnumerator
GetEvent (replaced with GetEventEx)
GetTVGTData
lastx10
NewCondition
NewEventAction
NewEventEx
NewEventGetRef
PrintOut
PrintOutRaw
RunningAsService
SetDeviceLastChange
SetDeviceStatus
SetDeviceStatusByName
X10InterfaceStatus
(more details on the survey page)

Device control / Device status functions removed?
All you need to do is add a device value pair that matches your old status (like ON=1, Off=0), and you have your old device status. Devices now use value pairs for all status and we have a new editor where you can edit the pairs as well as the graphics assigned to all values. It is a lot cleaner. If you worked with CAPI in HS2, this is the new API for device control and device status.

COM support
Support for COM is removed, so no COM based plugins will work (HS 1.7 plugins).

Linux support
Linux support is accomplished under MONO, so as long as your plugin is pure .NET, it should work under MONO on Linux. Make sure you install all of MONO, including the VisualBasic.Compatibility dll.

To check your plugin, just load into the MOMA application and it will tell you which functions are not supported. Getting MOMA to clear your plugin is a good first step to getting Linux compatible. (MOMA runs under Windows so Linux is not needed). You can ignore the late binding errors as they should not be a problem.

Scripts
Currently, VBScript still works in HS3 (Windows only) and I may leave it in for now, maybe only for a while and then remove it later. The scripting API will have changes though so many scripts will still need to be modified. Also, VBScript’s won’t work at all on Linux so the downside of leaving it there is confusion for the user. Any VB.NET scripts are supported on the Linux platform.

UI
ASP.NET is still supported (and supported on Linux). Old classic asp will not be supported since it will not work on Linux (it relied on the VBScript engine). We do have new API’s for building web pages that include a robust collection of screen elements that are Jquery based. This allows for dynamic HTML5 web pages.

Source thread
HS3 survey sticky thread
HS3 survey for plugin developers
HS3 development FAQ

Feel free to re-read some of the previous HS3 buzz.

Tags: , , , , ,
No Comments »

Awaiting HS3 goodies

March 23, 2012 in Home Automation, HomeSeer

Not much more information yet, but still nice to continue HS3 gossip in 2012 :-) . In case you are interested in previous episodes, here is where we left off.

2012, February
Any news on the new HS3 plug-in API?
We will be releasing a new plug-in API for HS3 in a few months. I don’t expect the changes to be sweeping. Anything your create now will likely be pretty easy to port.

2012, March
HS3 coming closer?
HS3 is still a few months away, but we are getting close.
Any specific hardware requirements for HS3?
Hardware requirements are the same as HS2. Note that we will have a Linux version and the hardware requirements on that are even less. I have it running quite well on our HomeTrollerSE unit with Ubuntu and LXDE. That unit is only 500mhz
Any plugin details available?
I don’t have a lot of plugin details yet as we are in the process of ironing them out. We will post a sample plugin with code so you can get started as soon as we can.
We will only be supporting the zip file method for plugins (at least on Linux). There will be a new option to create EXE plugins.
The API will remain the same except for the triggers/conditions/actions API which will be changing. If your plugin does not use those then you will only need to make minor changes. Some plugins may work with no changes at all.

2012, April
Beta version?
We are getting close to a beta, working on the plugin API right now as I want to get that out to developers.

Source

Tags: , ,
No Comments »

My first week with Vera

March 19, 2012 in Home Automation, Luup, Vera, Z-Wave

I finally decided to introduce Vera (V3) to my home. This is what I learned the first week.

  • Installing ntp client

    • Eventhough I’ve setup my location (city and timezone) correctly in the UI, it never showed the correct time. I tried reloading and restarting a few times, nothing seemed to work. I finally decided to do some (minor) “power-using” and logged on with ssh to install an ntp-client. Using putty I could easily log in with the root user (using password mentioned on the back of my Vera), and install an ntp client:


    Problem resolved :-)

  • Advanced network configuration

    • I’m using Vera as a wifi router in my local network and I needed some advanced configuration(s) done. I expected this to be available somewhere in UI5, but found nothing. Catching up on Vera forum threads, it looks like in UI4 there was a “Advanced configuration” link on the “Net & wifi” page. In UI5, that came with Vera V3 out of the box, this has been removed.
    Ignoring that pain and knowing that Vera basically just runs on top of an OpenWRT, you can just browse to openwrt web management console using http://your_vera_ip/cgi-bin/webif/info.sh (use your root user and password to login).

  • Adding z-wave device to Vera

    • Before moving my full z-wave network to Vera (I currently have HomeSeer as primary controller), I planned to introduce non critical devices first. I had a Everspring AN158 device lying around, destined to be my first test case. I expected it to be “plug and play”, but that wasn’t the case:
    My spare AN158 did not want to auto-configure correctly with Vera. On/Off however, did work correctly immediately after including, the power metering features of the AN158 did not. Within the Vera UI5, the device always ended up red with the warning “failed at: purging associations”. Resetting the AN158, including/excluding multiple times, desperately playing around with parameter values didn’t help. Logging on with ssh and snooping around in some log files, I saw many z-wave communication timeouts. Bringing my AN158 even closer to Vera (cm range) did not help :-) .

    I then decided to try to include another Everspring AN158 device, which I first needed to exclude from my Homeseer z-wave network. This second AN158 device automagically configured correctly immediately: all features of the device working. Trying a few more times with the first AN158, still no luck.

    Eventually, (more than) 48 hours later, it showed up green in Vera. Vera finally caught up with the device configuration and all features are now working as expected.

  • Fooling around with Vera’s apps functionality
    As a “power user” :-) , I wanted to setup some virtual devices. Using Apps/develop apps/create device, I added a motion sensor:

    DeviceType: urn:schemas-micasaverde-com:device:MotionSensor:1
    DeviceFile:D_MotionSensor1.xml

    The newly created device did not behave as a motion sensor (it did not have arm/bypass buttons) and it did not show up under “sensors”. Playing around with its configuration never fixed it. Eventually I ended up doing a luup reload…

    luup.call_action("urn:micasaverde-com:serviceId:HomeAutomationGateway1","Reload",{},0)

    … after which I finally had a proper (virtual) motion sensor. I’m not sure if this behaviour is the same for all device types.

Tags: , ,
1 Comment »

Let the z-wave micro module wars begin!

January 12, 2012 in Aeon Labs, News, Z-Wave

The word is out that the Aeon Labs Z-Wave Micro Modules have arrived. Do we dare say FINALLY :-) ?
Anyway, let the wars begin! Feel free to let your first (customer) experiences know below in the comments.

The Aeon Labs Micro Smart Energy products can report wattage energy usage or kWh energy usage to a Z-Wave gateway or controller when requested. If this function is supported by the gateway/controller, the energy consumption will be displayed in the user interface of the gateway/controller.

  • Micro Smart Energy Switch

    • The Aeon Labs Micro Smart Energy Switch is a low-cost Z-Wave appliance switch specifically used to enable Z-Wave command and control (on/off) for existing in-wall switches. It can also report immediate wattage consumption or kWh energy usage over a period of time.
    The wireless module is powered from the mains supply and is a three-wire design which requires a neutral connection. In the event of power failure, non-volatile memory retains all programmed information relating to the units operating status.

    Technical specs:
    USA: 110V 60Hz input, 1100W or 10A max output
    EU/AU: 230V 50Hz input, 2300W or 10A max output

  • Micro Smart Energy Illuminator

    • The Aeon Labs Micro Smart Energy Illuminator is a low-cost Z-Wave dimmer module specifically used to enable Z-Wave command and control (on/off/dim) for existing in-wall switches. It can also report immediate wattage consumption or kWh energy usage over a period of time.
    The wireless module is powered from the mains supply and is a three-wire design which requires a neutral connection. In the event of power failure, non-volatile memory retains all programmed information relating to the units operating status.

    Technical specs:
    USA: 110V 60Hz input, 275W or 2.5A max output
    EU/AU: 230V 50Hz input, 575W or 2.5A max output

  • Micro Smart Energy Motor Control

    • The Aeon Labs Micro Motor Controller is a low-cost Z-Wave motor controller specifically used to enable Z-Wave command and control (up/down) for existing window covering motors. The wireless module is powered from the mains supply and is a three-wire design which requires a neutral connection. In the event of power failure, non-volatile memory retains all programmed information relating to the units operating status.

    Technical specs:
    USA: 110V 60Hz input, 275W or 2.5A max output
    EU/AU: 230V 50Hz input, 575W or 2.5A max output

(Source: manuals found on the website of several web-shops)

1 Comment »

Interview with Fibaro : Past, present and future

January 5, 2012 in Fibaro, Home Automation, Home Entertainment, Interview, Z-Wave

Here is an interview with the people behind the Fibaro products. If there is anything else you’ve wanted to know, feel free to comment :-) . Enjoy!

Who are the people behind the Fibaro products and the Fibar Group? Can you give us a small introduction? How did they end up in home automation and in the z-wave world in general?
Behind the idea of Fibaro and its whole engineering stands Maciej Fiedler – a 35 year old passionate of ICT with over 18 years experience in this branch. He is the head of research and development department supported by a group of best qualified engineers. The history of Fibaro is quite trivial… it’s driven by necessity – the idea of developing the Fibaro System was inspired by a futile search for an intelligent house management system undertaken by already mentioned Maciej Fiedler. None of the offers available on the market met all his needs and requirements. Thus, the idea was born to develop our own system, which would allow control over and synergic operation of all the electrical devices in a facility and more….

Can you tell us a little about the Fibaro/Fibar Group background? Has the Fibar Group always been active in the world of Z-Wave? Was there any previous activity in the home automation world?
FIBAR GROUP was set up as a typical production company, shortly after main R&D works were completed. R&D works took over 2 years and they were conducted in DELTA Computers company owned by Maciej Fiedler, one of the FIBAR GROUP founders. Soon after prototypes were approved, decision regarding commercialization was made. FIBAR GROUP, as a production unit, was launched in November 2010 and its first franchise store was opened in April 2011. Currently, we have over 50 points of sale in Poland. Moreover we export to over 21 countries, mainly in Europe but we are also about to open showroom in Auckland, Hong Kong and Dubai.

Are the Fibaro products Z-Wave only?
Yes FIBARO, for the moment, is Z-Wave only. However, we are not closed for other solutions.

Can you explain the choice for Z-Wave?
We decided to implement Z-Wave to our products due to its potential. Z-wave has become widely known and applied in home automation worldwide. The alliance provides full technical support and is open for new solutions.

The last quarter of 2011, more or less out-of-the-blue, Fibar released its Fibaro Z-Wave micro modules. Did it take a long time to come up with their design?
Well, it might seem that we came out-of-the-blue, but we have spend over 2 years on R&D before commercialization decision appeared. Short after we decided on technology, we have started to built modules. The strategy for building our devices was developed in cooperation with many experts in the fields of electronics, electrical engineering, robotics and automation.

While we managed to develop the prototypes of our devices fast and without any failures, their size was a problem. Miniaturization of the actuator modules was the most time-consuming process. All the electronic elements were arranged on multilayer PCB plates with surgical precision. The tiniest deviation immediately resulted in interference and electronic noise, which caused device instability. To separate high voltage from low voltage we had to use additional filters, which took up more space. To ensure maximum safety, we installed an additional single fuse, which takes up little over 0.5 cm² of space.

After several months of work we have finally managed to bring our devices to perfection. Each Fibaro module is only 40mm long, 36mm wide and 15mm high. They can be fitted into any wall switch box. Currently, they are the world’s smallest devices of this type.

I believe you are the first in EU to release Z-Wave micro modules. Was it your goal to win the race for the first Z-Wave micro modules?
All we were thinking during product development was our clients’ needs. The technological solution – micro module – was just an outcome of our research.
As I mentioned before we were focused not to bring any modification in our customers’ house and due to that goal we’ve created the micro modules – the only devices that fit in switch boxes.

What were/are the challenges when manufacturing modules to use behind traditional switches? Any particular reason why only now the Z-Wave micro modules start showing up. Since Z-Wave is around (and mainstream) already for quite a while?
I believe nobody focused on basic clients needs… It is just a – thinking outside the box – approach.
Placing modules behind traditional switches gives to customers full functionality without interfering with interior design.
Regarding manufacturing, the production of micro modules is equally complicated as traditional devices.

How are the Fibaro micro modules different from its competition (eg. (soon) to be released Aeon Labs micro modules)?
Well, we have many unique features.

  • Dimmer:
    • Open configuration of lighting and dimming time in manual and automatic control
    • Possibility of defining maximum and minimum dimming
    • Feature of “stairs button”
    • Works with both mono and bistable buttons
    • Works with alarm frames

  • Relay Switch 1,5kW
    • Impulse control (possibility of controlling: blinds, garage doors etc. independently of buttons 1 and 2)
    • Possibility of separating association groups indepently of buttons 1and 2:
      • Associated devices may work via turning on or off the device
      • Associated devices may work
    • Works with both mono and bistable buttons
    • Configuration of all alarm frames
    • Possibility of choosing “the reaction” of relay 1 and 2 in case alarm frame appears:
      • No reaction
      • Device is on/ off
      • Cyclic change of state “flashing”
    • Possibility of defining the time of “flashing reaction”

  • Relay switch 3kW same features as 1,5kW but limited to 1 relay

  • Roller shutter:
    • Automatic calibration of blinds
    • Positioning of blinds
    • Works with both single, mono and bistable buttons
    • Works with alarm frames

Any specific reason for not putting any power metering feature in the Fibaro micro modules?
At the beginning our goal was to create micro modules with distinctive feature different from competitors. That’s why, among others, we decided to introduce possibility to assign associations to 2 buttons. Moreover our switch 1x3kW, as the only device, in the world has an additional feature: virtual switch. When you install the 1x3kW it appears as 3 devices (1 root, 2 switch, 3 virtual switch). You can use this virtual switch with your second button in a wall switch to control any other zwave device or run the scene. For example if you connect it to wall switch responsible for light control, the second button while connected to S2 can control e.g. blinds. It’s extremely good functionality for our customers.

But of course, such a common functionality as power metering feature will also be applied in our devices. We plan to introduce this in coming months.

The first youtube video of Fibaro showed up around April 2011. Have the modules been available locally in Poland since then?
Exactly, we have started sales in Poland in April 2011 while the first franchise store was opened.

Any plans for Fibaro devices outside EU?
In 2012 we want to launch sales in USA, Australia and New Zealand. These are very interesting markets with huge potential. In contrast to Poland, customers in those regions are familiar with smart home idea and they are looking for the best quality solutions at affordable price. Fibaro is very competitive regarding those demands.

What are the major challenges when building Z-Wave devices for different regions?
The major challenges when building devices lies mainly in software. We need to implement new chips and rebuilt our soft. No other changes in architecture are necessary.

About the Fibaro Home Center, the Fibaro Z-Wave gateway. What are the major differences with its competitors, eg. Vera… ? Does it run on similar hardware, and will it be priced accordingly? Is it already available in Poland currently?
Fibar Home Center 2 is already on the market. It’s premier was on 6th of December in our home city Poznan. It illuminated the lights on the City’s Christmas tree located in the heart of Poznan-old market square. It was part of city’s strategic campaign “Poznan city of know-how”. Officially you can purchase HC2 in Poland since 18th of December.

The major differences of HC2 with competitors are:

  • Extremely efficient hardware architecture = fastest device of the type in the world
  • Ultra low energy consumption
  • Remote access via web page or mobile phone
  • Simple, user friendly interface
  • Fast and simple configuration
  • Geo localization – tracking Your family members
  • SMS notification
  • Manageable users’ rights
  • Various devices’ associations
  • Conditioning scenes depending on weather or other, user-defined variables
  • Advanced recovery system
  • System backup is always saved on attached pendrive, hidden in the casing
  • History of events

Additionally the HC2 casing is 100% aluminum. The design of both the product and the package is very modern and elegant.

Regarding Fibaro multimedia, your website does mention some nifty things. Will it have an IR blaster included? Any (technical) details you can reveal already?
For the moment it’s in our R&D and in can not reveal more than the website :-) . But I can assure you, it will sweep out the competitors…

Anything else we can expect to see from the Fibar Group in 2012 (and beyond)?
Our website reveals also that we work on FIBARO SHOPPING and SERVICES.

  • Application “Services” will give you access to a variety of everyday services such as restaurants, movie theaters, theaters, taxis or plumbers. With Fibaro you can access a large database of service providers, which allows you to immediately respond to any failure in the house.
  • Application “Shopping” will give you more time to do whatever you want. Instead of standing in lines and browsing through shelves, you can enter internet stores and do your shopping right away.

Apart from new applications, we are about to introduce 2 new products to the market – but more about soon…

Head over to the Fibaro website to snack on more screens and pictures.
Might also be worth a read: Invasion of the z-wave micro modules and Fibaro review highlights

Tags: , , ,
1 Comment »

Continuing the HS3 gossip…

December 3, 2011 in Home Automation, HomeSeer

Last month, Rich “rjh” over at HomeSeer has revealed some nifty information regarding the upcoming HomeSeer 3.

In case anyone wants to re-read, here is the previous HS3 gossip & chatter.

Let’s not talk release date :-) , let’s talk beta version…
As for a ship date, whatever I post will be wrong, so I won’t post one I will say we hope to have a beta around the end of the year, or Jan time frame. But do not hold me to that!

Let’s talk changes…
* We have totally re-written the event engine, which has proven to be a big job. This includes a totally new interface (web page) for creating events. It is much easier to use and more robust then before. New additions include counters and timers as well as better grouping of events.
* The status page is totally new (the old one is still there but is now considered a utility page for device maintenance) The new page auto updates device status, allows for floor plan views, and an edit mode for editing the view on the web page.
* We are using jquery for the web pages, and if you are familiar with this, you know how powerful it is. The web pages look and act more like an application than a web page, with dialogs and dynamic updates. Plugins will have access to jquery but they don’t need to know how it works or write any javascript.
* The “button bar” has been replaced with a jquery menu to allow for better navigation of the web interface.

Let’s talk linux…
One big change is Linux compatibility. The entire application runs under Windows or Linux so you can choose the OS and hardware you want to run it on.

Let’s talk plugin-compatibility
Since there are changes to the plugin API, we hope to have a test version for plugin authors asap, so they can make any necessary changes. We have major changes we want to make the plugin API, but we are holding them offer for a later release. The first release will have a plugin API similar to HS2 so that most plugins will work with either little or no modifications. Almost every plugin will need some modification if they want to be compatible with the Linux version.

Source

Tags: ,
2 Comments »

MiCasaVerde Vera3 available in December

November 24, 2011 in Home Automation, News, Vera, Z-Wave

It looks like the Vera3 (quitely) sneaked in the available stock on MiCasaVerde. The specifications are the same as previously mentioned on the wiki:

  • CPU 500M Hz MIPS SoC
  • Flash NAND 32 MB
  • SDRAM 32 MB DDR2
  • Memory DDR2 128 MB
  • 2xUSB Port
  • 1xWAN Port (10/100 Mbit/sec)
  • 4xLAN Port 4 (10/100 Mbit/sect)
  • Z-Wave Built-in with internal antenna
  • Dimensions (HxWxD) 177mm x 130mm x 34mm

Now we’re still waiting for the at CEDIA showed VeraLite, having a built-in battery compartment for making inclusion of Z-Wave devices into the network easier, and its lack of Wi-Fi. Hopefully in time to make it under the christmas tree.

2011-11-25, update:
It looks like Vera3 will be available somewhere in December, “EU Vera3 Dealer pre-orders will ship December 12th and customer pre-orders December 15th.”

About Mi Casa Verde
Founded in 2008, Mi Casa Verde's mission is to provide home and small business control
and entertainment solutions that are easier to setup and use than any other product on the
market, and that are extremely energy-efficient, eco-friendly and affordable.

Mi Casa Verde's Z-Wave home and small business controller and bridge, called Vera,
is a simple and flexible solution. It is designed to help save energy, increase home and
small business security and enhance the home theater experience. Vera can be managed
from anywhere in the world using an iPhone, iPad, Android phone, PC and other mobile devices.

Mi Casa Verde's Z-Wave home controller is built on the MiOS platform.

Tags: , , , ,
3 Comments »

Groovy scripting in HomeSeer (part 2)

November 2, 2011 in Groovy, Home Automation, HomeSeer, Java

In part 1 we just used groovy standalone to connect to HomeSeer, now we take a step up to improve performance :-) .

I finally found time to write about the HomeSeer Groovy Script Server and the HSGroovyScript HomeSeer Plugin. I took me a while before I got all the HomeSeer API functions working from within Groovy, reason: DLL hell and x64/x86 COM component compatibility problems :-) .

Basically we have a (standalone) Groovy Server running waiting for commands/scripts to run. This server can run on any (windows) machine, and connects remotely to the HomeSeer host using the HS speakerclient active-x components. A plugin for HomeSeer then does the necessary work to start a groovy script on the applicable machine. Unfortunately I couldn’t find a way to initiate the script other then by an event. I tried fiddling with the scripting possibilities within HomeSeer itself, but failed to get a .groovy in there. If you guys have another idea, feel free to let me know.

When initializing, the server connects to the HomeSeer host, and prepares the “homeseer2.application” COM component and its Scheduler.hsapplication reference. These 2 objects are injected in each script/command executed as variables ‘hsi’ and ‘hs’.
This means that the scripts don’t have to initiate the connection to HomeSeer every time.

Example:

hs.writeLog("MyGroovyScript", "This is written remotely powered by a www.iHomeAutomate.eu HomeSeer Groovy script!")

def version = hs.version()
def uptime = hs.systemUpTime()
hs.speak "Your HomeSeer machine is running version ${version} and is already up for ${uptime}."

Result looks like this:

Or we could do some more complicated stuff:

def deviceEnumerator = hs.getDeviceEnumerator()

while (!deviceEnumerator.finished()) {
    def device = deviceEnumerator.getNext()
    def type = device.dev_type_string
    def deviceCode = device.hc + device.dc

    if (type.toLowerCase().contains("battery")
            && hs.deviceValue(deviceCode) < 75) {
                hs.writeLog "Battery low detected for device ${device.name}"
    }
}

On HomeSeer side, the scripts are fired by events:

The result looks like:

If people would be interested in this homeseer plugin, feel free to comment below. Of course opinions and other comments are welcome too :-) .

Tags: , , ,
3 Comments »

Duwi z-wave window blind Insert

October 22, 2011 in Home Automation, HomeSeer, Vera, Z-Wave

A short summary of some of the notes I had available for those who want to figure out how to customize the Duwi sun blind control.

  • Customizing the operating times (using the blind control) (source: Duwi manual)

    Please note a shutter/window blind does not necessarily have identical operating times in the UP and DOWN directions. The window blind control has to be adjusted to this, so that a desired, preset value (e.g. window blind to 80%) is attained both in the upward as well as downward motion.
    Also note that you (possibly) have to remove the mounted rocker of the window blind for this programming step.
    The window blind must first be driven along the upward direction up to the end stop. The reduction of the operating time must be started from the upper maximum position, if not the programmed values would be falsified.

    1. Move the window blind along the upward direction up to the end stop
    2. Simultaneously press the “UP” and “DOWN” buttons of the window blind for 2 seconds, the LED blinks green.
    3. Move the window blind with the “UP” or “DOWN” buttons of the window blind in the intended direction. During this measurement time, the LED promptly blinks green.
    4. Release control in the target position. The window blind stops, the LED confirms the successful folding with a 3 second green light and a failed folding with a red light.

  • Customizing the operating times (using parameter 0 with third party software – !only for experienced users!) (source: Duwi manual)

    Note that the adjustment of the operating times should be undertaken only by well-versed technicians.

    Send parameter 0 to the blind control root device node with 2 bytes HEX value(s) (one UP, one DOWN):
    0×00 = no interruption/permanent operation
    0×01-0x7F = 1 second to 127 seconds in 1-second steps
    0×80-0xFE = 130 seconds (0×80) to 1390 seconds (0xFE) in 10 second-steps
    0xFF = factory settings 120 seconds

    Examples:
    Parameter 0, value 0xFFFF should reset it to factory settings (120 seconds for both UP and DOWN).
    Parameter 0, value 0×7878 sets it to 120 seconds (for both UP and DOWN)

    I don’t have any Vera available to verify, but it should be the similar to HomeSeer, maybe even easier. With HomeSeer parameter 0 should be sent as a decimal value, for example for 0×7878 send decimal value 30840 (120 seconds for both UP and DOWN)
    It’s been a while since I verified this, but if my earlier notes are correct, this is how I parametrized the operating times of my blinds. So definately handle with care! The prefered way of customizing the operating times is still using the control itself :-) .

  • Adjusting the stop functionality (using the blind control) (source: Duwi manual)

    Apparently you can also program the shutter actuator in a way that, in case of a press in the opposite direction, the shutter won‘t stop, but continues immediately in the opposite direction. I haven’t verified myself, but the manual states the following:

    Hold the “UP” and “DOWN” button of the shutter actuator simulaneously for 5 seconds. Please note, the device should not be included in any network (yet)!

  • Adjusting the stop functionality (using parameter 1 with third party software – !only for experienced users!) (source: Duwi manual)

    The manual states the following:
    Send configuration command parameter 1 to the root node with the value “0” in order to disable the stop-functionality.
    Send configuration command parameter 1 to the root node with the value “1” in order to enable the stop-functionality.

    I have verified this with HomeSeer and it seems to work. Again, handle with care!

Source: different manuals in different languages :-)

Tags: , , , , ,
No Comments »

HomeSeer 3 gossips and appetizers

October 11, 2011 in Home Automation, HomeSeer

I’ve compiled a list of statements and other chatter regarding HomeSeer 3 (in chronological order). For the latest gossip, scroll down :) .

2009, December
>>How far away is HS3?
Light years away until we sit down and make the decisions on what goes in there and start figuring how long it will take.
Source

2010, September
The fact of the matter is that Z-Wave is handled by several class objects that do not even get initialized if Z-Wave is not used, so there is no significant additional memory used by having Z-Wave in the code.
However, because of a decision that we have made with regard to HS3, it is very likely that Z-Wave will be moved into a plug-in or a separate executable module of some type. So while it will never happen in HS2, and would not have happened in HS3 had we not made this other change, we probably now will.
Source

2011, July
Our software is incredibly complex because of the many interdependencies between it and the technologies it integrates with. We did the best that we could internally and via beta to test HS2 but the reality is that we couldn’t possibly test for all the variables you guys throw at it! So yes… HS2 definitely had some bugs that needed squashing. The good news with HS3 is that most of the changes will be focused on the GUI, on making the program easier to use and better organized (for devices and events). It does not represent a complete rewrite, as HS2 did.
Source

2011, August
08/26/2011 10:53 AM I’m impatient. Hmmm! Anybody know when (and if) we are allowed to beta test HS3?
08/26/2011 7:50 PM @Moskus: We’re several months away from a beta. Hang in there
Source

2011, October
The event engine is being completely re-engineered. A new status view is being implemented. JQuery is being introduced into the web GUI.
Source

2011, October
The bulk of Bugzilla issues will be addressed in HS3 once that program is in alpha/beta testing phase.
Source

2011, October
Web services will be in HS3, so you will be able to connect remotely easily with any app that supports sockets. We will be using this new interface for the speaker client on the Linux version.
Once we get an HS3 build working and the screens solidified, I will start a new HS3 thread and start discussing the new features, screen shots, etc. I hesitate to give any dates, but we are getting things together very quickly now, won’t be long.
Source

Tags: , ,
1 Comment »

← Previous Entries