- Changing to Manual mode (Heat, Cool Auto) all OK

- Changing to Schedule mode (Heat, Cool Auto) all OK

- If the climate zone is in Manual mode, trying to change it to Vacation mode is in fact reverting the climate zone to Schedule

When using any of the mobile application, Vaction mode is accepted and shown in the pc view. 

* note: it seems that using "api.put("/panels/climate/"..zoneId,newClimTable)" in a QA for changing a climate zone to vacation does not work as well but changing to manual mode yes.

I also tried to use the Swager and the api.put is accepted with the vacation mode: code 200 but in response details the mode is still "Schedule"

I'm not sure if this is 5.172.23 or earlier, but I don't want to downgrade to test....

If the QA above is saved as encrypted, .fqax, and installed again, there is a reasonable high probability that it starts 2 lua environment for the deviceId.
The output looks like

Please login or register to see this code.

So it seems to be 2 lua processes or environments started, as they don't share the lua global 'A'
The behavior is not consistent. Seven installations of the QA resulted in 2 having this "double instance" behavior.
However, some other forum members have also noticed this with their encrypted QAs.

I have seen this very sporadic in the past with older firmwares and unencrypted QAs, but it has been impossible to reproduce. 
 

----- speculation mode on -----

My investigation at that time steered me towards believing that it had something to do with installation of large files, a possibly resource low box, and a possible race condition when starting the Lua/QA process, resulting in doubles...

Maybe decryption, taking some time, makes the race condition more prominent?
---- speculation mode off -----

Anyway, here I got it twice in seven attempts, with a minimal QA, so I thought it's worth reporting  

See subject and using z-wave 3 engine,  however adding without security work fine .

When trying to add with S2, the error message is something like 'bootstrap failed'.

Any suggestions?  (I have tried to add the unit in physically very close proximity to HC3)

Also I have tried multiple times with the same result every time. 

Looks like in my case, an association I made between a Fibaro Double switch, and another Double switch stopped working after the update. Anyone else experiencing this? 

How can I test this? Or is it something else? 

kind regards,

Jeroen 

Please login or register to see this attachment.

I have recently migrated from Homecenter 2 which had the equivalent setup as below, but without the issue described below.

I have the following

- HC3 running 5.172.23 with Z-wave engine version 3

- HeatIt Z-water (the legacy version) included with S2 securit

- HeatIt Thermostat included with S2 security

Current status

- The thermostat controls through direct association the valve on Z-water (turning on when too cold, and off when too hot)

- I can manipulate the thermostat setpoint from HC3 (web and app) with no problems

- I can manipulate the valve from HC3 (web and app) with no problems

My problem: When the thermostat is controlling the valve, the status of the valve is not updated on the HC3.

Example: So let us say that the valve is turned off and the thermostat turns it on, it will still show as off in the web/app of HC3. If I then in the web/app turn on the vale after that, nothing happens since the valve is already on. But if then turn it off after that in the web/app then the valve is turning off. So the problem is in my view a pure update issue from Z-water to HC3 (a problem I did not have on HC2).

I have taken care to double check all association settings since it is important to have that configuration correctly. The strange thing is that it seems correct from first inclusion of z-water but at the same time it does not look exactly as in HC2 so it is hard to say if this is properly done. Also, HC3 does not accept any other association than the default one which seems correct. It is a bit fishy....

I have also double checked towards the clip below since it seems to work.

Anyone having any experience or idea?

Please login or register to see this attachment.

Please login or register to see this attachment.

Latest 5.172.23 did not correct that.

Please login or register to see this attachment.

What's new:

Devices

    HeatIt Z-Temp3 support added.

    Fantem Home Energy Meter Gen 8 support added.

    Aeotec Home Energy Meter Gen5 2P (US region) support added.

    Added a possibility to change HVAC devices icons.

Gateway Connection

    Possibility to connect hubs from different networks based on provided IP.

Nice*

    Optimized network configuration for better performance.

    Domi WSC parameters template updated. 

Other

    System boot-up procedure performance improvements.

Plugins

    Added support for Satel Integra 256 in old FW revision.

Scenes

    Default behavior for predefined scenario changed - from now no devices are selected by default.

Z-Wave

   Z-Wave radio module SDK updated for Yubii Home and Home Center 3 Light.

Zigbee

    Introduced the mechanism which prevents losing the network configuration in very rare cases.

    MOES Human Presence Sensor ZSS-QY-HP (and other revisions) support added.

Bug Fixes:

Access

    Installer does not see system notifications for administrator.

Backup

    Error while uploading a Cloud backup in rare cases.

Cameras

    Lack of local preview for some cameras in Safari browser.

Devices

    Custom icons do not work for CO Detector device type.

    Lack of correct icons for Silent Open and Silent Close actions on the control dialog.

    Thermostat Linked Device - fixed the issue when cooling and heating actor is the same device.

    Qubino Flush Dimmer 0-10V - fixed optional temperature sensor handling.

    Restored old sets of icons for some device types. 

Energy Panel

    Error during saving Energy Panel settings in some cases.

Gateway Connection

    Issue with listing slaves list in large IP network.

    Restoring a backup after replacing a slave with new unit fixed.

    Stability improvements.

History

    Missing thermostat set-point name in history entities.

Nice*

    Fixed binding procedure from the mobile app for BiDi-Multisensor.

    Corrected parameters template for TT2NBD.

Other

    Small UI/UX fixes.

Plugins

    Missing IP field configuration in Philips Hue.

    Fixed issue with Nice Cameras support in scenes when passwords with special signs are used.  

Quick Apps

    Dropdowns does not work correctly when new view is disabled for mobile application.

    Function setColorComponent doesn't refresh the view when custom color components are used.

    Template for Color Controller device type updated.

Scenes

    Fixed setting slats position for FGR-224/Rol-Control2 group in block scenes.

    Fixed issue in Custom Scenarios when FGKF-601 is used as a trigger.

Z-Wave

    Fixed issues with mesh network reconfiguration.

Known issues:

Z-Wave Engine 3.0

    Some Z-Wave devices are not fully compatible with the new version of Z-Wave engine.

* - Does not apply to HC3L (Home Center 3 Lite).
** - Applies only to Z-Wave 3.0 engine.