Update HC2 4.019 BETA

[I. Szymanski 0]

Fibaro Home Center 2 v 4.019 BETA.

Beta version is designed for user testing and soon will be released as official.

WARNING! After installing this upgrade backups from version 1.x and 3.x will be retained but hidden because they are incompatible with the version 4.x. In case of update from old version, v1.x, after that update all users will be deleted. Admin password will be reset. Also update to Beta software all devices will be automatically reconfigured to work with new system architecture. Reconfiguration progress will be shown in pop-up window.

This update can last longer than previous. If this update lasts longer than 30 minutes, please go to main HC2 address (e.g. 192.168.0.1).

If "System temporarily unavailable" text will appear during update, please wait - you will be redirected to the main page when all services start.

4.019:

New Functionalities:

- Configuration > Backup now is Backup & Recovery

- Recovery Memory Status - can be checked on Backup & Recovery

- Backups - information about compatibility with current HC version

Resolved Issues:

#0001359: For some reason 1 smoke sensor doesnt show black box info.

#0001524: 3.902 Alpha - HUE plugin won't create new user

#0002037: Cannot delete device, but after a restart the devices shows as being deleted

#0002048: JSON ENCODE / DECODE doesn't work properly

#0001920: [ERROR] 09:23:47: line 44: attempt to index global 'json' (a nil value)

#0001699: panel energii

#0001849: Fibaro Door and Window Sensors do not report

#0001852: Unable to delete devices

#0001861: Since upgrading no scenes work

#0001877: HC2 stops working on 4.017

#0001709: When adding Foscam generic camera to plugin the password field is misspelled "Passwrod" should be "Password"

#0001824: Aeon Switch with energy meter. No more energy measurement/logging after upgrade to 4.017 beta.

#0001935: Notification of the battery status

#0001963: Event panel refreshed while browsing

#0001869: Fast scrolling in event history

#0001894: Log messages do not span columns

#0001655: Changing pages results in spinning wheel

#0001815: Power calcutaion is only working in rooms with Fibaro Wall plugs

#0001790: Virtual Device icon change causes a crash

#0001834: Get error 502 and 503 after virtual device import

#0001701: Controlled device is set to Air Conditioner on dimmers

#0001962: UI crashed after creation of magic scene

#0001966: setting " How frequently GPS position from the user?s iPhone should be collected" is not saved after reboot hc2

#0001888: Execution of lua commands

#0001907: Danalock POL_ZES100 (Z-Wave Danalock Square) sowing but not functional

#0001596: universal sensor has not the normal picture and dallas 18b20 temp does not work

#0001652: uni bin sensor breach scene does not work

#0001548: Nie działa triger włączenia włącznika Duwi

#0001812: HC2 doesn't respond anymore

#0001593: Email address validation wont allow + to be used

#0001651: HTML special characters being displayed in Virtual Device code

#0001946: fibaro:getSelfId does not work

#0001889: Unable to debug slider code

#0001992: FGK-101 with a DS18B2

#0002005: After creation of a magic scene i'm unable to login to the fibaro home center (keeps loading)

#0002023: Disarm sensors with scene

Known Issues

- Breached sensoer with Arm Delay causes instant alarm after being armed

- Data range selection in event panel doesn't work properly

- For devices imported via Gateway Connection may have no icons

4.018:

Resolved Issues:

#0001566 All versions of FIBARO cannot support the switch state to return to the "Multilevel Switch Command Class, version 2"

#0001576 Untranslated text in Satel input/zone page

#0001578 Cannot change label value

#0001618 HSP02 no longer has parameters

#0001624 no different color for slave devices

#0001630 Reconfiguration did not run on a dimmer, resulting in no "sceneactivation"

#0001631 Roller Shutter 2 scene won't close

#0001711 Danfoss LC13 and older model are dead or E5 on the Danfoss itself

#0001773 Danfoss LC13 no Icon displayed

#0001747 Weather display wrong place

#0001834 Get error 502 and 503 after virtual device import

#0001836 Lili

#0001853 After upgrade web interface is slow when changing views

#0001873 No push messages possible on iPad/iPhone with 4.017

#0001880 Not able to set Variable manually anymore

many other fixes

Known Issues:

- Important! User Developed Plugins will be removed with this update. Please be sure you have your plugin source code.

- Important! Remote access is NOT available for this version.

- Gateway Connection - status of dead device between master and slave controller may be different

- Devices not properly configured on 3.X may not be converted properly

- Reconfiguration may not work properly in some cases

- On mobile clients devices may be visible in different categories than configured

- Advanced settings for some imported devices may not work properly

- Plugin for Sony TV will not work with newest Sony Firmware

- Event Panel- some issues with scrolling

- LUA functions fibaro:log("") i fibaro:call(id, "setproperty", "") may have some issues

- Horstmann Switch HRT4-ASR-ZW is not fully supported

- Horstmann Thermostat HRT4-ZW- higher battery usage and incorrect reports in some cases

- Doorlocks- some functions may not work properly

- Thermostats Setpoint- are not fully supported

4.017:

New functionalities:

User's Plugin Installation - ability to build and install Home Center plugin

FGHC Rest API Active Documentation - documentation and ability to test REST API requests, access at HOME_CENTER_IP/docs

Added support for American English (EN-US)

Plugins:

Nest - plugin for well-known thermostat

Netatmo - plugin for thermostat and weather station from netatmo

3.907:

This version mainly concentrate on adding better support and integration for more devices (not only z-wave device).

Important part of software responsible for management z-wave devices was rebuild from the scratch for better support different devices types.

New Home Center software introduces support for plugins. Plugins give support for new devices and new functionalities without modifying HC Firmware. Plugins can be used for controlling devices via different protocols and standards like TCP/IP, IR*, RS 232*, UPNP. Plugins have their own user interface and can call all APIs available on HC2. Possibility of building plugins by independent developers will be introduced in next versions.

* required additional hardware.

New functionalities

--------------------------

Drag & Drop for devices and scenes - available on home, devices and rooms screens. Assigning devices to rooms and changing its order is now much easier and faster.

Magic Scenes - new, simplified and easy to use graphical way to create scenes based on condition > action flow.

Temperature Panel - allows to see history of temperature changes in rooms and on each device.

Diagnostic Panel - general information about HC working condition like CPU & RAM usage, free space on hard drive. Will be extended in future versions.

New Z-Wave engine - redesigned and rewritten from the scratch. Now is faster and has better support for devices.

Z-Wave Door Locks support - controlling and PIN settings.

Thermostats - extended controlling for thermostats from manufacturers like: Honeywell, Trane Corporation.

Extended tamper for sensors - exclusive information for motion detection and violation of sensors.

Fibaro Smoke Sensor extended support - level of smoke and gap to alarm level is reported and visible on charts at iPad and Web Page. Sensitivity level is now easier to set.

Fibro Motion Sensor new device - when seismometer mode is turned on new device reporting tremors is available. Charts for temperature and illuminance. Additionally information about sensor violation.

Device hiding - device that is not in use can be hide without removing it.

Device deactivation - deactivated device is visible in UI but can't be controlled.

Multithreading added for HC (server and z-wave) - now engines work much faster.

Event panel moved - for better usability now is available in menu on right side of screen.

User rights management - moved to Configuration.

Block Scenes improvements - for device only available actions are visible, scene activation block added and logical conditions grouping using brackets.

Lua Scenes - updated tooltips for devices.

Plugins:

Plugins are grouped in categories: Safety, Cameras, Climate, Multimedia, Others

Plugins search

Network devices search via ARP

Plugins category Safety:

DSC Alarm - for DSC Alarms,

Helios Basic - integration using Basic license,

Helios Gold - integration using Gold license

Mobotix - for Mobotix videophone,

Satel Alarm - for SATEL

Plugins category Cameras

more than 100 devices from various manufacturers

Plugin category Climate

Carrier Furance

WS Davis Vantage

Plugins category Multimedia

LG Bluray

LG TV

NC + mediabox

XBMC Remote Control

Denon Amplifier

LG Bluray

Onkyo Amplifier

Philips Bluray

Pioneer Amplifier

Samsung TV

Sonos

Sony Bluray

Sony TV

Plugins category Other

Philips Hue

Wake on LAN

Other changes

Many other improvements to the system

Users who use version alpha from 3.901 to 3.906 need to perform recovery first and update from 3.590 after restoring backup.

[Guest minimax]

So far so good.

Well done, fibaro. At least all devices were preserved.

[fergalmccarthy 5]

I cannot understand how fixing the thermostats is not top priority.

@fibaro are there any priorities ?

[Guest gembrain]

As has been said by Yuzo earlier The update progress bar does not work. i was upgrading from 3.590 and it just stayed at 0%.

However, I could see something was happening from the traffic analysis on my router.

Opened another IE window and logged in again to find HC2 all upgraded and running.....

No dead node problems but I've only got 4 and they're all powered. They were all OK under 3.590.

[SirMaggot 12]

It's really sad to see that we have come so far that we actually regard "going dead sometimes" as a good thing. With any other solution it would be completely unacceptable.

Has Fibaro even admitted that there is a problem with dead devices yet? Or is it still our own fault? The youtube movie that was posted the other day (

) showing a "dead" motion sensor that reacts to motion, is still not enough proof that something is wrong?

As long as Fibaro continues to ignore this I don't see that we're going to get any improvement any time soon.

My dead device is 25 meters away in a mailbox, so im pretty happy that it works, even if its dead sometimes, it still works.

I had to check my battery devices as i write this, and they are all dead now...

[sj3fk3 27]

Are we at the point yet where Fibaro should be sending out test units to people that are beta testing their software ? The whole, don't use this in a production environment pisses me right off. Do they think people will fork out for a separate HC2 to help them out. Of course its the production environment, its over 500 euros worth of controller , not to mention the modules.

+1

[biggles 0]

Well, after a night of contemplation my HC2 is back online. Hurray. The problem is that now all Danfoss thermostats are dead again. I guess we wont see an update until February now and our house will be very cold bu then...

[sj3fk3 27]

Z-Wave.me wall controller scene activation still not fixed?

And also dead-nodes again (even though I have set Do not mark nodes as dead: set to YES)

But thanks for fancy temperature graphs that I am never going to use.

Please stop adding new features and start fixing *all* bugs that are listen in bugzila.

[D-Vine 65]

would like to test beta version again but with all the message of dead nodes, it scares me away.

how's are scenes working in this version ? (smart lights / LUA scheduler / Auto light in Bathroom )

and virtual devises ?

[robmac 173]

First impression is that it is working a little better in some areas than 4.017/018.

Web app has locked up a couple of times. First time just after install, the other was overnight. I was beginning to suspect it is the web app that had issues on 4.017 (either api or portal) and has the memory leak. Will have to test again on this version.

I like the checksum feature for a rather perverse reason. I might now know when my HC2 usb is corrupt before I try to recover. I still won't be able to replace without returning the unit if it is a media surface fault. If it fails you will still be a very sad (and probably with reason) bad forum user and ex HC2 user. Mine is cool just now so not corruption causing any of my issues,

Initial checks still indicate that battery devices are very badly handled.

Very poor handling compared to the same devices tested on very cheap controller. Yes I have taken the same device off HC2 and included it on a very cheap controller in the same location as HC2. It works spot on. Put it back on HC2 and it is random. It sometimes works and sometimes fails.

I have tried with many device types so this is generic poor handling of battery devices and my initial check is no improvement. Battery devices have never been well handled on HC2. Please, please, please totally rewrite how you handle battery device.

For many years I have given this feedback please listen and accept HC2 has an issue that needs fixing.

I state again the logic that has been used with battery devices must be wrong as other controllers work better with the exact same devices.

This is not a criticism just open and honest feedback. Please keep up the hard work as I look forward to a better HC2 soon.

[Guest AxelS]

Wrap Up from my side with 4.019

- Update go through the process, after restart no Z-Wave communication there at all; recovered and second try: Z-Wave communication is back after about 30 minutes

Please login or register to see this image.

/emoticons/default_icon_evil.gif" alt=":evil:" />

- all fibaro 2x1,5kw switches doesn´t work anymore. They are there and useable via the web interface but all the connected switches does´t work. The unit does´t recognize if the switch is turned on or off. After exclude and reinclude it seems that they are working again

Please login or register to see this image.

/emoticons/default_icon_curve.gif" alt=":-/" />

- the whole HC2 unit isn´t very stable with this version - Z-wave learning mode only work once, then the window stays open and you have to make a "hard-restart" by switching of the power. Second thing is, that my HC2 shows about 5 times in the last two days the 503 error. For me the whole web interface is worse that in 4.018

- still dead nodes in this version - as robmac already mentioned: HC2 and bettery driven devices = B..LLS....T

- All Merten Roller devices shows the blind closed when it´s open and vise versa

My opinion overall is that 4.019 is worse that 4.018

br

Axel

[petergebruers 1,268]

would like to test beta version again but with all the message of dead nodes, it scares me away.

how's are scenes working in this version ? (smart lights / LUA scheduler / Auto light in Bathroom )

and virtual devises ?

I think you should check

Please login or register to see this link.

- but I can summarize it for you: there are still many other bugs, I mean other than the ones you mention. But let me say this: I have several lua scripts that trigger from a Aeon 4 in 1 or a Fibaro Door sensor. And they don't fail - a lot. Like... the last 24 hours I haven't see a light come on maybe 2 times. That's still worse than Version 3. But It's not like the 'dead' status of a sensor means it won't work. I don't use virtual devices. If you decide to test it, I would REALLY appreciate that! Like you said, it's scary and you have to be confident that recovery works for you...

Maybe I should thank everyone (including myself?) for not giving up... trying, debugging, excluding/including/reconfiguring, moving modules, and filling bugzilla with information...

[derelict 0]

Wrap Up from my side with 4.019

- Update go through the process, after restart no Z-Wave communication there at all; recovered and second try: Z-Wave communication is back after about 30 minutes

Please login or register to see this image.

/emoticons/default_icon_evil.gif" alt=":evil:" />

- all fibaro 2x1,5kw switches doesn´t work anymore. They are there and useable via the web interface but all the connected switches does´t work. The unit does´t recognize if the switch is turned on or off. After exclude and reinclude it seems that they are working again

Please login or register to see this image.

/emoticons/default_icon_curve.gif" alt=":-/" />

- the whole HC2 unit isn´t very stable with this version - Z-wave learning mode only work once, then the window stays open and you have to make a "hard-restart" by switching of the power. Second thing is, that my HC2 shows about 5 times in the last two days the 503 error. For me the whole web interface is worse that in 4.018

I have/had the same experience.... and i've "found out" that it's the zwave process on the box itself which dies unexpectedly.... i don't know why... but it dies every hour or so...

only solution is restarting the box... or SSH Session into the box and (re)starting the zwave daemon (/etc/init.d/zwave restart) ... this requires the HC2 root password however... which you are not supposed to have/know.

[petergebruers 1,268]

(...) i've "found out" that it's the zwave process on the box itself which dies unexpectedly.... i don't know why... but it dies every hour or so... only solution is restarting the box... (...)

Yet another victim with a completely disabled system. To all users: it is my personal opinion that, if you have read all the posts in this topic, checked bugzilla and STILL want to try this 4.019... If you feel the urge to click on 'update'... Well..

DON'T DO THAT

It is more than clear enough that it is NO USE FURTHER TESTING. Not on a HC2 test device with 5 modules and certainly not on a HC2 in production with 50 modules.

This is my personal opinion, and not that of Fibaro.

[D-Vine 65]

would like to test beta version again but with all the message of dead nodes, it scares me away.

how's are scenes working in this version ? (smart lights / LUA scheduler / Auto light in Bathroom )

and virtual devises ?

I think you should check

Please login or register to see this link.

- but I can summarize it for you: there are still many other bugs, I mean other than the ones you mention. But let me say this: I have several lua scripts that trigger from a Aeon 4 in 1 or a Fibaro Door sensor. And they don't fail - a lot. Like... the last 24 hours I haven't see a light come on maybe 2 times. That's still worse than Version 3. But It's not like the 'dead' status of a sensor means it won't work. I don't use virtual devices. If you decide to test it, I would REALLY appreciate that! Like you said, it's scary and you have to be confident that recovery works for you...

Maybe I should thank everyone (including myself?) for not giving up... trying, debugging, excluding/including/reconfiguring, moving modules, and filling bugzilla with information...

I will wait again...

[fergalmccarthy 5]

Maybe I should thank everyone (including myself?) for not giving up... trying, debugging, excluding/including/reconfiguring, moving modules, and filling bugzilla with information...

Beta testers usually get some sort of compensation for their time, like money off final product or free hardware, something that compensates for time, effort, frustration, dealing with wife/girlfriend.

What do Fibaro Beta testers get .........

[stevenvd 51]

Fibaro can you confirm that the API for events is not working?

all calls give me nothing:

/api/panels/event?from=1417171000&to=1417171716

[yuzo 4]

Fibaro can you confirm that the API for events is not working?

all calls give me nothing:

/api/panels/event?from=1417171000&to=1417171716

if i copy and paste your link to mine (4.019 beta) incl. my HC2-ip i get a list like this:

[{"id":94467,"type":"DEVICE_EVENT","timestamp":1417171237,"deviceID":110,"deviceType":"com.fibaro.FGRM222","propertyName":"value","oldValue":99.00,"newValue":95.00},{"id":94464,"type":"DEVICE_EVENT","timestamp":1417171136,"deviceID":4,"deviceType":"com.fibaro.FGMS001","propertyName":"value","oldValue":1.00,"newValue":0.00},

...

[stevenvd 51]

sht, all I get is []

[Dino 0]

Yep Yep......4.019 is worse than 4.018

Just wanted to reconfigure a RGBW module.....and now it is gone......

What the heck....

Oh oh my what a nightmare it is...

When will we get the intercom

Please login or register to see this image.

/emoticons/default_icon_wink.gif" alt=";-)" />

[robmac 173]

sht, all I get is []

Sure the memory usage issue is in the web so api and interface both die on occasions. Are you still unable to restart?

Worse than ever in this version. It is like they are eating memory.

This is all I have running.

Plugins unloaded.

Please login or register to see this code.

Please login or register to see this attachment.

Please login or register to see this attachment.