Update 3.570

[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.

3.70:

- New json library in LUA.

- User icons in remote access.

- Z-Wave bug fixes.

- Fibaro FGFS101 Flood Sensor support.

- Importing devices from other HC2 gateways (gateway connections).

- New virtual devices with support for iPad and Android apps.

- Changes dedicated to iPad v1.1 application and new Android application.

- Other minor bug fixes.

Bugtracker tickets:

- 0000899: Can't turn off potential fire and freeze notifications

- 0000511: SP814 template (broken)

- 0000142: Everspring ST814

- 0000782: After HC2 restart/upgrade the RGBW module is shown as 'On' in GUI

- 0000882: Virtual Device popup

- 0000890: When setting new value for ID of a slider(not tested for other controls) the old ui..value tag in JSON is not removed

3.558:

- RGB panel added.

- Fibaro RGBW Controller support.

- Added notifications (email and in UI) about devices low battery level.

- Support for iPad application and new Android application.

- Added possibility to sort sections, rooms, devices and scenes in configuration interface.

- New Event Panel - TimeLine.

- Possibility to move views in Dashboard.

- Possibility to change the type of binary sensor, e.g. motion sensor to smoke sensor.

- Information about last state change of the sensor (e.g. door).

- Fibaro Alarm panel added.

- Added possibility to reset device energy data.

- New languages: Russian, Danish, Finnish, Chinese.

- Bug fixes in showing and configuring power measurements.

- Bug fix in saving Advanced mode of GPS position reading frequency.

- Bug fix in showing information on the map in Family panel.

- Bug fix in VoIP panel - fixed logging in as system user.

- Z-Wave bug fixes.

- Aeon Labs 4in1 bug fixes (attention, in case of not working properly, device must be re-added to the system).

- Other minor fixes in UI and translations.

Bugtracker tickets:

- 0000080: Cameras do not display in IE10

- 0000200: Can't use a binary sensor as an input for bell push in video gate.

- 0000325: Parameter 42/45 representation of wallplug in GUI messed up

- 0000390: Rooms icon

- 0000419: Brak aktualizacji w zakładce pomieszczenia

- 0000488: fibaro:killScenes(ID) doesn't work

- 0000494: Wrong energy usage descriptions in energy panel

- 0000510: call wakeUpDeadDevice in scene seems not work as expected

- 0000515: Problem w wyznaczenia godziny wschodu i zachodu słońca

- 0000519: decimal points or comma's in variables panel

- 0000550: Don't mark as dead node option not saving

- 0000544: LUA 'Attention' dialog rendering

- 0000545: Improve alarm panel labels used in 'status' drop down

- 0000546: Device name length needs to be enforced when editing

- 0000556: złe tłumaczenie

- 0000590: Energy panel settings tab has a save button

- 0000596: Dashboard General Main sensors show Wrong DEAD

- 0000602: no ptz actions with a foscam like camera

- 0000647: Problems with setting associations

- 0000667: In dashboard view Danfoss thermostats are counted as dead

- 0000673: In General Panel on Dashboard all FGK101 Door/Window Sensors counted as doors even if change device kind to window sensor

- 0000678: fibaro:log not work in devices panel "/fibaro/xx/devices"

- 0000679: Aktualne zużycie energii

- 0000719: Can't use private icons for window sensor

- 0000769: Error message in dasboard

- 0000778: Missing translation

- 0000784: in german translation no values in devices configuration

3.548:

- Changes related to new version of operating system repositories.

[Shad 4]

I have this version 3.570.

[wasil 0]

So when You try to add any battery operated device You should have information during setup to wake up device manually. Even if You do not have this message try to press 3x tamper inside door sensor and check if that helps.

[Shad 4]

I did it but nothing. Stay like a sensor -_-'.

I will go tomorrow on my friend house to try again.

[Guest shapa]

Each day the system is less stable (reboot not helps).

Very frequent, sometimes big delays in scenes execution (i.e. it could take up to 10 minutes to switch on lights after motion is detected)

Sometime scenes (especially scheduled) are completely not executed (like outdoor lights dawn scene - works ok in 95% cases but randomly they are not switching on)

Very hard to add or remove any device (multiple attempts should be made, quite frequently - "sending error")

[Lauri 6]

Could it be that you have some scenes that keep on running all the time and they never stops?

If you do not have many big things controlled by scenes, try to deactivate all and see if system keeps hanging..

[Guest shapa]

I doubt it could be a scene issue.

I've got same problems in earlier betas (just a few months ago) and fibaro support didn't find anything suspicious in scenes. However, they found a lot of bugs in their code.

Nothing is really changed since (a few devices added, that's it).

[gilbert 0]

My opinion is that scenes (and the main loop of virtual devices) can be very tricky. One scene can run in parallel endlessly and scenes can trigger other scenes which, on their turn, can trigger new scenes. If in one bad scene an endless loop occurs, HC2 will explode with endless loops (I don't know if Fibaro possibly handles such cases), which will not be good for the performance of the HC2

Afterwards, it's almost impossible to find scenes that cause incorrect behaviour and when creating scenes, a bad scene is easily created without proper debugging.

[Guest shapa]

Well, Fibaro team doing everything to make our lives more complicated.

No any proper debug, no shell / logs access... Yep, it could be some scene issue. No way to know which one.

No way to check some simplest thing - CPU load (the system could be busy for some reason, or memory leak, or...)

[wasil 0]

That is true shapa I wonder to have some diagnostic software to check if there is everything all right with Home Center. I think that Fibaro team is going to develop this software but I will take few months more...still have to wait.

[gilbert 0]

I'm redesigning my scenes again and add to all scenes a check if not too many duplicates of the same scene are running. Otherwise, I get a notification and know there is something working incorrectly.

Please login or register to see this code.

[Guest shapa]

gilbert - it is just to check duplicates (I'm using similar code for along time), no way to know about some CPU hogging infinite loop for example.

[robmac 173]

another way to check instances of scenes is

Please login or register to see this link.

... runningInstances field

I have also found that

heating panel is a bit of a hog when I was using many zones.

and

main loop I have given up as it makes my HC2 unstable with the number of devices I want to use

[deanrparry 19]

Same here main loop is unusable under most circumstances here aswell

[robmac 173]

Hi Andrew,

Any update when the battery usage will be fixed?

Please login or register to see this link.

[Guest shapa]

robmac,

Did you tried to re-include the HRT4?

I've got plenty of them and still using original set of batteries (7 months...)

[robmac 173]

Hi Shapa,

Yes tried that but did not help.

Used to be fine until release with battery level check.

[ Added: 2013-10-28, 23:43 ]

Hi Shapa,

Do you see "Device is asleep" regularly in the status bar of your devices when nothing is happening?

thanks