Update HC2 4.020 BETA

[I. Szymanski 0]

Fibaro Home Center 2 v 4.020 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.020:

New Features:

Pre-Update Confirmation - installing update on 4.020 or newer will prompt user additional confirmation.

Mesh Network Reconfiguration - available on Configuration -> Z-Wave Network

Fixed Issues:

Incidental marking devices as dead

Horstmann Devices support

Many other Z-Wave engine 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.

Devices Polling may not work properly - devices state in UI may be refreshed only after action taken.

Previous:

Breached senser with Arm Delay causes instant alarm after being armed

Data range selection in event panel doesn't work properly

Devices imported via Gateway Connection may have no icons

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

Horstmann Thermostat HRT4-ZW higher battery usage in some cases

Doorlocks some functions may not work properly

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.

[stevenvd 51]

does someone use json in this fashion?

json = json.encode(jsonTable);

HC2:PUT("/api/panels/heating?id="..zoneid, json)

for me it is not working anymore. json decode works ok

thanks

Ah, I thought it was me. I use it in the same way. But it does not work anymore... So clearly it's something they broke... why?

[mmdonnelly 0]

So. . . When's z wave going to work? Nodes still going dead and NEVER show current correct status. I always have to turn on and off a few times to actually get status correct for that session.

[JanJoh 1]

I am seeing that battery sensors stop reporting new values after about two hours. (aeon 4-in-1)

anyone seeing same thing?

[robmac 173]

Yes but related to a complete lock up every few hours.

[ Added: 2014-12-01, 08:14 ]

made a bug report on bugzilla:

0002138: Universal Binary Sensor wrong temperature in scene's

if someone has to add something too that, please do

hope this gets fixed fast because i use the sensor as anti freeze protection on my water pipes outside, and it is going to freeze here.

Added a note. Not sure when this started. I am not convinced it is new behaviour just more prevalent. The random nature reminds me of non thread safe or bad buffer use in code.

[christos 9]

I don't know if this has to do with the latest update but here is a problem i'm facing now

i have included a new Door Window Sensor close to my HC2.....

Made all configurations as needed

i played with the magnet and was looking at the interface and was working just fine

THEN

I move the sensor to the basement ( i took my laptop with me )

i play with the magnet open close and after some time i see that it starts to report back to the interface just fine.... meaning that it found a new route ... right???

NOW

i take battery off so i can screw the sensor to its place..... put battery back in .....

My sensor shows up as DEAD.....

no matter what i do ....

[petergebruers 1,268]

So... Are you all going back to 3.X? I checked this thread + bugzilla and I think we all are done with this beta...

The random nature reminds me of non thread safe or bad buffer use in code.

Doh! That's exactly what I have been thinking. Pure speculation of my part, of course. I have done some multithread programming myself, and indeed it reminds me of bad synchronization... But again, that's speculation.

[ Added: 2014-12-01, 10:08 ]

i take battery off so i can screw the sensor to its place..... put battery back in .....

My sensor shows up as DEAD.....

no matter what i do ....

I have seen this problem with 3.X too. Not often though.

Maybe the sensor got accidentally reset... Did you notice a "double LED blink" when you put back the battery?

Anyway... Try to add it again. If it was not reset, it may fix your problem and restore the connection. And if it WAS reset, you get a new device, and your problem is solved too...

This is the reset procedure, from the manual:

1) Take off the Sensor's cover and remove battery.

2) Touch the Sensor's body with a magnet,

3) Insert the battery,

4) Remove the magnet from the Sensor's body,

5) Remove the battery

6) Re-install the battery,

7) Reset will be confirmed by double LED blink.

I had this problem at least once (accidentally)...

[christos 9]

So... Are you all going back to 3.X? I checked this thread + bugzilla and I think we all are done with this beta...

The random nature reminds me of non thread safe or bad buffer use in code.

Doh! That's exactly what I have been thinking. Pure speculation of my part, of course. I have done some multithread programming myself, and indeed it reminds me of bad synchronization... But again, that's speculation.

[ Added: 2014-12-01, 10:08 ]

i take battery off so i can screw the sensor to its place..... put battery back in .....

My sensor shows up as DEAD.....

no matter what i do ....

I have seen this problem with 3.X too. Not often though.

Maybe the sensor got accidentally reset... Did you notice a "double LED blink" when you put back the battery?

Anyway... Try to add it again. If it was not reset, it may fix your problem and restore the connection. And if it WAS reset, you get a new device, and your problem is solved too...

This is the reset procedure, from the manual:

1) Take off the Sensor's cover and remove battery.

2) Touch the Sensor's body with a magnet,

3) Insert the battery,

4) Remove the magnet from the Sensor's body,

5) Remove the battery

6) Re-install the battery,

7) Reset will be confirmed by double LED blink.

I had this problem at least once (accidentally)...

Thanx Man.....

That did the trick

i had to reset the sensor and include it again

working like a charm now

[Guest]

Hi!

Could you describe further the problem with json.encode (include full lua source code and error messages if there are any)? I've tested it myself and it works properly:

Please login or register to see this code.

I've noticed one thing that might cause you problems. You assign the result of json.encode to variable named 'json'. This name collides with the name of json module and make this module inaccessible for the end of the script. Please use other name e.g. 'jsonStr' as I did in the example above.

[stevenvd 51]

json.encode and decode work. Just not for putting it back into the heating panel.

My code:

(not full for loop, just the first part).

Please login or register to see this code.

Result of the second (after editing the vacationtemperature) jsonStr =

: {"created":1417194619,"name":"Studeerkamer","id":5,"properties":{"handTemperature":21,"wednesday":{"night":{"temperature":16,"minute":0,"hour":23},"morning":{"temperature":20,"minute":15,"hour":6},"day":{"temperature":17,"minute":10,"hour":8},"evening":{"temperature":18,"minute":45,"hour":17}},"thursday":{"night":{"temperature":16,"minute":0,"hour":23},"morning":{"temperature":20,"minute":15,"hour":6},"day":{"temperature":17,"minute":10,"hour":8},"evening":{"temperature":18,"minute":45,"hour":17}},"rooms":[3],"vacationTemperature":15,"tuesday":{"night":{"temperature":16,"minute":0,"hour":23},"morning":{"temperature":20,"minute":15,"hour":6},"day":{"temperature":17,"minute":10,"hour":8},"evening":{"temperature":18,"minute":45,"hour":17}},"saturday":{"night":{"temperature":19.5,"minute":0,"hour":23},"morning":{"temperature":16.5,"minute":10,"hour":1},"day":{"temperature":19.5,"minute":30,"hour":8},"evening":{"temperature":19.5,"minute":45,"hour":17}},"friday":{"night":{"temperature":16,"minute":0,"hour":23},"morning":{"temperature":20,"minute":15,"hour":6},"day":{"temperature":17,"minute":10,"hour":8},"evening":{"temperature":18,"minute":45,"hour":17}},"sunday":{"night":{"temperature":16,"minute":0,"hour":23},"morning":{"temperature":16,"minute":10,"hour":1},"day":{"temperature":19.5,"minute":30,"hour":8},"evening":{"temperature":19,"minute":45,"hour":17}},"handTimestamp":1411659038,"monday":{"night":{"temperature":16,"minute":0,"hour":23},"morning":{"temperature":20,"minute":15,"hour":6},"day":{"temperature":17,"minute":10,"hour":8},"evening":{"temperature":18,"minute":45,"hour":17}}},"modified":1417194619}

[tcviper 20]

Anyone any idea what exactly Mesh network reconfiguration: does? Is it wise to run this once to see if it can become better or is it only good to run this when lots of things have changed?

[MorpheusRO 1]

json.encode and decode work. Just not for putting it back into the heating panel.

My code:

(not full for loop, just the first part).

Please login or register to see this code.

Result of the second (after editing the vacationtemperature) jsonStr =

: {"created":1417194619,"name":"Studeerkamer","id":5,"properties":{"handTemperature":21,"wednesday":{"night":{"temperature":16,"minute":0,"hour":23},"morning":{"temperature":20,"minute":15,"hour":6},"day":{"temperature":17,"minute":10,"hour":8},"evening":{"temperature":18,"minute":45,"hour":17}},"thursday":{"night":{"temperature":16,"minute":0,"hour":23},"morning":{"temperature":20,"minute":15,"hour":6},"day":{"temperature":17,"minute":10,"hour":8},"evening":{"temperature":18,"minute":45,"hour":17}},"rooms":[3],"vacationTemperature":15,"tuesday":{"night":{"temperature":16,"minute":0,"hour":23},"morning":{"temperature":20,"minute":15,"hour":6},"day":{"temperature":17,"minute":10,"hour":8},"evening":{"temperature":18,"minute":45,"hour":17}},"saturday":{"night":{"temperature":19.5,"minute":0,"hour":23},"morning":{"temperature":16.5,"minute":10,"hour":1},"day":{"temperature":19.5,"minute":30,"hour":8},"evening":{"temperature":19.5,"minute":45,"hour":17}},"friday":{"night":{"temperature":16,"minute":0,"hour":23},"morning":{"temperature":20,"minute":15,"hour":6},"day":{"temperature":17,"minute":10,"hour":8},"evening":{"temperature":18,"minute":45,"hour":17}},"sunday":{"night":{"temperature":16,"minute":0,"hour":23},"morning":{"temperature":16,"minute":10,"hour":1},"day":{"temperature":19.5,"minute":30,"hour":8},"evening":{"temperature":19,"minute":45,"hour":17}},"handTimestamp":1411659038,"monday":{"night":{"temperature":16,"minute":0,"hour":23},"morning":{"temperature":20,"minute":15,"hour":6},"day":{"temperature":17,"minute":10,"hour":8},"evening":{"temperature":18,"minute":45,"hour":17}}},"modified":1417194619}

Instead of connection:PUT("/api/panels/heating?id=" .. heating_section, jsonStr), just use connection:PUT("/api/panels/heating/" .. heating_section, jsonStr) and it should work...

I discovered this behavior a few betas ago... It seems that ?id= is removed from new api, or maybe is only a bug...

Anyway, I changed all my code to use "/" instead of "?id=" and I didn't had any problem since.

[stevenvd 51]

Hero! Thanks

Please login or register to see this image.

/emoticons/default_smile.png" alt=":)" srcset="https://forum.fibaro.com/uploads/emoticons/[email protected] 2x" width="20" height="20" />

[nicohi 19]

I have found a new ultra bug. Since yesterday I am searching why most of the scene I use in lua are not working with the good value. I found, look a that :

Code executed :

Please login or register to see this code.

Results after executing more time :

[DEBUG] 15:24:37: 18

[DEBUG] 15:24:38: 18

[DEBUG] 15:24:39: 18

[DEBUG] 15:24:40: 18

[DEBUG] 15:24:41: 18

[DEBUG] 15:24:42: 18

[DEBUG] 15:24:51: 18

[DEBUG] 15:24:52: 46.56

[DEBUG] 15:24:53: 46.56

[DEBUG] 15:24:54: 46.56

[DEBUG] 15:24:55: 46.56

[DEBUG] 15:24:56: 46.56

[DEBUG] 15:25:16: 46.56

[DEBUG] 15:25:17: 46.56

[DEBUG] 15:25:18: 46.56

[DEBUG] 15:25:19: 46.56

[DEBUG] 15:25:20: 46.56

[DEBUG] 15:25:21: 46.56

[DEBUG] 15:25:28: 46.56

[DEBUG] 15:25:29: 46.56

[DEBUG] 15:25:30: 46.56

[DEBUG] 15:25:31: 46.56

[DEBUG] 15:25:32: 46.56

[DEBUG] 15:25:33: 20.7

[DEBUG] 15:25:38: 4

[DEBUG] 15:25:39: 4

[DEBUG] 15:25:40: 4

[DEBUG] 15:25:41: 4

[DEBUG] 15:25:42: 18

[DEBUG] 15:25:43: 18

And what is ID 60 module : A ST814 and this is the reading of temperature... Have the same for all module, FGMS, ST814 etc...

What is that ??? ID table is out or new bug in 4.020 ?????

[Guest]

I confirm that MorpheusRO's answer is correct. We're changing design of our REST API to use clean URLs:

BEFORE:

Please login or register to see this code.

CLEAN URL:

Please login or register to see this code.

Old links should work too so you can easily adapt to the new design. Hovewer, as you've found out, they don't work for heating panel which might be considered a bug in this case.

To sum up, please use clean URLs to all REST resources (for versions 4.xxx)

Please login or register to see this image.

/emoticons/default_icon_smile.gif" alt=":-)" />

[nicohi 19]

j.bacic, an idea for the bug i have ? Should I open a ticket on bugtracker for that ?

[Guest]

Reading properties associated with temperature is broken in 4.020. This bug is already fixed and patch will be included in the next beta release (

Please login or register to see this link.

).

You can use the workaround below in order to get property value but I highly recommend to wait for the next version to be released. Hovewer, if you decide to apply it, remember to remove this code after installing 4.020.

Please login or register to see this code.

Sorry for the inconvenience.

[nicohi 19]

Thanks for reply. I could potentially wait, but an idea of delay to know what I do ?

[Ucciogenerale 2]

I don't know if this has to do with the latest update but here is a problem i'm facing now

i have included a new Door Window Sensor close to my HC2.....

Made all configurations as needed

i played with the magnet and was looking at the interface and was working just fine

THEN

I move the sensor to the basement ( i took my laptop with me )

i play with the magnet open close and after some time i see that it starts to report back to the interface just fine.... meaning that it found a new route ... right???

NOW

i take battery off so i can screw the sensor to its place..... put battery back in .....

My sensor shows up as DEAD.....

no matter what i do ....

Christos,

I struggled many times with this behaviour of Fibaro Door Sensor.

You have to remove the battery only if the sensor is open, then far from the magnet.

If you change the battery keeping the sensor closed (with magnet) you will struggle to understand if it is working or not, but the only way is to remove and reconfigure from scratch.

All of this is not mentioned in the instructions.

Regards

[petergebruers 1,268]

You have to remove the battery only if the sensor is open, then far from the magnet.

Yes, that is what I was trying to explain... "Accidental Reset". The way you put it is... very good. I think it should be mentioned in the manual!

[sj3fk3 27]

Is it just me or are all (predefined) alarm actions gone? When i click on edit.. I get an empty box.