Cant get a smartthings sensor setup

[lorenjz]

I have several smartThings multipurpose sensors that I was successful in connecting to HomeSeer via deconz and a cronbee 2. There is one however that no matter what I try, it won't show the open/close feature within the device. I've reset it and removed it from both HomeSeer and deconz several times without any luck. Also there is some sort of issue that it has kept the name "Front Door" for some features and not others. Attached are two pictures of what I am talking about:

[w.vuyk]

Trying to wrap my head around this, am I understanding that the first image is showing a device that is how it should be defined and the second is the problem device that is missing the open/close device as well as having the name issue?
TBH I did not know there was a device combining both the vibration and open close functions

Could you send me a verbose logging perhaps? Follow these steps:

1. Set verbose logging and log to file in the settings of the plugin
2. Stop the plugin and remove the faulty device from the HS4 device list
3. restart the plugin once, so I can see the start in the logging
4. Let the plugin run until it creates the device from scratch
5. Then disable the verbose logging and log to file options again.
6. Locate the log "JowiHue.log" in the \Logs subdirectory of the HS4 installation directory.

Send the log to jowihue at ziggo dot nl?

Thanks,

Wim

[bdickhaus]

I have one of these too (on my HS3 system) but I have not had the time to get all the information together. I was not able to use it in the location I was hoping to, so for now it is just sitting here not being used. Let me know if I can help. There is also a separate device "Vibration Sensor" that gets created every time JowiHue starts, I delete them after I get about 10 of them, but they keep getting created

[w.vuyk]

Bill,

Do you still have the extra vibration sensor devices created with the latest HS3 version (2.1.1.4) of the plugin? I changed a lot in the device recognition part in the plugin, and one that I solved was the creation of the vibration sensor as a orphan device?

I am waiting for lorenjz to send the log based on post #2 so I can see what is happening here. But if you got the time for it a log from you would be nice as well (starting with HS4 version)

Thanks,

Wim

[lorenjz]

Sorry I had a couple of things pop up. Ill try and get this to you later today.

Sent from my SM-G988U using Tapatalk

[lorenjz]

Just sent the log. Let me know if there is anything else that I can do to help.

Thank you!

[bdickhaus]

Bill,

Do you still have the extra vibration sensor devices created with the latest HS3 version (2.1.1.4) of the plugin? I changed a lot in the device recognition part in the plugin, and one that I solved was the creation of the vibration sensor as a orphan device?

Wim,

Yes, still creating the orphan device in 2.1.1.4. I have the log saved and some screen captures. I do not have access to my HS4 system right now. The Internet provider at that location is no longer providing the service that I had, so I have no connectivity there and no immediate plans to get any. If I can find some time I have a spare RPi that I can build as an HS4 test system (it is actually the backup hardware in case my main HS3 system fails but I have never needed it) I have that third deCONZ system that I can use.

That reminds me. There is a button or check box (forget which one) to ignore a discovered bridge, but it does not work.

There is another "feature" that I would like to request that you not do it. I will explain in my email. That is in the trace as well. I am very busy with life events at the moment so it could be a couple of days before I put the package together. But I did capture the log.

Bill