HS3 – a peek around the corner

A peek around the corner of HS3 (beta) release status

Are we there yet?

Quick post before end-of-year activities . Here’s what’s new in the HS3 universe: 2012,

Bring on the Fall!

Get back to school, get back to work… summertime is over! Here’s a short HS3 rumour roun

 

HS3 – a peek around the corner

May 3, 2013 in Home Automation, HomeSeer

2013, February 4 – About Z-Wave
- we have completely rewritten much of Z-Wave in HS3
Source

2013, February 21 – About SSL support
… will SSL be supported in HS3? Yes this is planned.
Source

2013, February 26 – About the Z-Wave rework
… In HS3, since our Z-Wave support is being vastly reworked, we have the opportunity to enhance this feature. For one thing, devices found on the Z-Wave Alliance certification list may be able to be identified by the software so that you, the consumer, will know whether you are using a device that has passed the Z-Wave Alliance’s tests of interoperability. What we will also be able to do is to identify a device by its product name, so that not only does it make sense looking at it in your own system, but it will also be able to be identified more easily as working with the current version of the Z-Wave plug-in for HS3 before you make a purchase.
….

Source

2013, March 10 – Status update
We are in final stages of in-house testing, no beta this week, but any time now. As soon we work out reported issues we will move to posting a beta.
Source

2013, March 15 – Another status update
In the middle of HS3 at the moment, trying to get a beta out.
Source

2013, April 8 – About new features
It is almost easier to say what has not changed. Scripting support is still there, but probably most scripts will have to be touched in some way to update them to work with HS3 properly. For example, the device address is no longer the primary way of accessing a device – you can have a device without an address in fact, and you can have a device with an address that includes something specific about the device followed by the old code format if you want. For example, if your Z-Wave network is AABBCCDD, then you will have devices with a full address of AABBCCDD-10-Q05, which is a node 10 child device of network AABBCCDD. The code-only part of the address is Q05, which many people are familiar with. Accessing a device by name is unchanged.
Plug-ins can now run on remote systems and you can run multiple instances of a plug-in. A big part of the delay has been due in part to us removing Z-Wave from the core program and making it a standalone plug-in, and the new features that are being put into that.
It is our hope that testing of that plug-in will resolve some of the last of the more serious issues so that we can begin a public beta period soon.
I wish I could spend all day telling you about it, as there are many things I left out, but please understand that we are working as hard as we can to bring this to you as soon as possible.

Source

2013, April 26 – About Perl scripting
Perl will work on Windows, but not on Linux right now. I realize Linux supports perl but we are using a Windows scripting host to run the process. You can launch a perl script from HS but I am not sure how it can access the scripting API.
The problem is that the scripting in windows is hosted using Windows Scritping Host, and this exposes our API to the script engine. This is not available on Linux, but I will research and see if there is a way to interface to Perl or Python from our application.

Source

2013, May 2 – A HS3 teaser
A taste of things to come. Hang in there… won’t be too long before we can roll out the details for the first beta.


HS3 Teaser (events)

[Pictures & quotes coming from board.homeseer.com]

Are we there yet?

December 21, 2012 in HomeSeer

Quick post before end-of-year activities :-) . Here’s what’s new in the HS3 universe:

2012, November 16
Email sent to inform the HS3 developer’s release is just about ready for distribution. Developer beta versions will only be provided to developers who sign and return the software beta NDA
HS3 Developer NDA

2012, December 14
First we need to get the initial version of HS3 released and that is in the hands of developers now. Should have a beta out in Jan
Source

2012, December 20
We are planning on a Beta release by the end of Jan. From there we will release once all reported issues are resolved. Plugin authors are currently updating plugins with a developer release.
Source

Happy holidays!

Bring on the Fall!

August 31, 2012 in Home Automation, HomeSeer

Get back to school, get back to work… summertime is over! Here’s a short HS3 rumour round-up.
While lots of plugin developers (among others) are working/questioning/gathering intel regarding HS3 versions of (their) plugins, here’s what we do know:

2012, July 19
We are getting close to getting out the SDK for 3rd party plugin developers, that is the next milestone.
Source

2012, August 7
We are finalizing the SDK for our plugin developers and should have that out shortly. We are targeting this fall for a beta release.
Source

*yawn*

Buzz: Nexus Q going home automation?

July 15, 2012 in Android, Google, Home Automation, Home Entertainment, Z-Wave, ZigBee

Stating facts:



Connecting the dots:

    Buzz on the streets is that the announced Nexus Q might be ZigBee enabled. Good for us home-automation geeks! Too bad one of the dots did not leave a trace to Sigma Designs, making it it magically z-wave compatible. Would that be too much?

Dream on :-) ?

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.

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

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.

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)

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

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