You mention imperihome as having issues.
Does that mean that it is still correctly displayed inside PulseStation itself?
Just to narrow the investigation.
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 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 😉
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.
