Update 3.590

[A.Socha 133]

WARNING! In case of update from old version, v1.x, after that update all users will be deleted. Admin password will be reset. Also 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.

Mobile apps fully working with this version:

- iPhone app - version 2.1.1 (available on the App Store),

- Android phones app - version 1.3 (available on the Google Play),

- iPad app - version 1.2 (available on the App Store).

3.590

- Optimized for remote access activities.

- Support for Fibaro Motion Sensor.

- Fibaro Alarm minor fixes.

- Gateway Connections improvements.

- Z-Wave engine improvements.

- Other minor bug fixes.

3.580

- Testing connection with Satel alarm.

- Faster HC2 booting.

- "Undo" button after predefined alarm scene has started.

- PIN codes added to alarm (warning: PIN code will be reset after this update and has to be set up again).

- Information from Fibaro icon added.

- Entry time and exit time in Fibaro Alarm.

- Excluding sensors from alarm system.

- Excluding devices from events history.

- Possibility of setting sensor as always armed or always disarmed.

- Changes dedicated to mobile apps new versions.

- Importing gateways - information about connected gateways.

- Possibility to change temperarure unit.

- Importing / exporting virtual devices.

- Network settings fixes.

- Virtual devices changes and fixes.

- RGBW device fixes.

- Backups creating fixes.

- Virtual devices update - sleep in main loop increased to 3 seconds.

- Fibaro Alarm fixes and changes (i.e. always armed / always disarmed, multi arming / multi disarming devices, excluding sensors from alarm system, configuring sensors).

- Stopping scenes and blocking saving scenes and devices while alarm is active.

- Fixed searching for other HC2 units in local network.

- Other minor bug fixes.

Bugtracker tickets:

- 0000077: Logi

- 0000141: Włączanie alarmu z iOS

- 0000398: Error uploading .png icons

- 0000413: HC2 show me 0.01 W usage for one fibaro dimmer Turned OFF !

- 0000414: HC2 show me 0 W usage for one fibaro 3k switch Turned ON but 10W declared !

- 0000522: In API field "type" appears twice in properties node, sensor, binary light etc.

- 0000531: Show the scene in interfaces changed to "No" without notification -> scenes not visible in Iphone & Android app.

- 0000585: Device Declared power consumption does not work sometimes

- 0000631: 3.548 json.encode crashes in virtual device

- 0000723: 'modified' field in /api/devices is not updated with new timestamp after device state changed

- 0000742: Add delayed trigger to alarm panel

- 0000757: Extra options for "device kind"

- 0000942: Alarm Panel Problems

[remcoploeg 10]

I have strange issues since the 3.590 update (I have restarted already several times);

1. Ipad app crashes a lot (have to hit the refresh button), and when it runs it's really slow, slow and slow

2. Some lights are on when I arrive at home (ore are suddenly on), but there no reason why

3. Slow, slow slow. sometimes I have the put the power off of the HC2 to get it work again

Anybody an idea?

@Fibaro;

- why we can't see an overview of the processes / running scenes or other thing in the HC2? This really help us understand why the HC2 crashes. Or is this in 4.x resolved?

- More logging possibilities! Why can't I see in the eventlog when a scene runs (yes I can use debug or log in my scene...)

[petergebruers 1,268]

With this version I no longer have these "semi-dead nodes". Had a few of them per week. I run a script hourly to detect and reanimate them (modified code from Fibaro support) and it hasn't reported anything since a few days. I had to issue "requestNodeNeighborUpdate" on two plugs (close to each other) that occasionally wouldn't respond to a script and then everything was very stable!

[ Added: 2014-03-11, 19:43 ]

I have strange issues since the 3.590 update (I have restarted already several times);

(...)

3. Slow, slow slow. sometimes I have the put the power off of the HC2 to get it work again

Fibaro asked me to change this:

Please login or register to see this code.

into this:

Please login or register to see this code.

I understand it makes a difference, especially in loops, by not sending unnecessary commands... I read that rebooting the HC2 clears the backlog of commands still to send. I think your problem description fits this explanation...

[Guest shapa]

HC Lite - some weird issues.

Network - static, it work for a while then jumping to the old address (received by DHCP initially)

What is interesting, it is also updating gateway connection settings on HC2

I.e., initial boot - DHCP received address 172.16.1.67

Switched to static, 172.16.1.36. Works for a while (few hours?), then suddenly jumping back to 172.16.1.67. Without reboot or any failures. Some watchdog feature??

Gateway reboot not helps.

[ccie4451 0]

HC Lite - some weird issues.

Network - static, it work for a while then jumping to the old address (received by DHCP initially)

Shapa, I experienced the exact same issue with my HC Lite. I resolved it by re-entering the static IP address details, saving the config, and rebooting. I also deleted the backup I had initially created just in case it was trying to read something back from that.

It has now been stable on the configured static IP address for eight days and counting, and my HC2 gateway connection setting is also remaining stable.

[Guest shapa]

ccie4451, yes, I did the same. finally it works...

One more bug to fix.

[1152 33]

Woke up at night. Tried to access my network. Extremly slow response to all I tried. HC2 has been running stable for 16 days. Now this.... Whats up?

PS Tried to restart the HC2 from the config page. No Joy first time. Second time Joy! All back to normal now. Still like to know what made the system almost hang?

[Lauri 6]

Have anyone else trouble with power consumption option?

If I use declared power consumption on fibaro relays and dimmers then they appear to change frequently into degrees, luxes, percentages etc.. how is that? I know that if I delete power consumption value and add it again, then it will be ok. But after some time I still see 50% or 50lux, or even 20,5C instead of 50W

[Guest shapa]

Guys, are you kidding me?

HCL 3.590 is broken, I opened critical case, no feedback at all!!!

"

Type your response ABOVE THIS LINE to reply

Re: HCL critical issues

Fibaro | Apr 20, 2014 09:01PM CEST

Thank you for submitting your request. We have received your request and are working on responding to you as soon as possible. If you have any additional information to add to this case, please reply to this email.

Thanks in advance for your patience and support.

This message was sent to [email protected] in reference to Case #4593."

[UrSv 6]

Guys, are you kidding me?

HCL 3.590 is broken, I opened critical case, no feedback at all!!!

One problem is not the same as broken. It works fine for most users. No feedback at all is probably not really the best description since today is the first day after holidays so a more appropriate statement would be "no feedback within 8 working hours" rather than "not at all". Support will most likely get back to you as soon as they can.

[deanrparry 19]

Wonder why my "3.590 (blue text)" displays "3.590 beta (red text)"?

Very odd yet my other box at work shows "3.590 (blue text)"

[j.nowacki 5]

deanrparry, you probably restored backup from 3.591. It can be used on 3.590 but it leaves info about beta version.

[SirMaggot 12]

Yes, same for me, and i restored my backup from v3.591 beta.

[DimaStud 0]

Hello. My device:

HC2 V. 3.590

I have a problem: When I click on save Backup it does not save it, clock start spinning but only for one-two sec. also when i try to get in recovery mode after "diodes will turn ON sequentially, starting from the left hand side" center stop doing nothing. All diodes is glow. I wate for 10 or even more min. And even after that its unposible to get in recovery mode(i try to set up manualy static ip via pressing + for long time, but it gives me nothing). And nothing is happen. And one more problem: sometimes it`s unposible to seave or change scenes.

What it can be and how can i fixed it?

[A.Socha 133]

DimaStud, please contact with [email protected] that can be a hardware problem

[DimaStud 0]

A.Socha,

already done it. I hope it will help me.

p.s. interesting that home center working on normal mode, but with problems that i mention above.

[deanrparry 19]

My garage light has been on for most of today and motion sensor never went safe again! Stable firmware my arse how about you pay my electric bill?

[MalvinYNJ 4]

My motion sensor gave me 2-3 false alarms for the past week after having installed for 3 weeks. What's happening.

[novos 9]

My scene stopped work (((

I can't RUN it any more Why? 3.590 Version.

[j.nowacki 5]

MalvinYNJ, is it installed in place with radical temperature/light changes or drafts?

novos, have you tried rebooting HC2? If clicking RUN do not cause any results, please clear cache or try different browser. If it is not matter of interface, we will take a look at a scene itself.

[TimJWatts 4]

A.Socha

Thanks for the quick reply and the seemingly stable release

But

On Aeon HEM 2 - configured and showing KwH values (this version issues

Please login or register to see this link.

)

When I click

"show Energy Consumption measurements"

and save

It remains unclicked and no energy consumption measurements seen

Have tried Chrome and just now Explorer and Ipad - same result

Seems the same as this bugzilla report

Please login or register to see this link.

Fixed - by Configure all devices again: - ?upgraded device -> but now lets me report energy usage. Thanks.

Hopefully back to stable Hc2

Glenn[/u]

Thank you! Just used this trick to fix my new TZ88E that would not report energy.