Aller au contenu

Hc Lite 4.057 Béta - 23/09/2015


cquint

Messages recommandés

Retard à  cause d'une attaque des serveurs FIBARO:

 

http://forum.fibaro.com/index.php?/topic/19509-update-4057-announcement/page-4

 

We are really sorry for keeping you waiting. We would like to release the update, as it is ready, but we are holding back due to possible attack on our servers. We will try to release it later today, after managing the situation. I apologize on behalf on our whole team for any inconvenience, we are doing our best to stop it as soon as possible. I will keep you posted in that matter

Lien vers le commentaire
Partager sur d’autres sites

Bon, bah à  priori ils sont attaqués... :

 

We are really sorry for keeping you waiting. We would like to release the update, as it is ready, but we are holding back due to possible attack on our servers. We will try to release it later today, after managing the situation. I apologize on behalf on our whole team for any inconvenience, we are doing our best to stop it as soon as possible. I will keep you posted in that matter.

Lien vers le commentaire
Partager sur d’autres sites

Les gars, je voudrais pas vous faire peur, mais je ne peux pas garder ça pour moi.

A un moment, il faudra bien que les dev de Fibaro se professionnalisent un peu, c'est pas normal un log pareil lors d'une mise à  jour, même si à  priori tout a fonctionné. Si leur stratégie, c'est d'appliquer des scripts de mise à  jour bêtement sans aucun test en se disant "bah de toute façon l'utilisateur sur son interface web il ne verra rien", bah ça craint.

 

Extrait du morceau le plus croustillant :

Executing sql files ...
FILE: sql/Borrowed_Devices.sql
Error: near line 1: table "Borrowed_Devices" already exists
FILE: sql/Dashboard.sql
Error: near line 1: table "Dashboard" already exists
Error: near line 6: duplicate column name: positionX
Error: near line 7: duplicate column name: positionY
Error: near line 8: duplicate column name: sizeX
Error: near line 9: duplicate column name: sizeY
FILE: sql/DefaultSensors.sql
Error: near line 1: duplicate column name: DefaultTemperatureSensor
Error: near line 2: duplicate column name: DefaultHumiditySensor
Error: near line 3: duplicate column name: DefaultLightSensor
Error: near line 4: duplicate column name: DefaultThermostat
FILE: sql/Device_Icon_Set.sql
FILE: sql/Drenchers_Panel.sql
Error: near line 1: table "Drenchers_Zone_Drencher_Day" already exists
Error: near line 8: table "Drenchers_Zone" already exists
Error: near line 17: table "Drenchers_Zone_Drencher" already exists
Error: near line 24: table "Drenchers_Zone_Drencher_Cycle" already exists
Error: near line 32: PRIMARY KEY must be unique
FILE: sql/Energy_Tariff.sql
FILE: sql/FastAccessActors.sql
Error: near line 1: table "FastAccessActors" already exists
FILE: sql/FavouriteColours.sql
Error: near line 1: table [FavouriteColours] already exists
FILE: sql/FibaroAlarm.sql
Error: near line 2: duplicate column name: ReadOnly
Error: near line 4: table "Alarm_Fibaro_Scene" already exists
Error: near line 14: PRIMARY KEY must be unique
Error: near line 44: PRIMARY KEY must be unique
Error: near line 63: PRIMARY KEY must be unique
Error: near line 74: PRIMARY KEY must be unique
Error: near line 93: PRIMARY KEY must be unique
Error: near line 104: PRIMARY KEY must be unique
Error: near line 112: columns lang, key are not unique
Error: near line 113: columns lang, key are not unique
Error: near line 114: columns lang, key are not unique
Error: near line 115: columns lang, key are not unique
Error: near line 116: columns lang, key are not unique
Error: near line 117: columns lang, key are not unique
Error: near line 118: columns lang, key are not unique
Error: near line 119: columns lang, key are not unique
Error: near line 120: columns lang, key are not unique
Error: near line 121: columns lang, key are not unique
Error: near line 122: columns lang, key are not unique
Error: near line 123: columns lang, key are not unique
Error: near line 124: columns lang, key are not unique
Error: near line 125: columns lang, key are not unique
Error: near line 126: columns lang, key are not unique
Error: near line 127: columns lang, key are not unique
Error: near line 128: columns lang, key are not unique
Error: near line 129: columns lang, key are not unique
Error: near line 130: columns lang, key are not unique
Error: near line 131: columns lang, key are not unique
Error: near line 132: columns lang, key are not unique
Error: near line 133: columns lang, key are not unique
Error: near line 134: columns lang, key are not unique
Error: near line 135: columns lang, key are not unique
FILE: sql/HC_Data.sql
Error: near line 1: duplicate column name: batteryLowNotification
Error: near line 2: duplicate column name: defaultTemperatureSensor
Error: near line 3: duplicate column name: defaultHumiditySensor
Error: near line 4: duplicate column name: defaultLightSensor
Error: near line 5: duplicate column name: fireAlarmTemperature
Error: near line 6: duplicate column name: freezeAlarmTemperature
Error: near line 7: duplicate column name: smsManagement
FILE: sql/HC_Location.sql
Error: near line 1: duplicate column name: decimalMark
FILE: sql/LastChange.sql
Error: near line 1: table "Last_Change" already exists
FILE: sql/Lili.sql
Error: near line 4: duplicate column name: liliStartCommand
Error: near line 5: duplicate column name: liliStopCommand
FILE: sql/LogTranslation.sql
FILE: sql/Log_Type.sql
Error: near line 88: PRIMARY KEY must be unique
FILE: sql/NEW_Device_History.sql
Error: near line 1: table "NEW_Device_History" already exists
Error: near line 2: index NEW_Device_History_timestamp already exists
Error: near line 4: duplicate column name: propertyName
FILE: sql/NEW_Device.sql
Error: near line 1: duplicate column name: Device_Type
Error: near line 2: duplicate column name: Enabled
Error: near line 3: duplicate column name: Visible
Error: near line 4: duplicate column name: Parent_Id
Error: near line 252: no such table: TMP_NEW_Device
FILE: sql/NEW_Energy_History.sql
Error: near line 1: table "NEW_Energy_History" already exists
Error: near line 9: index NEW_Energy_History_deviceId_timeTo_timeFrom already exists
FILE: sql/NEW_Installed_Plugins.sql
Error: near line 1: table "NEW_Installed_Plugins" already exists
Error: near line 4: index NEW_Installed_Plugins_pluginName already exists
FILE: sql/NEW_Power_History.sql
Error: near line 1: table "NEW_Power_History" already exists
Error: near line 9: table NEW_Power_History has no column named timeTo
FILE: sql/NEW_Scene_Killable.sql
Error: near line 1: duplicate column name: Killable
FILE: sql/NEW_Scene_Visible.sql
Error: near line 1: duplicate column name: Visible
FILE: sql/NEW_Smoke_History.sql
Error: near line 1: table "NEW_Smoke_History" already exists
Error: near line 9: table NEW_Smoke_History has no column named timeTo
FILE: sql/NEW_Socket.sql
FILE: sql/NEW_Temperature_History.sql
Error: near line 1: table "NEW_Temperature_History" already exists
Error: near line 9: table NEW_Temperature_History has no column named timeTo
FILE: sql/NEW_Zwave_Company.sql
FILE: sql/notification_center.sql
FILE: sql/N_Virtual_Device_Icon.sql
FILE: sql/Parent_ID.sql
FILE: sql/pluginsChanges.sql
Error: near line 1: duplicate column name: Enabled
Error: near line 2: duplicate column name: Visible
Error: near line 3: duplicate column name: Parent_Id
Error: near line 5: table "NEW_Internal" already exists
Error: near line 9: index NEW_Internal_Device_Id already exists
Error: near line 11: table "NEW_Interface" already exists
FILE: sql/ProtectedByPin.sql
Error: near line 1: duplicate column name: protectedByPin
FILE: sql/Read_Changes.sql
Error: near line 1: table "Read_Changes" already exists
FILE: sql/Remote_Gateway.sql
Error: near line 1: duplicate column name: Remote_Gateway_Id
Error: near line 3: table RemoteGateway already exists
Error: near line 6: table RemoteGatewayDevice already exists
Error: near line 9: duplicate column name: remotePin
FILE: sql/RGBProgram.sql
Error: near line 4: table "RGBProgram" already exists
Error: near line 10: table "RGBProgram_Step" already exists
FILE: sql/Scene_Icon.sql
FILE: sql/Sort_Orders.sql
Error: near line 1: table "Mobile_Scenes_Sort_Order" already exists
Error: near line 8: table "Mobile_Rooms_Sort_Order" already exists
Error: near line 15: table "Mobile_Devices_Sort_Order" already exists
Error: near line 21: table "Sort_Order" already exists
Error: near line 28: table "Sort_Order_Mobile" already exists
FILE: sql/TemperatureUnit.sql
Error: near line 1: duplicate column name: temperatureUnit
FILE: sql/templates.sql
FILE: sql/timeDateFormat.sql
Error: near line 1: duplicate column name: timeFormat
Error: near line 2: duplicate column name: dateFormat
FILE: sql/tours.sql
Error: near line 1: table Tour already exists
Error: near line 7: table Tour_Prop already exists
FILE: sql/user_right_drop_tables.sql
FILE: sql/v4otherChanges.sql
Error: near line 7: columns Device_Id, Name are not unique
FILE: sql/windUnit.sql
Error: near line 1: duplicate column name: windUnit
FILE: sql/ZwaveReconfigurationService.sql
Error: near line 1: table "ZwaveReconfigurationService" already exists
FILE: sql/zwave_settings.sql
14|properties||0|""|0
Copying etc ...
Copying opt ...
Copying usr ...
cp: cannot stat `/var/www/fibaro/icons/User*': No such file or directory
Copying var ...
PHP Warning:  PHP Startup: Unable to load dynamic library '/usr/lib/php5/20090626+lfs/oauth.so' - /usr/lib/php5/20090626+lfs/oauth.so: cannot open shared object file: No such file or directory in Unknown on line 0
PHP Warning:  PHP Startup: Unable to load dynamic library '/usr/lib/php5/20090626+lfs/mysql.so' - libmysqlclient_r.so.16: cannot open shared object file: No such file or directory in Unknown on line 0
PHP Warning:  PHP Startup: Unable to load dynamic library '/usr/lib/php5/20090626+lfs/mysqli.so' - libmysqlclient_r.so.16: cannot open shared object file: No such file or directory in Unknown on line 0
PHP Warning:  PHP Startup: Unable to load dynamic library '/usr/lib/php5/20090626+lfs/pdo_mysql.so' - libmysqlclient_r.so.16: cannot open shared object file: No such file or directory in Unknown on line 0
Unexpected error: Value named 'associationView' couldn't be found in given internal data.
zwaveDevices

  • Upvote 1
Lien vers le commentaire
Partager sur d’autres sites

Et moi qui pensais que je n'étais pas un super développeur.

En fait, y a pire :(

 

C'est moche de mélanger le camel case et le snake case dans les noms de fichiers.

à‡a ne devrait pas être permis de faire passer ça en "prod". Nous on se fait jeter par le release manager.

Lien vers le commentaire
Partager sur d’autres sites

Je pense vraiment que ce n'est pas nouveau.

Au contraire, je dirais même que c'est moins pire qu'avant, car depuis 1 ou 2 versions, le script de mise à  jour effectue beaucoup plus de vérifications qu'il ne le faisait avant. Donc c'est positif car y'a du mieux, mais c'est pas encore ça :/

 

Sinon, si tu fais bien une sauvegarde avant la mise à  jour, et que le checksum de ta clé recovery est OK, tu pourras toujours revenir en arrière si la mise à  jour est un échec.

Lien vers le commentaire
Partager sur d’autres sites

Euh, pour moi, outre le tout nouveau process de migration depuis la V3 (qui ne concerne plus grand monde.... SebDel si tu passes par là  ;) ), la méga grosse nouveauté c'est ça !

 

Devices with multiple endpoint are now building correctly even without templates

 

Si c'est vrai, on pourra utiliser tous les modules, mêmes ceux qui ne sont pas du tout reconnus à  l'heure actuelle.

Lien vers le commentaire
Partager sur d’autres sites

En fait, il est connu depuis longtemps que les modules de type "plusieurs-en-un" sont mal reconnus par la HC2.

 

Exemple de module "simple" : relai simple, dimmer simple

Exemple de module "plusieurs-en-un" : relai double avec mesure de consommation, oeil de sauron, tous les modules Qubino, la plupart des modules Aeon Labs, etc

 

Donc si j'interprète bien cette phrase, les nouveaux modules qui sortent et qui intègrent plusieurs fonctionnalités seront correctement reconnus et directement utilisables dans la HC2, même sans template.

Le template ne servant qu'à  appliquer les paramètres (n°1, n°2, etc), c'est pas indispensable. D'autant plus que l'interface de la HC2 permet de forcer manuellement un paramètre donné si on en connait le numéro (généralement indiqué dans la doc du module).

 

Donc ça serait l'évolution ultime qui permet d'utiliser immédiatement n'importe quel nouveau module du marché.

 

A voir....

Lien vers le commentaire
Partager sur d’autres sites

Merci Lazer ça serait vraiment top en effet!! en attendant la reconfig (soft ou full) de mes switchs aeon qui étaient sans template ne se fait pas et impossible d'avorter le process. Idem après reboot, je vais essayer demain d'exclure les modules qui posent problème, ils sont encastrés et je n'ai plus le courage.

Bonne soirée àtous et àdemain pour de nouvelles aventures

Lien vers le commentaire
Partager sur d’autres sites

×
×
  • Créer...