Imperihome – FIBARO FGSD002 Smoke Sensor

Domotica gratuit Forums Report a bug Imperihome – FIBARO FGSD002 Smoke Sensor

Mots-clés : 

Ce sujet a 5 réponses, 3 participants et a été mis à jour par  Pat, il y a 1 an et 7 mois.

6 sujets de 1 à 6 (sur un total de 6)
  • Auteur
    Messages
  • #1785

    Pat
    Participant

    Hi all,

    Since few weeks, the Imperihome service do not recognize my FGSD002 Smoke Sensor.

    At the beginning, the json code was :

    “id”: “zwave-10”,
    “name”: “”,
    “location”: “”,
    “type”: “Routing Slave”,
    “manufacturer”: “FIBARO System”,
    “product”: “FGSD002 Smoke Sensor”,
    “status”: “Probe1”,
    “values”: …

    Now, this is :

    “id”: “zwave-10”,
    “name”: “”,
    “location”: “”,
    “type”: “Notification Sensor”,
    “manufacturer”: “”,
    “product”: “”,
    “status”: “Probe”,
    “values”: …

    Now, the smoke sensor is not connected and does not work with PulseStation.

    More over, the device’s properties are not loaded by default for the property “DevSmoke” and “DevTemperature”.

    Could you help me please ?

    kr

    Patrice.

    #1789

    K.Rens
    Admin bbPress

    You mention imperihome as having issues.
    Does that mean that it is still correctly displayed inside PulseStation itself?
    Just to narrow the investigation.

    Kind regards,
    K.Rens

    #1793
    Mika
    Mika
    Admin bbPress

    I think that it comes with the new release of the zwave serive…
    I already correct that issue.
    I’ll release the service soon…

    #1865

    Pat
    Participant

    Hi,

    To be clearer, I have 2 mistakes:

    The first one on the Imperihome service (after an update), it’s not realy an issue but it’s still a improvment for me. The properties are not loaded with the correct properties, meaning the FGSD002 is not recognized as a routing slave for the properties DevSmoke” and “DevTemperature”. I think that the default value are not loaded with this requirements. If this properties are not automaticcaly loaded, after each release, I have to right the “property” device in the 2 service properties.

    The second one on the zwave service, since the last update and the reset of conf ; my smoke sensor is recognized as a notification sensor instead of a routing slave (the previous conf). PulseStation detects the device, but I can not display it in Pulsestation nor Imperihome.

    I hope to be clearer.

    Many thanks.

    KR Pat

    #1956
    Mika
    Mika
    Admin bbPress

    I updated the openzwave library so this is because you device change from “Routing Slave” to “Notification”.
    I adapted the imperihome service, have to make a relaese 😉

    #1985

    Pat
    Participant

    Hi,

    I’m ok for the imperihome service, but not for the zwave service. I still have one properties instead of many properties ? The only property is wait time… That’s why I said that the device is not regnozied by zwave service.

    Have you got an idea ?

    BR.
    Patrice.

6 sujets de 1 à 6 (sur un total de 6)

Vous devez être connecté pour répondre à ce sujet.