ericl78

oui tu as raison, donc mon idée était mauvaise et cela est donc impossible. Le mieux, tu dois utiliser ta hc3 pour communiquer avec Alexa et tu passes tes commandes de ta HC2 via API sur la HC3 pour déclencher Alexa. Ce que je fais depuis jeedom qui commande ma HC3 pour utiliser Alexa.

Bonsoir à tous Voilà, sur ma HC2, que j'ai décomissionné il y a un an, un programme existait afin de suivre les communication de nos modules zwave. Extremement pratique lorsqu'un module déconnait ! Sur la HC3, plus rien, voici ma question: Connaissez vous un logiciel d'analyse de trafic zwave (style wireshark) ? a utiliser sur pc ou mac Ou une autre solution ? J'ai 68 modules connectés sur ma HC3, et je voudrais vérifier le trafic avant d'avoir des problèmes. Merci à vous

Hi De mon coté, je pense que oui, mais tu dois créer deux comptes chez fibaro, un pour chaque HCx. Autrement, déjà essayé et commenté sur le forum, pas possible. A tester :=)

Hi all Mise à jour effectuée RAS PS: j'ai le plugin Eaton --> ras A plus

Hi Mise à jour effectuée RAS, ca tourne

Thank you for using our gateway! Be sure to update to the latest version to enjoy new features and improvements. Important Notices: This version focuses on system performance optimisation and fixes for existing features. Main features: 1. Performance Improvements Enhanced speed and responsiveness of the interface for better user experience. Removed storage of unnecessary data to save more system resources. 2. Bug Fixing Critical fixes for gateway connection feature. Resolved heating-related issues. What's new: Alarm Unlocked creating alarm zones for all types of binary sensors. Possibility of changing and setting custom icons for Satel outputs and zones. Dashboard Reduced time of loading device tiles. Loading subsequent items with scrolling. Devices Reduced time of loading device rows. Loading subsequent items with scrolling the list. More available icons based on device hierarchy. Possibility to disable saving of device energy to the database. Elero* Correct handling of the ongoing device pairing process. Regionalization of available features based on gateway frequency. Energy Comparing the same time periods on the Savings tab. Chart of savings since the date of installation. Interval for storing virtual energy measurement reduced to five minutes. More user-friendly installation cost removal. Gateway Connection Information that the gateway is ready to use as a slave. Information on incompatibility due to a different version of the Z-Wave engine. General Possibility of choosing more than one main energy meter. Nice* Regionalization of available features based on gateway frequency. Other Four new language versions of the recovery interface (DA, HU, LT, RU). Added missing translations for several language versions. Performance Removed storing the charts-related data into RAM. Reduced redundant requests to api. Bug fixes: Dashboard Unresponsive interface and long loading times for large systems. Quick App control view scrolls automatically after using the control. Devices Device after reconfiguration changes its name, ID, and room assignment (ZW3). Possibility of starting a few reconfiguration processes for one device (ZW3). Removing queued action of setting parameter if the device entered sleep mode (ZW3). Overriding the temperature set in heating schedule is not possible for FGT-001 (ZW3). No support for FIBARO Heat Controller error notifications (ZW3). No support for com.fibaro.hvacSystem device type (ZW3). Incorrect support for MCO MH10, MH-S31x, MH-S41x devices (ZW3). Thermostat in Auto mode added as linked device does not operate the switch correctly. Some endpoints belonging to multifunctional devices (e.g. thermostats) are missing. Virtual power metering value does not change after its editing. Configuration parameter value is not refreshed after resetting. No units for sensors connected to FIBARO Smart Implant. The device list scrolls automatically when switching tabs with its settings. Deleting all devices belonging to a linked device causes a system error. Incorrect default values of FIBARO Heat Controller configuration parameters. Some of the roller shutter icons are incorrectly mapped to the device state. Incorrect handling of power and temperature charts. Energy Sum of energy consumed by all devices is not calculated properly. In some cases, energy data stops being saved to the database. Gateway Connection No possibility to restore backup with previous software version. State of devices added to slave gateway does not update and gateway needs rebooting. Incorrect mapping of devices connected to FIBARO Smart Implant added to slave gateway. No possibility to configure virtual power metering for devices added to slave gateway. Incorrect support of FIBARO RGBW Controller added to slave gateway. No possibility to select category for devices added to slave gateway. Notifications Devices that are discharged or unavailable still trigger notifications. Other VoIP feature does not work. Outdated translations for several language versions. Performance Some systems experience significant delays in executing and reporting actions. Profiles Action assigned to the Quick App button does not start after switching the profile. Scenes Creating new global variable does not allow to use it in scenes. Known issues: Z-Wave Engine 3.0 Some Z-Wave devices are not fully compatible with the new version of Z-Wave engine. Gateway connection is not available in the new Z-Wave engine version. * - does not apply to HC3L (Home Center 3 Lite)

mise à jur effectuée RAS

oui 100% d'accord avec toi , voilà pour moi : (61 modules Zwave)

Bonsoir MAJ effectuée, beaucoup plus rapide, pour le reste cela semble OK

Bonsoinr à vous tous Je viens de commander la nouvelle version qui est à nouveau disponible. Le firmware est en version 2.0 et je posséde une HC3 firmware version 5.080.20 Et Oups, pas compatible, voici après l'inclusion ce que j'obtiens : ne regarder que le 366.X svp donc, rien de très bon. Avez vous constaté la même chose que moi, ou j'ai un problème ? Je pense que la version 2.0 du firmware de ce device n'est pas compatible HC3 . A vous lire. Bon week end

Bonjour à tous Je viens par curiosité de scanner les ports ouverts sur ma hc3, voici le résultat : 22,80,443,500,5060,5061,9999 Pour 22 SSH, 80 HTTP, 443 HTTPS, 500 peut être VPN avec Fibaro mais pour le reste, avez vous une idée de l'utilisation possible ? Merci

Mise à jour effectuée RAS à suivre

Merci

@Lazer Peux tu stp me traduire "PKO Smart Home program" Merci

Pour moi, elle est connectée en câble uniquement. Je préfère laisser tout le paramétrage wifi "VIDE" comme cela le problème ne m'affecte pas :=). Autrement, tu dois à chaque reboot fermer le wifi, pas pratique. Il y a dans le forum des scripts qui réalisent cette fonction. (A lancer au démarrage de ta boxe) cdlt