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

[JanJoh 1]

can someone whit a aeon 4-in-1 tell me what the default value for param 113 is in 3.59x?

I seem to recall that it was a rather high number?

[MalvinYNJ 4]

Push notification not working in this version. Anyone has this problem?

[Guest fat]

can someone whit a aeon 4-in-1 tell me what the default value for param 113 is in 3.59x?

I seem to recall that it was a rather high number?

Mine shows as 4s

[candrea77 26]

can someone whit a aeon 4-in-1 tell me what the default value for param 113 is in 3.59x?

I seem to recall that it was a rather high number?

Mine shows as 4s

Me too (i'm using beta 4.021) , but this sound very strange.

113 (as far as i know) is the time interval between reporting humidity ........

I've ask aeotec to send me all parameter specification ..... when i've got it i'll share in forum.

Bye

[JanJoh 1]

can someone whit a aeon 4-in-1 tell me what the default value for param 113 is in 3.59x?

I seem to recall that it was a rather high number?

Mine shows as 4s

Me too (i'm using beta 4.021) , but this sound very strange.

113 (as far as i know) is the time interval between reporting humidity ........

I've ask aeotec to send me all parameter specification ..... when i've got it i'll share in forum.

Bye

Please login or register to see this link.

[candrea77 26]

Please login or register to see this link.

Please login or register to see this link.

Thank you .....

So parameter 112 112 and 113 is the time between report value, for the value specifies by parameter 101 102 and 103.

So in my case :

101 = 225 --> Report Luminance , Humidity and Temperature + Battery every 300s

102 = 1 --> Report Battery every 1800s

103 = 0 --> Report nothing every 4s

I'll try to set 102 to 0 (becouse seems already covered by 101) and 112 and 113 to 3600s

Maybe battery may last longer !!!

[globart 5]

MalvinYNJ, pisze o tym od kilku dni w wątku iPhone. Oczywiście ZERO reakcji. Na razie jest nas dwóch + kilka osób z forum międzynarodowego. Nie wiem ile jeszcze trzeba czekać na reakcję, a co dopiero poprawę......