Aller au contenu

V4.033 Hot Fix - 05-02-2015


Moicphil

Messages recommandés

Mise à  jour V 4.033

 

 

This version is hot fixing version addressing some of issues reported by users.

 
4.033 Hotfix
 
Resolved Issues:
 
#0001820: Cannot modify (edit) device group in scene if a device has been removed from system
#0001965: Device group list selection behaves erratically
#0002234: sceneActivation doesn't trigger with Zwave.me KeyFob in 4.022
#0002249, #0002542, #0002631: Unable to change multiple user settings (Done)
#0002281: Virtual Device Slider
#0002285: NothQ Gas Meter not configured
#0002288: HC2 Craches when deleting custom RGBW program
#0002289: Alarm Go Crazy
#0002328: Magic Scenes don't save parameters...only default ones
#0002523: v4.031 - Fibaro FGRM-221/222 - Venetian mode - Lamellas button
#0002584: Fibaro Motion Sensor stops turning associated lights on/of
#0002741: Plugin Dimmer - BeNext [bEN_PlDi]
 
Occasionally Error 400 after hidding plugin
 
Saving Magic Scenes - spinning circle when Fibaro Alarm triggered.
 
Many minor fixes
 
 
Known issues:
After the update clearing browser cache could be required
Power Mettering may not work properly for some devices
UBS Temperature is not visivble on iPhone/iPad client
RGBW Controler may not work propery when used in in/out mode
Alarm Panel doesn't work in some specific configurations
 
Plugins for TV Sets of various manufacturers may not work with its newes firmware due to restricions provided by new devices firmware. There will be added detalied information about suported firmwave versions within plugins.
 
-
Satel - adding plugin progress bar disappears during configuration. Please wait about 15 minutes before performing actions on Satel devices.
Devices Polling may not work properly - devices state in UI may be refreshed only after action taken.
Breached sensor with Arm Delay causes instant alarm after being armed
Data range selection in event panel doesn't work properly
Devices imported via Gateway Connection may have no icons
Gateway Connection status of dead device between master and slave controller may be different
Devices not properly configured on 3.X may not be converted properly
Reconfiguration may not work properly in some cases
On mobile clients devices may be visible in different categories than configured
Advanced settings for some imported devices may not work properly
Horstmann Thermostat HRT4-ZW higher battery usage in some cases
Doorlocks - some functions may not work properly
Lack of decimal mark in Event Panel
  • Upvote 1
Lien vers le commentaire
Partager sur d’autres sites

@Nico, j’espère que c'est effectivement corrigé car j' ai passé pas mal de temps avec le support en faisant des démos: marche / marche pas :rolleyes:.

Je croise les doigts, verdict demain matin !

 

@Phil, pour le RGBW je suis persuadé que c'est juste une propriété qui dérange l' UI puisque l'export json de l' API retourne bien un power à  0 et un value aussi à  0, pourtant mon bandeau est sur ON.

Lien vers le commentaire
Partager sur d’autres sites

@krikroff oui on verra bien dans 3h moi ca doit planté vers 20h20 :D

 

@Sakkhho la danfoss que je n'arrive pas a inclure retour SAV depuis 2 jours (je ne pense pas que cela venait de la v4 car impossible a inclure sous toutes les versions ni avec ma clef zwave

je viens de tester celle qui me pose probléme lorsque que je l'inclus toujours pareil

(une fois inclus ma Danfoss ne régule plus elle reste en position fermée alors qu elle fonction très bien si non inclus)

Lien vers le commentaire
Partager sur d’autres sites

J'avais pas vu cela avant c'est nouveau ?

 

Download device's template

 

post-374-0-87470300-1423161132_thumb.jpg

 

 

quand on ouvre le fichier on obtient cela Fichier XML

<?xml version="1.0" encoding="UTF-8"?>

-<Zwave xsi:noNamespaceSchemaLocation="http://production-server.fibaro.com/xml/Zwave.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:vc="http://www.w3.org/2007/XMLSchema-versioning" version="10">


-<zwaveData>

<basicClass>04</basicClass>

<manufacturerID>0000</manufacturerID>

<productType>0000</productType>

<productID>0000</productID>

<zLibraryType>00</zLibraryType>

<zProtocolVersion>00</zProtocolVersion>

<zProtocolSubVersion>00</zProtocolSubVersion>

<applicationVersion>00</applicationVersion>

<applicationSubVersion>00</applicationSubVersion>

<routing>true</routing>

<flirs>false</flirs>

</zwaveData>


-<deviceInfo>

<country/>

<company>Vision Security</company>

<brand/>

<productName/>

<productLine/>

<descriptionInclude/>

<description/>

</deviceInfo>


-<endPoint>


-<endPointID visible="true" enabled="true" id="0">

<genericClass>20</genericClass>

<specificClass>1</specificClass>

<typeFibaro>com.fibaro.motionSensor</typeFibaro>


-<interfacesFibaro>

<interface>battery</interface>

<interface>zwaveWakeup</interface>

<interface>battery</interface>

<interface>zwaveWakeup</interface>

</interfacesFibaro>


-<interfaces>

<interface>BinarySensor</interface>

<interface>Association</interface>

<interface>Battery</interface>

<interface>Basic</interface>

</interfaces>


-<commandClasses>


-<commandClass cmdClass="COMMAND_CLASS_BASIC">


-<valueHashes>


-<value type="byte" index="1">

<name>value</name>

<typeFibaro/>

<interfaceFibaro/>

<max>255</max>

<min>0</min>

<virtual>0</virtual>

</value>

</valueHashes>

</commandClass>


-<commandClass cmdClass="COMMAND_CLASS_SENSOR_BINARY">


-<valueHashes>


-<value type="bool" index="1">

<name>value</name>

<typeFibaro/>

<interfaceFibaro/>

<virtual>0</virtual>

</value>

</valueHashes>

</commandClass>


-<commandClass version="2" cmdClass="COMMAND_CLASS_ALARM">


-<valueHashes>


-<value type="byte" index="100">

<name>alarmType</name>

<typeFibaro/>

<interfaceFibaro>zwaveAlarm</interfaceFibaro>

<max>255</max>

<min>0</min>

<virtual>0</virtual>

</value>


-<value type="byte" index="101">

<name>alarmLevel</name>

<typeFibaro/>

<interfaceFibaro>zwaveAlarm</interfaceFibaro>

<max>255</max>

<min>0</min>

<virtual>0</virtual>

</value>

</valueHashes>

</commandClass>


-<commandClass cmdClass="COMMAND_CLASS_MANUFACTURER_SPECIFIC">

<valueHashes/>

</commandClass>


-<commandClass cmdClass="COMMAND_CLASS_BATTERY">


-<valueHashes>


-<value type="byte" index="1">

<name>batteryLevel</name>

<typeFibaro/>

<interfaceFibaro>battery</interfaceFibaro>

<max>255</max>

<min>0</min>

<virtual>0</virtual>

</value>

</valueHashes>

</commandClass>


-<commandClass version="2" cmdClass="COMMAND_CLASS_WAKE_UP">


-<valueHashes>


-<value type="int" index="1">

<name>wakeUpTime</name>

<typeFibaro/>

<interfaceFibaro>zwaveWakeup</interfaceFibaro>

<max>-1</max>

<min>0</min>

<virtual>0</virtual>

</value>

</valueHashes>

</commandClass>


-<commandClass cmdClass="COMMAND_CLASS_ASSOCIATION">


-<cmdCAssociation>


-<associationGroup setAuto="true" maxNode="5" number="1">


-<description>

<lang tr="EN"/>

</description>

</associationGroup>

</cmdCAssociation>


-<valueHashes>


-<value type="association" index="1">

<name>associationView</name>

<typeFibaro/>

<interfaceFibaro>zwaveAssociation</interfaceFibaro>

<max>255</max>

<virtual>0</virtual>

</value>


-<value type="int" index="2">

<name>associationGroups</name>

<typeFibaro/>

<interfaceFibaro>zwaveAssociation</interfaceFibaro>

<max>-1</max>

<min>0</min>

<virtual>0</virtual>

</value>

</valueHashes>

</commandClass>


-<commandClass cmdClass="COMMAND_CLASS_VERSION">

<valueHashes/>

</commandClass>

</commandClasses>

</endPointID>

</endPoint>

</Zwave>

 

 

Lien vers le commentaire
Partager sur d’autres sites

×
×
  • Créer...