update 3.517

[K.Bergmann 2]

Dear Members,

I am proud to say, that we've released stable version 3x interface.

Also, we would like to thank all forum and bugtracker power users who supports our arrangements for this release!

Thank you for your great feedback!

FIBARO Development Team

After update to this software all devices will be automatically reconfigured to work with new system architecture. Reconfiguration progress will be shown in pop-up window.

WARNING! After this update all users will be deleted. Admin password will be reset.

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.

- New, quicker and future oriented system architecture.

- Rebuilded, faster configuration interface.

- Faster communication within Z-Wave network. Faster system reaction for devices states changes.

- Improved, much quicker sending commands to devices via the iOS application.

- Quicker scenes execution.

- Added support and debugging for Lua scripts.

- Automatic conversion from graphic block scenes to Lua scripts.

- Added possibility for Lua debugging.

- Sending sms/email/push notification from scenes.

- Integration with Satel alarm.

- Added support for new device types.

- Energy panel and managing devices with energy measurement.

- New, extended mobile interfaces.

- Power consumption options in block scenes.

- Additional options in video cameras.

- Z-Wave tab in configuration.

- New device inclusion window, informing user of new device configuration stages.

- Helios intercom support

- VoIP panel

- Information top bar and Dashboard - subpage with configurable information views

- New drenchers panel

- Views from cameras in Your Home section

- Possibility to manually add theoretical power consumption for devices not supporting power metering, visible in Energy Panel too

- Support for new device types, new device parameters.

- Modified scenes main screen.

- New Virtual Devices version - now you can add a button or slider executing Lua script.

- Changed configuration interface layout

- Moreover 3000 minor bug fixes and improvements.

[richo 4]

ezHome.nl,

I have the same issue. If you look at the LUA code it seems that in current version if you use OR statement especially with variables HC will trigger the scene even if only variable is changed.

[TANE 12]

ezHome.nl,

I have the same issue. If you look at the LUA code it seems that in current version if you use OR statement especially with variables HC will trigger the scene even if only variable is changed.

Correct also found the same issue in some scenes..

[Guest Sjandu]

Hi

Thanks for the software update. I can see many improvements. The upgrade process itself worked well and the user accounts were recreated.

The Aeon Labs 4 in 1 sensor didnt automatically show the additional sensors after upgrade but did after the second attempt removing and adding the device. I'm just waiting for data from the additional sensors to show.

I did have to reset one of the variables to make the script work.

The only point I had query on so far is:

1. On the energy tab, I only see the option for "The whole house", there are no individual rooms listed below. Is there an additional configuration change I need to make to show them?

Thanks

[Guest jrkalf]

Fix the lua scripting please and make it the same in every part of the device.

- OS.execute has been removed which seriously impact the better developers to make this box awesome.

- LUA scene scripting lacks the implementation of the NET. library to communicate with other devices properly.

- LUA virtual device scripting has the .Net library, but doesn't have any debugging, so it's useless.

Please login or register to see this link.

having the specific issues discussed in this thread, but it's covered by other threads so nobody can or will read it. It can't be bumped up, I can only flood your forums with new postings so it'll draw attention.. Perhaps

Please login or register to see this link.

, so it'll behave like a real forum?

[Guest Sjandu]

Also had one incident where the controller was unresponsive and required a restart.

[Guest Digipat]

Hello;

First I was surprised I had to come to a forum to make my homecenter work.

I did the update and no more connection...

Now I logged in as admin and tried to change the log in... I cannot save it...

Impossible to change admin name and password!!!!

I cannot enter the homecenter expect via the finder!!!

Even with the IP: nothing (and the IP is constant)

I cannot connect via any device, either using the application or opened port!!!!!

I go to change a variable from 0 to 1 and when I save the new figure... it turns back to 0.

I want to change a scene and when I save it... the balls keep turning and never stop...

Please can anyone help me?

I am not an expert but I don't think this is normal....

I am a little bit

Please login or register to see this image.

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

[Guest vayher]

Hello;

First I was surprised I had to come to a forum to make my homecenter work.

I did the update and no more connection...

Now I logged in as admin and tried to change the log in... I cannot save it...

Impossible to change admin name and password!!!!

I cannot enter the homecenter expect via the finder!!!

Even with the IP: nothing (and the IP is constant)

I go to change a variable from 0 to 1 and when I save the new figure... it turns back to 0.

I want to change a scene and when I save it... the balls keep turning and never stop...

Please can anyone help me?

I am not an expert but I don't think this is normal....

I am a little bit

Please login or register to see this image.

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

Check PM please.

[Guest Digipat]

Check PM please.

Thank you for your helping me so fast...

Trying to fix with your help...

[Guest guidetti]

I think it is a bug:

if in the scene I write in graphical mode "IF (from time1 to time2 every time3) AND (ALARM == 1) THEN alarm_device = TURN_ON..."

the alarm_device is activated also if the time3 has not been met. It seems that the status change of the variable "ALARM" activates the "THEN" part of the scene despite the timer. So it is not an "AND" but "OR".

This statement worked fine in the 1.047

[Guest jrkalf]

I think this is a bug:

JSON is disabled or unavailable in scenes?

[Shad 4]

Now we can have the name od device with fibaro:getName(i).

But like you know we want more everytime

Please login or register to see this image.

/emoticons/default_icon_smile.gif" alt=":-)" /> , does it have a way to have the room of the device??

[Guest dsilletti]

BUG:

My HC2 is falling back to DHCP every day even if I setted a Static IP and saved, it shows always Static IP but the IP changes every day... someone with this issue?

[deanrparry 19]

Now we can have the name od device with fibaro:getName(i).

But like you know we want more everytime

Please login or register to see this image.

/emoticons/default_icon_smile.gif" alt=":-)" /> , does it have a way to have the room of the device??

room only seems to return the id 0,1 etc at the moment which is a shame... started on my xbmc notification with icons etc... and room would top it off beautifully!

[Guest paogig]

Hi,

the alarm activation from iphone doesn't work on 3.517!

Everything is fine if I use the web browser on my PC, but when I use the phone no error message is shown (I am tying in the admin password) ad a fast "on-off" click is heard on the switch (2X1,5W).

Everything was working on v1.047....

Any suggestion?

P

[Guest Dennis]

In FW 1.XX I used scenes with conditions but in the new architecture the way it uses conditions acts really strange.

As you can see in the attached file the scene should look up to the condition If Alarm Status is "Thuis" and...... then

But only the first works, the rest also triggers the scene even if the condition has another value.

+1 i have the same problem with al lot of scenes with time and variable conditions.

[Guest guidetti]

This problem could be similar to mine (explained yesterday in the title "BUG in the scenes activated by variable status change").

I switched to the Lua translation and indeed I found that there is a bug in the translation. At the beginning there a condition is evaluated (sourceTrigger["type"] == "autostart") but it seems always negative and in the "else" conditions the implementation of the timer is wrong because there is only os.time > time1 and os.time > time2, always true if the time increment is missing!! So the AND with the variable was not working for that reason.

I corrected it in the Lua and now is fine!!

[Guest Dennis]

This problem could be similar to mine (explained yesterday in the title "BUG in the scenes activated by variable status change").

I switched to the Lua translation and indeed I found that there is a bug in the translation. At the beginning there a condition is evaluated (sourceTrigger["type"] == "autostart") but it seems always negative and in the "else" conditions the implementation of the timer is wrong because there is only os.time > time1 and os.time > time2, always true if the time increment is missing!! So the AND with the variable was not working for that reason.

I corrected it in the Lua and now is fine!!

what line did you corrected or did you removed a line ?

[Guest guidetti]

I have just copied the line "( (tonumber(os.date("%H%M")) >= tonumber(string.format("%02d%02d", "00", "00")) and tonumber(os.date("%H%M")) <= tonumber(string.format("%02d%02d", "23", "59"))) and ((math.floor(os.time()/60)-math.floor(1364079600/60))%3 == 0) and tonumber(fibaro:getGlobalValue("ALARM")) == tonumber("1") )" from the first "local startSource = fibaro:getSourceTrigger();" module activated by "autostart" to the second one (I presume only active) where the time increment "((math.floor(os.time()/60)-math.floor(1364079600/60))%3" was missing!!

By the way the math.floor(1364079600/60) is a little odd...[/u]

[ Added: 2013-03-26, 23:53 ]

I found other problems, I mean scenes working in the 1.047 and now no more functional in the 3.517.

I used a door sensor like a remote to ARM and DISARM an alarm system, using it in a bistable mode through a variable [in the ARM scene "if (remote=breached AND ARMVAR=0) then (.....) AND (ARMVAR=1= and in the DISARM scene "if (remote=breached AND ARMVAR=1) then (.....) AND (ARMVAR=0=]

In the 1.047 the two scenes were mutually exclusive, but no more in the 3.517. I presume the scenes are executed one after the other but it seems that in the 1.047 the "remote=breached" condition was valid only for the first scene executed and now in the 3.517 the condition continues to be valid for long time and for all the scenes, so the system becomes instable. Indeed in the Lua translation all these scenes are executed inside a loop!!

I cannot define this a bug but I can express my concern about this big change in the scene behavior. It is wrong to say that after the upgrade the system is back compatible, it is necessary to rethink about all the scenes. Of course only the simple scenes like "IF event then switch=something" remain functional.

By the way there is no manual explaining these differences in behavior.

[Shad 4]

I have a problem with the window sensor.

I put a contact on it and when I click the door open. But if I activate the parameter14 it stop to work.

Edit: Work great with the the last beta.

[Ctrl-Stuff 0]

BUG:

My HC2 is falling back to DHCP every day even if I setted a Static IP and saved, it shows always Static IP but the IP changes every day... someone with this issue?

+1