After investigation It looks that you have started to use icons 192x192x8 😀 but uploading of even same default icon doesn't work because you want to have only size 128x128 ...

Here is downloaded icons from HC3 - newest beta (all 192x192 points):

Please login or register to see this image.

However, it does not always appear.

Please login or register to see this image.

Correct view

I have done some testing with my weather provider and weather condition codes just to find out how Fibaro managed to do complete nonsense out of this.

First of all this list of weather condition codes was still working on the last stable update 5.180:

Please login or register to see this attachment.

at least most of them and above codes are almost same as they were on HC2.

Of course, on HC3 WeatherCondition description is reduced to this list:

• clear
• partlyCloudy
• cloudy
• storm
• snow
• rain
• fog

BTW - in the QA example that mr. @m.roszak or mr. @A.Socha is usually asking you to download from 

Please login or register to see this link.

Since some genius in Fibaro development team changed so that WeatherCondition selects what weather icon will show on dashboard instead ConditionCode that example is now not so incorrect, now is just missing WeatherCondition "partlyCloudy". Of course this still will work only if you also set ConditionCode to one of available ones:

• 4
• 20
• 30
• 32
• 38
• 40
• 3200

Of course, it doesn't matter if you put ConditionCode 40 which is for "rain", but then set WeatherCondition to "clear" because you will get icon for "clear" even ConditionCode is set to 40. Only ConditionCode 3200 for "unknown" will show icon with crossed circle for any WeatherCondition that is set.

I do not need to mention that after QA changes WeatherCondition from eg. "clear" to "rain" (no matter if ConditionCode is set to proper code or not), then dashboard or GUI home page must be refreshed at least in Firefox to show appropriate icon.

Since ConditionCode and WeatherCondition can be mixed and then WeatherCondition has higher priority next table is for info only and might be wrong:

Please login or register to see this code.

Notice that weather conditions "cloudy" and "partlyCloudy" has same ConditionCode, but on dashboard show different icons  

So, now I ask Fibaro:

What is weather ConditionCode actually used for ??!?!

Have you really deleted all weather icons from above picture and left only few for the WeatherCondition list? 

If I test in Swagger rate 0.1:

Please login or register to see this code.

I get the response status 204 operation succesfull

If I test in Swagger rate 0.0:

Please login or register to see this code.

I get the response status 400:

Please login or register to see this code.

If I test in Swagger rate -0.1:

Please login or register to see this code.

I also get the response status 400:

Please login or register to see this code.

Or am I missing something?

I do believe that you can count incoming and outgoing messages of the device even there is no template.

Please consider showing number of Communication (Frames/Hour) for these devices also

Since currently ZigBee devices are to fully supported it could be a great idea to have same table for ZigBee devices.

Thank you

Please login or register to see this attachment.

No matter if above call to change Quick app variable is executed from scene or from Quick app it still converts string with numerical value to number.

Since Quick app variables can store numbers, but then edit button is gone and can't be changed by user anymore on Variables tab of the Quick app that is actually problem.

Here is QA debug variable value before this call:

Please login or register to see this attachment.

After executing this command:

Please login or register to see this code.

This is a result:

Please login or register to see this attachment.

As you can see variable value is changed, but with number, not string and button to edit variable is gone.

Since QA variables are string only values, why above command does conversion of string into number?

Or even better question is why QA variables if hold number value can't be edited?

Please login or register to see this attachment.

2 - The selected LUA file is no longer highlighted, making it much less clear. The highlighting in the top bar is not sufficient.

Please login or register to see this image.

Thank you

Opening access page and while no changes done the Unsaved changes popup window shown

Please login or register to see this spoiler.

Please login or register to see this attachment.

I compared LUA scenes on HC3 and HC2 and find out that abilities were better on HC2.

Here is JSON response for one of my scenes on HC3:

Please login or register to see this spoiler.

What I'm missing in LUA scenes on HC3 and was there on HC2:

1. properties - it was really nice to use it on HC2 to store some information to easy find scene by e.g. role and module.
2. iconID - it was much easier to manipulate icons on HC2.
3. arguments - possibility to send some arguments to the scene when called to run.
4. categories - why use category ID instead of the category name same as on QA?
5. maxRunningInstances - why is not possible to setup this through GUI interface? I guess it can be changed with API call? What is the maximum of running instances?

Why are scenes on newer gateways HC3, HC3L etc. worst than on the HC2?

NOTE - this is not new topic, but is still interesting after 5 years of HC3(L) firmware development since there was no much improvement until this last beta.

And to top it of you have also removed the ability to reconfigure the Z-wave, Even using the Installer app fails to reconfigure the mesh and shows no information for any of the devices.

For me this is causing huge issues as we have multiple large projects currently underway and are now unable to finish these installs properly.

I just discovered that all the extra messages only appear when the history display is open and they are not saved. The "disabled" messages are gone when reopening the history. But the flooding of new messages makes the history unusable for me.

What's new:

Devices

    Adapted the Husqvarna plugin to the new manufacturer API.

Other

    Documents for Privacy Policy and Terms of Service have been separated when updating the Hub.
    Changelog history added when updating the Hub version.
    Adapted the appearance of swagger to the new UI design.
    New look for entering your security PIN.

Quick Apps

    The preview tab is updated on-the-fly after copying the JSON view.

Scenes

    Scene launch optimization.
 

Z-Wave

    Z-wave engine 3.0 is set as default in the FTI process.
    Updated parameters template for FGR-224/Roll-Control2 for version 8.2.
    Added support for class Thermostat Fan Mode version 5.

Bug Fixes:

Climate

    Fixed incorrect calculation of the temperature value for thermostats auto mode.

Devices

    Full https support for Nice Cameras and NVRs.
    UI fixes for parameters values refresh in Z-Wave devices configuration.
    Fixed Smart Implant device configuration flow when "Other" option is selected.
    Fixed display of statuses in the Dashboard for colorController and multilevelSwitch devices.
    Optimised web UI wizards for some devices.
    Fixed an issue where the device removal process in the mobile app would loop.
    Fixed issue with loading multiple icons for devices.

Gateway connection

    Fixed device counting in backups for the Master Hub.

Nice*

    Fixed moving to favorite position for mono devices.

Other

    Fixed acceptance of entered login data using Enter on the keyboard.
    Improved modals appearance for Manage Access and rights edition.
    Fixed the appearance of system modal windows.
    Fixed the connection type selector in the Smart Implant device Wizard.
    Fixed issues for the /api/scenes endpoint in swagger.
    Fixed SVG icon colors in dark mode for scenes.
    Fixed the display of days when selecting from the calendar.
    Changed the size of buttons in the user interface.
    Changed the appearance of the stepper component.
    Fixed the visibility of text messages in the interface.
    Fixed display of device protocol logos.
    Minor UI/UX fixes.

Quick Apps

    Added support for uploading external icons for Multilevel Sensor device type.

Scenes

    Removed redundant unsaved changes dialog when no changes were made when editing scenarios.
    Fixed issue with saving default Morning Scenario after making changes.
    Fixed scenes trigger based on current color for Block Scenes.

Z-Wave

    Fixed the issue of lost Zipato RFID device reports.**
    Fixed invalid parameters 2,3 value for HeatIt Z-Temp3 device.
    Fixed a rare issue where learning mode would freeze.
    UX fixes for Z-wave parameters.
    Fixed template for Aeon Multisensor 6 device.

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.

Security:

    Due to the upcoming new cybersecurity regulations (RED), work has been implemented to improve the product's security level to comply with the EN18301 standard and the latest security guidelines.
    The user password reset procedure has been changed - user sets a new password himself.
    The number of required characters in a user password has been increased to 12 - for new users and when changing the password for existing users.
    Added email notification for administrator regarding unauthorized login attempts when an unknown user logs in.
    The default login password for the FTI process has been changed for the ones from device label.
    Improved security for requests from localhost.
    Increased security for plugins: Husqvarna Mower, Tedee.
    Cross-Site Scripting vulnerabilities fixed.
    Additional security for users in the Recovery Mode area.
    Added protection against PIN brute-force attacks.
    It is possible to make 3 attempts to disarm alarm partition before the alarm is triggered.
    The procedure for assigning passwords to new local users has been changed - the user sets his own password in the system.
    Improved encryption and security in databases.
    Added the ability to report a security issue has been added as an extension of the Support Department option.
    Added information for the user when attempting to perform potentially dangerous actions in the interface.
    Sensitive device data removed from databases.