Comme annoncé, ce forum est passé en lecture seule au 1er janvier 2020. Désormais nous vous invitons à vous rendre sur notre nouvelle page communauté :
Image

A très bientôt !

Smart Implant de Fibaro (FGBS-222): configuration ?

Pour parler de tout, et surtout de rien !
cyril
Timide
Messages : 22
Inscription : 02 sept. 2015, 17:29

Re: Smart Implant de Fibaro (FGBS-222): configuration ?

Message par cyril » 10 sept. 2019, 14:30

maxredphenix a écrit :
24 juin 2019, 21:44
Bonjour à tous,

Je viens de recevoir mes smart-implants, est-ce que quelqu'un a réussi à les configurer correctement car pour le moment ce n'est toujours pas reconnu :(

Il est inclu avec la derniere mise a jour du plugin Zwave, il est inclu



Quelqu'un a t'il fait la config avec un THD22, je n'ai aucun retour du capteur
Cyril

Jeedom sur RPI4

biarnes64
Timide
Messages : 176
Inscription : 05 août 2016, 15:17
Localisation : Pau

Re: Smart Implant de Fibaro (FGBS-222): configuration ?

Message par biarnes64 » 10 sept. 2019, 15:22

cyril a écrit :
10 sept. 2019, 14:30


Il est inclu avec la derniere mise a jour du plugin Zwave, il est inclu
Bonne nouvelle !!!

Avatar de l’utilisateur
maxredphenix
Actif
Messages : 539
Inscription : 18 sept. 2015, 21:36
Localisation : Bourgogne

Re: Smart Implant de Fibaro (FGBS-222): configuration ?

Message par maxredphenix » 10 sept. 2019, 18:46

Génial !!!!
DIY Intel NUC i5 7Gen(via Proxmox) - Jeedom 3.2.

IPX800 v4 + 2 modules X-4FP
Détecteur fuite d'eau + fumée fibaro
Divers modules Zwave

Avatar de l’utilisateur
maxredphenix
Actif
Messages : 539
Inscription : 18 sept. 2015, 21:36
Localisation : Bourgogne

Re: Smart Implant de Fibaro (FGBS-222): configuration ?

Message par maxredphenix » 10 sept. 2019, 21:41

Bon je ne comprends pas trop, mais la MAJ ne change rien.
Le module n'est toujours pas reconnu correctement, je n'ai que 2 commandes de créées à l'inclusion.

J'ai :
- Mis à jour le plugin
- Réinstallé les dépendances
- Au cas ou dans Général / Options avancées j'ai refait une synchro des configs modules

Au niveau des LOG OpenZWave_update :

Code : Tout sélectionner

: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin:
Fetched 1504 kB in 1s (1457 kB/s)
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 66308 files and directories currently installed.)
Preparing to unpack .../libudev-dev_232-25+deb9u12_amd64.deb ...
Unpacking libudev-dev:amd64 (232-25+deb9u12) over (232-25+deb9u11) ...
Preparing to unpack .../udev_232-25+deb9u12_amd64.deb ...
Unpacking udev (232-25+deb9u12) over (232-25+deb9u11) ...
Preparing to unpack .../libudev1_232-25+deb9u12_amd64.deb ...
Unpacking libudev1:amd64 (232-25+deb9u12) over (232-25+deb9u11) ...
Setting up libudev1:amd64 (232-25+deb9u12) ...
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 66308 files and directories currently installed.)
Preparing to unpack .../unzip_6.0-21+deb9u2_amd64.deb ...
Unpacking unzip (6.0-21+deb9u2) over (6.0-21+deb9u1) ...
Processing triggers for mime-support (3.60) ...
Setting up unzip (6.0-21+deb9u2) ...
Processing triggers for libc-bin (2.24-11+deb9u4) ...
Setting up udev (232-25+deb9u12) ...
addgroup: The group `input' already exists as a system group. Exiting.
update-initramfs: deferring update (trigger activated)
Processing triggers for systemd (232-25+deb9u11) ...
Processing triggers for man-db (2.7.6.1-2) ...
Setting up libudev-dev:amd64 (232-25+deb9u12) ...
Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-4.9.0-9-amd64
Installation des dependances Python
DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7.
Requirement already satisfied: urwid in /usr/local/lib/python2.7/dist-packages (2.0.1)
WARNING: You are using pip version 19.1.1, however version 19.2.3 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7.
Requirement already satisfied: louie in /usr/lib/python2.7/dist-packages (1.1)
Requirement already satisfied: nose>=0.8.3 in /usr/lib/python2.7/dist-packages (from louie) (1.3.7)
WARNING: You are using pip version 19.1.1, however version 19.2.3 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7.
Requirement already satisfied: six in /usr/lib/python2.7/dist-packages (1.10.0)
WARNING: You are using pip version 19.1.1, however version 19.2.3 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7.
Requirement already satisfied: tornado in /usr/local/lib/python2.7/dist-packages (5.1.1)
Requirement already satisfied: singledispatch in /usr/local/lib/python2.7/dist-packages (from tornado) (3.4.0.3)
Requirement already satisfied: futures in /usr/local/lib/python2.7/dist-packages (from tornado) (3.2.0)
Requirement already satisfied: backports-abc>=0.4 in /usr/local/lib/python2.7/dist-packages (from tornado) (0.5)
Requirement already satisfied: six in /usr/lib/python2.7/dist-packages (from singledispatch->tornado) (1.10.0)
WARNING: You are using pip version 19.1.1, however version 19.2.3 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
mkdir: cannot create directory '/opt': File exists
Désinstallation de la version précédente
Installation de Python-OpenZwave
DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7.
ERROR: Cannot uninstall 'Cython'. It is a distutils installed project and thus we cannot accurately determine which files belong to it which would lead to only a partial uninstall.
apt-get install --force-yes -y cython
Reading package lists...
Building dependency tree...
Reading state information...
cython is already the newest version (0.25.2-1).
0 upgraded, 0 newly installed, 0 to remove and 49 not upgraded.
Installing dependencies for python : 2 7 13
apt-get install --force-yes -y python-pip python-dev python-docutils python-setuptools python-louie
Reading package lists...
Building dependency tree...
Reading state information...
python-louie is already the newest version (1.1-2.1).
python-dev is already the newest version (2.7.13-2).
python-docutils is already the newest version (0.13.1+dfsg-2).
python-pip is already the newest version (9.0.1-2+deb9u1).
python-setuptools is already the newest version (33.1.1-1).
0 upgraded, 0 newly installed, 0 to remove and 49 not upgraded.
apt-get install --force-yes -y build-essential libudev-dev g++
Reading package lists...
Building dependency tree...
Reading state information...
build-essential is already the newest version (12.3).
g++ is already the newest version (4:6.3.0-4).
libudev-dev is already the newest version (232-25+deb9u12).
0 upgraded, 0 newly installed, 0 to remove and 49 not upgraded.
apt-get install --force-yes -y cython
Reading package lists...
Building dependency tree...
Reading state information...
cython is already the newest version (0.25.2-1).
0 upgraded, 0 newly installed, 0 to remove and 49 not upgraded.
pip install nose-html
DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7.
Requirement already satisfied: nose-html in /usr/local/lib/python2.7/dist-packages (1.1)
Requirement already satisfied: nose>=0.11.1 in /usr/lib/python2.7/dist-packages (from nose-html) (1.3.7)
WARNING: You are using pip version 19.1.1, however version 19.2.3 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
pip install nose-progressive
DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7.
Requirement already satisfied: nose-progressive in /usr/local/lib/python2.7/dist-packages (1.5.2)
Requirement already satisfied: nose>=1.2.1 in /usr/lib/python2.7/dist-packages (from nose-progressive) (1.3.7)
Requirement already satisfied: blessings<2.0,>=1.3 in /usr/local/lib/python2.7/dist-packages (from nose-progressive) (1.7)
Requirement already satisfied: six in /usr/lib/python2.7/dist-packages (from blessings<2.0,>=1.3->nose-progressive) (1.10.0)
WARNING: You are using pip version 19.1.1, however version 19.2.3 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
pip install coverage
DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7.
Requirement already satisfied: coverage in /usr/local/lib/python2.7/dist-packages (4.5.2)
WARNING: You are using pip version 19.1.1, however version 19.2.3 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
pip install nose
DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7.
Requirement already satisfied: nose in /usr/lib/python2.7/dist-packages (1.3.7)
WARNING: You are using pip version 19.1.1, however version 19.2.3 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
pip install pylint
DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7.
Requirement already satisfied: pylint in /usr/local/lib/python2.7/dist-packages (1.9.4)
Requirement already satisfied: six in /usr/lib/python2.7/dist-packages (from pylint) (1.10.0)
Requirement already satisfied: mccabe in /usr/local/lib/python2.7/dist-packages (from pylint) (0.6.1)
Requirement already satisfied: astroid<2.0,>=1.6 in /usr/local/lib/python2.7/dist-packages (from pylint) (1.6.5)
Requirement already satisfied: singledispatch; python_version < "3.4" in /usr/local/lib/python2.7/dist-packages (from pylint) (3.4.0.3)
Requirement already satisfied: isort>=4.2.5 in /usr/local/lib/python2.7/dist-packages (from pylint) (4.3.4)
Requirement already satisfied: configparser; python_version == "2.7" in /usr/local/lib/python2.7/dist-packages (from pylint) (3.5.0)
Requirement already satisfied: backports.functools-lru-cache; python_version == "2.7" in /usr/local/lib/python2.7/dist-packages (from pylint) (1.5)
Requirement already satisfied: enum34>=1.1.3; python_version < "3.4" in /usr/lib/python2.7/dist-packages (from astroid<2.0,>=1.6->pylint) (1.1.6)
Requirement already satisfied: lazy-object-proxy in /usr/local/lib/python2.7/dist-packages (from astroid<2.0,>=1.6->pylint) (1.3.1)
Requirement already satisfied: wrapt in /usr/local/lib/python2.7/dist-packages (from astroid<2.0,>=1.6->pylint) (1.10.11)
Requirement already satisfied: futures in /usr/local/lib/python2.7/dist-packages (from isort>=4.2.5->pylint) (3.2.0)
WARNING: You are using pip version 19.1.1, however version 19.2.3 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
#pip install docutils
#pip install setuptools
#The following line crashes with a core dump
#pip install "Cython==0.22"
Dependencies for users installed (python 2 7 13)
sed -i -e '253s/.*//' openzwave/cpp/src/value_classes/ValueID.h
cd openzwave && make
make[1]: Entering directory '/opt/python-openzwave/openzwave'
CPPFLAGS= make -C /opt/python-openzwave/openzwave/cpp/build/ -w
make[2]: Entering directory '/opt/python-openzwave/openzwave/cpp/build'
Building OpenZWave Version 1.4.-1
Building tinystr.o
Building tinyxmlerror.o
Building tinyxml.o
Building tinyxmlparser.o
Building hid.o
Building aeskey.o
Building aescrypt.o
Building aestab.o
Building aes_modes.o
Building SensorAlarm.o
Building Proprietary.o
Building ClimateControlSchedule.o
Building SensorBinary.o
Building Language.o
Building MultiChannelAssociation.o
Building NoOperation.o
Building ZWavePlusInfo.o
Building Indicator.o
Building SoundSwitch.o
Building MultiInstance.o
Building MeterPulse.o
Building DoorLockLogging.o
Building ThermostatFanMode.o
Building Color.o
Building Basic.o
Building Clock.o
Building Configuration.o
Building SwitchToggleBinary.o
Building Hail.o
Building ThermostatMode.o
Building SwitchMultilevel.o
Building UserCode.o
Building TimeParameters.o
Building BarrierOperator.o
Building Lock.o
Building ApplicationStatus.o
Building SwitchToggleMultilevel.o
Building NodeNaming.o
Building DoorLock.o
Building WakeUp.o
Building ManufacturerProprietary.o
Building BasicWindowCovering.o
Building SwitchAll.o
Building MultiCmd.o
Building Association.o
Building ManufacturerSpecific.o
Building SceneActivation.o
Building CentralScene.o
Building Powerlevel.o
Building ThermostatFanState.o
Building Meter.o
Building AssociationCommandConfiguration.o
Building SensorMultilevel.o
Building ThermostatOperatingState.o
Building Battery.o
Building CRC16Encap.o
Building DeviceResetLocally.o
Building Version.o
Building Alarm.o
Building CommandClasses.o
Building ThermostatSetpoint.o
Building Security.o
Building EnergyProduction.o
Building CommandClass.o
Building ControllerReplication.o
Building Protection.o
Building SwitchBinary.o
Building Value.o
Building ValueList.o
Building ValueButton.o
Building ValueInt.o
Building ValueStore.o
Building ValueDecimal.o
Building ValueRaw.o
Building ValueString.o
Building ValueByte.o
Building ValueBool.o
Building ValueSchedule.o
Building ValueShort.o
Building Controller.o
Building Wait.o
Building Thread.o
Building Stream.o
Building Log.o
Building HidController.o
Building Mutex.o
Building SerialController.o
Building Event.o
Building FileOps.o
Building TimeStamp.o
Building FileOpsImpl.o
Building TimeStampImpl.o
Building WaitImpl.o
Building ThreadImpl.o
Building LogImpl.o
Building MutexImpl.o
Building SerialControllerImpl.o
Building EventImpl.o
Building Options.o
Building Scene.o
Building Utils.o
Building Driver.o
Building ZWSecurity.o
Building Group.o
Building Node.o
Building Manager.o
Building Msg.o
Building Notification.o
Creating vers.cpp
Building vers.o
Linking Static Library
Linking Shared Library
Making ozw_config file
make[2]: Leaving directory '/opt/python-openzwave/openzwave/cpp/build'
CPPFLAGS= make -C /opt/python-openzwave/openzwave/cpp/examples/MinOZW/ -w
make[2]: Entering directory '/opt/python-openzwave/openzwave/cpp/examples/MinOZW'
Building Main.o
Linking /opt/python-openzwave/openzwave/.lib/MinOZW
g++   -o /opt/python-openzwave/openzwave/.lib/MinOZW /opt/python-openzwave/openzwave/.lib/Main.o /opt/python-openzwave/openzwave/libopenzwave.so -pthread
Creating Temporary Shell Launch Script
make[2]: Leaving directory '/opt/python-openzwave/openzwave/cpp/examples/MinOZW'
make[1]: Leaving directory '/opt/python-openzwave/openzwave'
python setup-lib.py build
running build
running build_ext
cythoning src-lib/libopenzwave/libopenzwave.pyx to src-lib/libopenzwave/libopenzwave.cpp
building 'libopenzwave' extension
creating build
creating build/temp.linux-x86_64-2.7
creating build/temp.linux-x86_64-2.7/src-lib
creating build/temp.linux-x86_64-2.7/src-lib/libopenzwave
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g -fdebug-prefix-map=/build/python2.7-2.7.13=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -DPY_SSIZE_T_CLEAN=1 -Iopenzwave/cpp/src/ -Iopenzwave/cpp/src/value_classes/ -Iopenzwave/cpp/src/platform/ -Iopenzwave/cpp/build/linux/ -I/usr/include/python2.7 -c src-lib/libopenzwave/libopenzwave.cpp -o build/temp.linux-x86_64-2.7/src-lib/libopenzwave/libopenzwave.o
cc1plus: warning: command line option '-Wstrict-prototypes' is valid for C/ObjC but not for C++
src-lib/libopenzwave/libopenzwave.cpp:3:0: warning: "PY_SSIZE_T_CLEAN" redefined
#define PY_SSIZE_T_CLEAN
<command-line>:0:0: note: this is the location of the previous definition
In file included from openzwave/cpp/src/aes/aescpp.h:26:0,
from openzwave/cpp/src/Driver.h:42,
from src-lib/libopenzwave/libopenzwave.cpp:459:
openzwave/cpp/src/aes/aes.h:75:0: warning: ignoring #pragma warning  [-Wunknown-pragmas]
#pragma warning( disable : 4324 )
openzwave/cpp/src/aes/aes.h:93:0: warning: ignoring #pragma warning  [-Wunknown-pragmas]
#pragma warning( default : 4324 )
src-lib/libopenzwave/libopenzwave.cpp: In function 'PyObject* __pyx_pf_12libopenzwave_9PyManager_268beginControllerCommand(__pyx_obj_12libopenzwave_PyManager*, PyObject*, PyObject*, PyObject*, PyObject*, PyObject*, PyObject*)':
src-lib/libopenzwave/libopenzwave.cpp:29891:204: warning: 'bool OpenZWave::Manager::BeginControllerCommand(uint32, OpenZWave::Driver::ControllerCommand, OpenZWave::Driver::pfnControllerCallback_t, void*, bool, uint8, uint8)' is deprecated [-Wdeprecated-declarations]
__pyx_t_6 = __Pyx_PyBool_FromLong(__pyx_v_self->manager->BeginControllerCommand(__pyx_t_1, __pyx_t_2, __pyx_f_12libopenzwave_ctrl_callback, ((void *)__pyx_v_pythonfunc), __pyx_t_3, __pyx_t_4, __pyx_t_5)); if (unlikely(!__pyx_t_6)) __PYX_ERR(0, 4120, __pyx_L1_error)
^
src-lib/libopenzwave/libopenzwave.cpp:545:36: note: in definition of macro '__Pyx_PyBool_FromLong'
#define __Pyx_PyBool_FromLong(b) ((b) ? __Pyx_NewRef(Py_True) : __Pyx_NewRef(Py_False))
^
In file included from src-lib/libopenzwave/libopenzwave.cpp:464:0:
openzwave/cpp/src/Manager.h:1731:19: note: declared here
DEPRECATED bool BeginControllerCommand( uint32 const _homeId, Driver::ControllerCommand _command, Driver::pfnControllerCallback_t _callback = NULL, void* _context = NULL, bool _highPower = false, uint8 _nodeId = 0xff, uint8 _arg = 0 );
^~~~~~~~~~~~~~~~~~~~~~
creating build/lib.linux-x86_64-2.7
x86_64-linux-gnu-g++ -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-z,relro -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -Wdate-time -D_FORTIFY_SOURCE=2 -g -fdebug-prefix-map=/build/python2.7-2.7.13=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -Wdate-time -D_FORTIFY_SOURCE=2 -g -fdebug-prefix-map=/build/python2.7-2.7.13=. -fstack-protector-strong -Wformat -Werror=format-security build/temp.linux-x86_64-2.7/src-lib/libopenzwave/libopenzwave.o openzwave/libopenzwave.a -ludev -lstdc++ -o build/lib.linux-x86_64-2.7/libopenzwave.so
python setup-lib.py install
running install
running bdist_egg
running egg_info
creating src-lib/libopenzwave.egg-info
writing requirements to src-lib/libopenzwave.egg-info/requires.txt
writing src-lib/libopenzwave.egg-info/PKG-INFO
writing top-level names to src-lib/libopenzwave.egg-info/top_level.txt
writing dependency_links to src-lib/libopenzwave.egg-info/dependency_links.txt
writing manifest file 'src-lib/libopenzwave.egg-info/SOURCES.txt'
reading manifest file 'src-lib/libopenzwave.egg-info/SOURCES.txt'
writing manifest file 'src-lib/libopenzwave.egg-info/SOURCES.txt'
installing library code to build/bdist.linux-x86_64/egg
running install_lib
running build_ext
skipping 'src-lib/libopenzwave/libopenzwave.cpp' Cython extension (up-to-date)
creating build/bdist.linux-x86_64
creating build/bdist.linux-x86_64/egg
copying build/lib.linux-x86_64-2.7/libopenzwave.so -> build/bdist.linux-x86_64/egg
creating stub loader for libopenzwave.so
byte-compiling build/bdist.linux-x86_64/egg/libopenzwave.py to libopenzwave.pyc
installing package data to build/bdist.linux-x86_64/egg
running install_data
creating build/bdist.linux-x86_64/egg/config
creating build/bdist.linux-x86_64/egg/EGG-INFO
copying src-lib/libopenzwave.egg-info/PKG-INFO -> build/bdist.linux-x86_64/egg/EGG-INFO
copying src-lib/libopenzwave.egg-info/SOURCES.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying src-lib/libopenzwave.egg-info/dependency_links.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying src-lib/libopenzwave.egg-info/not-zip-safe -> build/bdist.linux-x86_64/egg/EGG-INFO
copying src-lib/libopenzwave.egg-info/requires.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying src-lib/libopenzwave.egg-info/top_level.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
writing build/bdist.linux-x86_64/egg/EGG-INFO/native_libs.txt
creating dist
creating 'dist/libopenzwave-0.3.1-py2.7-linux-x86_64.egg' and adding 'build/bdist.linux-x86_64/egg' to it
removing 'build/bdist.linux-x86_64/egg' (and everything under it)
Processing libopenzwave-0.3.1-py2.7-linux-x86_64.egg
creating /usr/local/lib/python2.7/dist-packages/libopenzwave-0.3.1-py2.7-linux-x86_64.egg
Extracting libopenzwave-0.3.1-py2.7-linux-x86_64.egg to /usr/local/lib/python2.7/dist-packages
Adding libopenzwave 0.3.1 to easy-install.pth file
Installed /usr/local/lib/python2.7/dist-packages/libopenzwave-0.3.1-py2.7-linux-x86_64.egg
Processing dependencies for libopenzwave==0.3.1
Searching for six==1.10.0
Best match: six 1.10.0
Adding six 1.10.0 to easy-install.pth file
Using /usr/lib/python2.7/dist-packages
Finished processing dependencies for libopenzwave==0.3.1
Installation of lib finished.
python setup-api.py install
running install
running bdist_egg
running egg_info
creating src-api/openzwave.egg-info
writing requirements to src-api/openzwave.egg-info/requires.txt
writing src-api/openzwave.egg-info/PKG-INFO
writing top-level names to src-api/openzwave.egg-info/top_level.txt
writing dependency_links to src-api/openzwave.egg-info/dependency_links.txt
writing manifest file 'src-api/openzwave.egg-info/SOURCES.txt'
reading manifest file 'src-api/openzwave.egg-info/SOURCES.txt'
writing manifest file 'src-api/openzwave.egg-info/SOURCES.txt'
installing library code to build/bdist.linux-x86_64/egg
running install_lib
running build_py
creating build/lib.linux-x86_64-2.7/openzwave
copying src-api/openzwave/node.py -> build/lib.linux-x86_64-2.7/openzwave
copying src-api/openzwave/value.py -> build/lib.linux-x86_64-2.7/openzwave
copying src-api/openzwave/scene.py -> build/lib.linux-x86_64-2.7/openzwave
copying src-api/openzwave/singleton.py -> build/lib.linux-x86_64-2.7/openzwave
copying src-api/openzwave/object.py -> build/lib.linux-x86_64-2.7/openzwave
copying src-api/openzwave/command.py -> build/lib.linux-x86_64-2.7/openzwave
copying src-api/openzwave/controller.py -> build/lib.linux-x86_64-2.7/openzwave
copying src-api/openzwave/__init__.py -> build/lib.linux-x86_64-2.7/openzwave
copying src-api/openzwave/group.py -> build/lib.linux-x86_64-2.7/openzwave
copying src-api/openzwave/network.py -> build/lib.linux-x86_64-2.7/openzwave
copying src-api/openzwave/option.py -> build/lib.linux-x86_64-2.7/openzwave
creating build/bdist.linux-x86_64/egg
creating build/bdist.linux-x86_64/egg/openzwave
copying build/lib.linux-x86_64-2.7/openzwave/node.py -> build/bdist.linux-x86_64/egg/openzwave
copying build/lib.linux-x86_64-2.7/openzwave/value.py -> build/bdist.linux-x86_64/egg/openzwave
copying build/lib.linux-x86_64-2.7/openzwave/scene.py -> build/bdist.linux-x86_64/egg/openzwave
copying build/lib.linux-x86_64-2.7/openzwave/singleton.py -> build/bdist.linux-x86_64/egg/openzwave
copying build/lib.linux-x86_64-2.7/openzwave/object.py -> build/bdist.linux-x86_64/egg/openzwave
copying build/lib.linux-x86_64-2.7/openzwave/command.py -> build/bdist.linux-x86_64/egg/openzwave
copying build/lib.linux-x86_64-2.7/openzwave/controller.py -> build/bdist.linux-x86_64/egg/openzwave
copying build/lib.linux-x86_64-2.7/openzwave/__init__.py -> build/bdist.linux-x86_64/egg/openzwave
copying build/lib.linux-x86_64-2.7/openzwave/group.py -> build/bdist.linux-x86_64/egg/openzwave
copying build/lib.linux-x86_64-2.7/openzwave/network.py -> build/bdist.linux-x86_64/egg/openzwave
copying build/lib.linux-x86_64-2.7/openzwave/option.py -> build/bdist.linux-x86_64/egg/openzwave
copying build/lib.linux-x86_64-2.7/libopenzwave.so -> build/bdist.linux-x86_64/egg
byte-compiling build/bdist.linux-x86_64/egg/openzwave/node.py to node.pyc
byte-compiling build/bdist.linux-x86_64/egg/openzwave/value.py to value.pyc
byte-compiling build/bdist.linux-x86_64/egg/openzwave/scene.py to scene.pyc
byte-compiling build/bdist.linux-x86_64/egg/openzwave/singleton.py to singleton.pyc
byte-compiling build/bdist.linux-x86_64/egg/openzwave/object.py to object.pyc
byte-compiling build/bdist.linux-x86_64/egg/openzwave/command.py to command.pyc
byte-compiling build/bdist.linux-x86_64/egg/openzwave/controller.py to controller.pyc
byte-compiling build/bdist.linux-x86_64/egg/openzwave/__init__.py to __init__.pyc
byte-compiling build/bdist.linux-x86_64/egg/openzwave/group.py to group.pyc
byte-compiling build/bdist.linux-x86_64/egg/openzwave/network.py to network.pyc
byte-compiling build/bdist.linux-x86_64/egg/openzwave/option.py to option.pyc
creating build/bdist.linux-x86_64/egg/EGG-INFO
copying src-api/openzwave.egg-info/PKG-INFO -> build/bdist.linux-x86_64/egg/EGG-INFO
copying src-api/openzwave.egg-info/SOURCES.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying src-api/openzwave.egg-info/dependency_links.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying src-api/openzwave.egg-info/not-zip-safe -> build/bdist.linux-x86_64/egg/EGG-INFO
copying src-api/openzwave.egg-info/requires.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying src-api/openzwave.egg-info/top_level.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
writing build/bdist.linux-x86_64/egg/EGG-INFO/native_libs.txt
creating 'dist/openzwave-0.3.1-py2.7.egg' and adding 'build/bdist.linux-x86_64/egg' to it
removing 'build/bdist.linux-x86_64/egg' (and everything under it)
Processing openzwave-0.3.1-py2.7.egg
creating /usr/local/lib/python2.7/dist-packages/openzwave-0.3.1-py2.7.egg
Extracting openzwave-0.3.1-py2.7.egg to /usr/local/lib/python2.7/dist-packages
Adding openzwave 0.3.1 to easy-install.pth file
Installed /usr/local/lib/python2.7/dist-packages/openzwave-0.3.1-py2.7.egg
Processing dependencies for openzwave==0.3.1
Searching for libopenzwave==0.3.1
Best match: libopenzwave 0.3.1
Processing libopenzwave-0.3.1-py2.7-linux-x86_64.egg
libopenzwave 0.3.1 is already the active version in easy-install.pth
Using /usr/local/lib/python2.7/dist-packages/libopenzwave-0.3.1-py2.7-linux-x86_64.egg
Searching for Louie==1.1
Best match: Louie 1.1
Adding Louie 1.1 to easy-install.pth file
Using /usr/lib/python2.7/dist-packages
Searching for six==1.10.0
Best match: six 1.10.0
Adding six 1.10.0 to easy-install.pth file
Using /usr/lib/python2.7/dist-packages
Searching for nose==1.3.7
Best match: nose 1.3.7
Adding nose 1.3.7 to easy-install.pth file
Installing nosetests script to /usr/local/bin
Installing nosetests-2.7 script to /usr/local/bin
Using /usr/lib/python2.7/dist-packages
Finished processing dependencies for openzwave==0.3.1
Installation of API finished.
Everything is successfully installed!
D'ailleurs l'erreur "pip install --upgrade pip' command" impacte la MAJ ?
DIY Intel NUC i5 7Gen(via Proxmox) - Jeedom 3.2.

IPX800 v4 + 2 modules X-4FP
Détecteur fuite d'eau + fumée fibaro
Divers modules Zwave

Idaho947
Actif
Messages : 1281
Inscription : 30 mai 2017, 21:36

Re: Smart Implant de Fibaro (FGBS-222): configuration ?

Message par Idaho947 » 10 sept. 2019, 22:11

Tu a relancé l'installation des dépendances ?

Avatar de l’utilisateur
maxredphenix
Actif
Messages : 539
Inscription : 18 sept. 2015, 21:36
Localisation : Bourgogne

Re: Smart Implant de Fibaro (FGBS-222): configuration ?

Message par maxredphenix » 10 sept. 2019, 22:12

En fait, c'est bon tout est reconnu. J'ai redémarré le plugin et... tout est OK.
DIY Intel NUC i5 7Gen(via Proxmox) - Jeedom 3.2.

IPX800 v4 + 2 modules X-4FP
Détecteur fuite d'eau + fumée fibaro
Divers modules Zwave

Avatar de l’utilisateur
maxredphenix
Actif
Messages : 539
Inscription : 18 sept. 2015, 21:36
Localisation : Bourgogne

Re: Smart Implant de Fibaro (FGBS-222): configuration ?

Message par maxredphenix » 10 sept. 2019, 22:14

Une personne a déjà fait le test avec plusieurs sondes de température ?
J'ai mis un DS18BD20, la température est trop haute (31 °C au lieu de 15 réel) mais ça affiche quelque chose.
Par contre lorsque je mets 2 sondes... la 2eme n'est pas reconnue.
DIY Intel NUC i5 7Gen(via Proxmox) - Jeedom 3.2.

IPX800 v4 + 2 modules X-4FP
Détecteur fuite d'eau + fumée fibaro
Divers modules Zwave

Avatar de l’utilisateur
mich0111
Timide
Messages : 460
Inscription : 25 juin 2019, 13:59

Re: Smart Implant de Fibaro (FGBS-222): configuration ?

Message par mich0111 » 10 sept. 2019, 22:52

Bonsoir,
As-tu fait l'inclusion ave les 2 sondes déjà branchées ?
C'est obligatoire pour que les 2 soient reconnues.
Jeedom V4 DIY
RPI3B+
SSD
RFXCOM version XL
Contrôleur Z-Wave Z-stick Gen5
CronBee2
Et plus de 70 devices de toutes marques et toutes natures

Avatar de l’utilisateur
maxredphenix
Actif
Messages : 539
Inscription : 18 sept. 2015, 21:36
Localisation : Bourgogne

Re: Smart Implant de Fibaro (FGBS-222): configuration ?

Message par maxredphenix » 11 sept. 2019, 06:21

Ah non, je vais tenter ce soir du coup.
Merci
DIY Intel NUC i5 7Gen(via Proxmox) - Jeedom 3.2.

IPX800 v4 + 2 modules X-4FP
Détecteur fuite d'eau + fumée fibaro
Divers modules Zwave

iquid
Timide
Messages : 36
Inscription : 09 sept. 2014, 20:56

Re: Smart Implant de Fibaro (FGBS-222): configuration ?

Message par iquid » 13 sept. 2019, 18:01

Je tente de le configurer pour mon portail coulissant Somfy.
J'ai relier l'input 1 avec le détecteur d'ouverture et l'output 1 avec la commande d'ouverture du portail, mais rien ne se passe, j'avoue être un peu perdu dans les réglages... car rien ne se passe, comment passe-t-on d'un ON . OFF à un actionneur ?

arnog23
Timide
Messages : 428
Inscription : 02 mars 2016, 21:50

Re: Smart Implant de Fibaro (FGBS-222): configuration ?

Message par arnog23 » 13 sept. 2019, 22:29

Bonsoir,

As tu bien configuré le mode de protection pour séparer les entrées des sorties.

À quel valeur as tu mis le paramètre 20 ? Il faut le passer à Normally closed ou Normally open dans ton cas je pense.

Loutre38
Timide
Messages : 8
Inscription : 01 juin 2019, 13:16

Re: Smart Implant de Fibaro (FGBS-222): configuration ?

Message par Loutre38 » 15 sept. 2019, 20:49

Bonsoir,
J'ai branché 1 sonde DS18B20 sur le fgbs-222 puis procédé à l'inclusion. j'ai bien une température (température 2, classe : 49, instance : 3 , index : 1), mais qui ne correspond pas à la réalité (32,4°c d’affiché, dans la pièce il fait moins de 26°C), c'est peut être la sonde interne ?
Faut-il rajouter une résistance de tirage de 4,7 kΩ (raccordé sur le + et le DATA) ?

J'ai mise hors tension le FGBS et branché une 2ème sonde, toujours le même problème.

Ps : j'ai fait le mise à jour du openzwave 10/09 mais pas celle du 12/09.

Merci pour votre aide.
Pièces jointes
Capture2.JPG
Capture2.JPG (37.97 Kio) Consulté 1527 fois
Capture.JPG
Capture.JPG (202.27 Kio) Consulté 1527 fois
pi 3 b+ Z-Wave+ Z-Stick GEN5
Vision ZM1602+ PST02-A 4 in 1 + hank HKZW-DWS01 x2 + Aeotec ZW116 x2 + FGBS-222 DS18B20x2 + DSM 213 + surveillance station + Foscam R4M
Jeedom

iquid
Timide
Messages : 36
Inscription : 09 sept. 2014, 20:56

Re: Smart Implant de Fibaro (FGBS-222): configuration ?

Message par iquid » 18 sept. 2019, 11:23

arnog23 a écrit :
13 sept. 2019, 22:29
Bonsoir,

As tu bien configuré le mode de protection pour séparer les entrées des sorties.

À quel valeur as tu mis le paramètre 20 ? Il faut le passer à Normally closed ou Normally open dans ton cas je pense.
Merci , je ne trouve pas le paramètre de protection dont tu parles pour séparer entrée / sortie ?

justmi
Timide
Messages : 54
Inscription : 02 nov. 2017, 15:11

Re: Smart Implant de Fibaro (FGBS-222): configuration ?

Message par justmi » 20 sept. 2019, 12:07

Bonjour,

je viens de brancher le mien.

Mon idée c'est de le brancher au portier Konx a la place du bouton poussoir mais je n'arrive pas a configurer la sortir 1 en impulsion de fois il se passe un truc mis je ne sais pas comment.

J'essai de modifier les paramètres mais c'est mieux de faire attention quand même la dedans. Si quelqu'un sait je suis preneur.
cdt

justmi
Timide
Messages : 54
Inscription : 02 nov. 2017, 15:11

Re: Smart Implant de Fibaro (FGBS-222): configuration ?

Message par justmi » 25 sept. 2019, 19:08

j'essai également d'avoir les information de l'entrée 1 mais rien pourtant j'ai bien désactiver la protection.

j'ai un interrupteur qui a 3,7V et quand j'appuis il passe a 0.

je voulais se retour d'état en 0 ou 1 pour domotiser le bouton d'appel du konx

justmi
Timide
Messages : 54
Inscription : 02 nov. 2017, 15:11

Re: Smart Implant de Fibaro (FGBS-222): configuration ?

Message par justmi » 03 nov. 2019, 18:55

justmi a écrit :
25 sept. 2019, 19:08
j'essai également d'avoir les information de l'entrée 1 mais rien pourtant j'ai bien désactiver la protection.

j'ai un interrupteur qui a 3,7V et quand j'appuis il passe a 0.

je voulais se retour d'état en 0 ou 1 pour domotiser le bouton d'appel du konx
Bonjour,


J'ai réussi a récupérer le retour d'information de mon bouton poussoir du Konx.

J'ai branché 2 fils sur mon poussoir raccordé en IN1 et GND du smart implant. Grace à cela, je peux etre informé des l'appuis sur le bouton pour ensuite déclenché des scénario (photo, pushbullet...)

Par contre j'ai toujours mon problème initial.

Je veux piloter ma gâche électrique depuis les sortie out1 ou out2. alimentation 12V + 1 bouton + 1 gâche. Schéma pas compliqué en soit mais impossible d’implanté une sortie du smart pour piloter la gâche.

Chiki
Timide
Messages : 8
Inscription : 17 mars 2019, 03:57

Re: Smart Implant de Fibaro (FGBS-222): configuration ?

Message par Chiki » 19 nov. 2019, 10:54

bonjour tout le monde :mrgreen: :mrgreen:

pour moi meme problème je n 'arrive pas a faire fonctionner les deux sorties
je met bien la protection sur "no opperation possible"
j arrive a allumer la premiere led sur la sortie 1
mais rien ne se passe avec la sortie 2 je n 'arrive rien à faire comment tester si celle-ci fonctionne bien ??

pourtant je gère bien la sortie 1 une idée ???? :D

arnog23
Timide
Messages : 428
Inscription : 02 mars 2016, 21:50

Re: Smart Implant de Fibaro (FGBS-222): configuration ?

Message par arnog23 » 19 nov. 2019, 23:01

Bonsoir,

As tu le mode qui apparaît deux fois dans les paramètres. Une fois pour chaque entrée/sortie ?

Cela m’est arrivée lors d’une inclusion que seul le mode de protection pour l’entrée/sortie1 apparaisse et pas pour l’entree/sortie 2.

Après exclusion/inclusion, je voyais bien les deux.

Mike88200
Timide
Messages : 16
Inscription : 08 déc. 2017, 20:08

Re: Smart Implant de Fibaro (FGBS-222): configuration ?

Message par Mike88200 » 24 déc. 2019, 09:39

Bonjour,
Voila j'ai un souci.
je voulais m'en servir juste comme sonde de température dans mes pièces.
Car au mois il y a pas de souci de pile et avec les oregon problème de remonter d'information.
J'ai installé une sonde cela fonctionne, mais des que j'en mais deux et plus celle ci ne fonctionne plus. pour info je l'exclu et refait l'inclusion a chaque fois. j'avais l'ancienne version mais cela ne change pas.
Merci

arnog23
Timide
Messages : 428
Inscription : 02 mars 2016, 21:50

Re: Smart Implant de Fibaro (FGBS-222): configuration ?

Message par arnog23 » 24 déc. 2019, 10:28

Bonjour,

Je n’ai pas testé avec plusieurs sonde de température mais il faudrait que tu nous en dise un peu plus.

Quel version d’OS (Jessie / Stretch / Buster), de Jeedom, du plugin openzwave, du module (5.1 ?), type d’inclusion (normal / sécurisée), ...

Répondre

Revenir vers « Discussions Générales »

Qui est en ligne ?

Utilisateurs parcourant ce forum : Aucun utilisateur inscrit et 3 invités