[quote=“Marc Shenker, post:108, topic:191115”][quote=“JDL, post:106, topic:191115”]We’ve just bought into Vera Plus because of the exciting prospect of using Zigbee, Z-Wave and 433 simultaneously. We’ve got a stock of Osram Lightify lamps and I was looking forward to creating scenes to demonstrate them. But nope: They won’t link to the Vera Plus.
Trying as generic Zigbee devices the Vera Plus reports that they’ve paired, but then errors because they cannot be configured.
Can Vera comment on the likely prospect of the Lightify Bulbs working with the Vera Plus. They pair very nicely with the Cozify Hub and with the Almond+ so they cannot have too many manufacturer specific aspects.[/quote]
We have not begun integrating the Lightify bulbs. I will pass your request onto the Device Integration Team.
ZigBee is not a plug and play platform in the way that Z-Wave is setup to be. Each device requires the equivalent to a driver be created for it to work on our platform.[/quote]
If ZigBee is not a plug and play platform for Vera then please, please allow developers/users to write our own ZigBee device profiles/drivers, similar to how Vera allows plugin development. This will solve this issue for both Vera and users.
ZigBee HA 1.2 certified devices use the the same predefined cluster IDs to report their various information (i.e. same cluster ID to report temperature data for example) so it’s just matter of creating and then assigning the correct JSON/XML to the ZigBee device, similar to how unknown/incorrectly identified Z-Wave devices sometimes requires the user to manually assign the correct JSON/XML device profiles to make it function properly.
SmartThings allows this and that’s one reason why so many developers can add nearly any kind of ZigBee/Zwave devices to it. Even non-certified ZigBee devices such as Xiaomi sensor/button/plug have been added and is working great (I have the button, which I use daily).
Please open up device profile development to developers/users.
It’s about six months since Mark mentioned looking into adding Lightify capability. Any updates? Also, would adding a lightify bulb to hue be a possible workaround?
Took a chance on the Visonic Window/Door Sensor (model MCT-340E). Zigbee HA1.2 compliant. They were very cheap, but listed as Samsung SmartThings only. They do work on Vera Plus, but there was a trick. Adding them as a generic zigbee device did nothing. The device would not pair after several attempts. I instead tried to pair it as a NYCE door window sensor. Vera recognized it was not that device, but paired it successfully. Have installed 2 so far and they’re working great.
Also bought the Bosch Motion Sensor (PIR w/Pet Immunity) model ISQ-ZPR1-WP13. Same deal. Would not recognize as a generic zigbee. Tried again as an NYCE motion sensor and again, Vera reported it was not that device, but then paired it successfully as a motion sensor. Also functioning properly so far.
[quote=“ListerD, post:124, topic:191115”]Took a chance on the Visonic Window/Door Sensor (model MCT-340E). Zigbee HA1.2 compliant. They were very cheap, but listed as Samsung SmartThings only. They do work on Vera Plus, but there was a trick. Adding them as a generic zigbee device did nothing. The device would not pair after several attempts. I instead tried to pair it as a NYCE door window sensor. Vera recognized it was not that device, but paired it successfully. Have installed 2 so far and they’re working great.
Also bought the Bosch Motion Sensor (PIR w/Pet Immunity) model ISQ-ZPR1-WP13. Same deal. Would not recognize as a generic zigbee. Tried again as an NYCE motion sensor and again, Vera reported it was not that device, but then paired it successfully as a motion sensor. Also functioning properly so far.[/quote]
I tried doing this exact thing and the Bosch motion is stuck endlessly “configuring”. Did yours do that as well? It will also disappear from the interface randomly while in this state, but Home-Assistant sees it completely fine…
I follow the advice of ListerD and paired a Visonic Window/Door Sensor (model MCT-340E). Zigbee HA1.2 compliant. At the beginning it displayed as a Smoke Sensor, but a few minutes later it change to a Window/Door Sensor. The only issue I have is that is not displaying the battery and its charge. Any suggestions?
Taken the battery out did not work. I have asked tech support, but so far no results.
I found in the Smartthings web page the complete plugin for the sensor. This is written in Groovy similar to Luua. Can this code be somehow modified to create a plugin for Vera? Here is the link
When will Vera support the Lutron Connected Bulb Remote and Cree Connected Bulbs? I just tried (several times) pairing each with VeraPlus 1.7.2935 and they both report Unable to Configure. (In case Vera is not aware, they both have worked flawlessly with Wink for years.)
I started with the Wink Hub and the Wink Connect app running on UI5. The main reason I bought the Wink was because it interfaced with Amazon Echo. There were so many problems I abandoned the Wink and took a different route: Raspberry Pi with the ha-bridge from GitHub. The ha-bridge is one of the nicest apps I have seen. It works flawlessly as an interface between Vera and Amazon Echo. It ran so well I then added a Harmony Hub to control my A/V system. That also runs well, with the exception of some Harmony problems getting out of synch with A/V devices because there is no feedback loop possible. My old Vera3 kept acting up so I installed a VeraPlus to replace it. As you probably know, that has been on the market well over a year and it still barely supports Zigbee and has a very buggy interface. But for some reason, most of us hang on to our venerable Vera machines…
I am one of those who still uses Vera with UI5 on my trusty Lite. A Wink 2 has recently bridged the void for ZigBee that my Vera Plus will likely never fill. My Plus should have been returned, but I held on to hope too long. Now it just collects dust.
The Wink Connect app is great for those of us who invested in ZigBee devices that never worked with Vera directly. My plan is to migrate away from Vera.
OSRAM has opened the API for Lightify for development of apps. The link to the website is: https://us.lightify-api.org . Does this information help in developing an app for vera? Hopefully someone with programing expertise could use this to develop an app.
Vera Support – I’ve added one of these to my UI7 V+, and am having the same issue. It sees the device, but no battery status, no open/close status, just an "ARM’ or “DISARM” choice. help?
Any update on Xiaomi ZigBee sensors support? I’d really love to have couple of their temp. sensors at my home. It costs almost nothing compared to similarly capable z-wave devices.
I’ve had luck recently with the SmartThings F-OUT-US-2 smart outlet/plug, their newest (V4?) of these smart plugs. It was on sale last week so I picked up a few. I added it as an “Appliance Module - Centralite Appliance Module 4257050-RZHAC” under “Dimmers and Lights”. Vera tried to add it as a smoke sensor, so I had to change the device_type to BinaryLight:1, the device_file to D_BinaryLight1.xml, the device_json to D_BinaryLight1.json, the category_num to 3, and the subcategory_num to 1. They all work fine* now and even report the watts being used, which Samsung doesn’t advertise as a feature.
*The only issue I’m having is that sometimes when the F-OUT-US-2 is on and another zigbee device is turned on or off, Vera reports that the F-OUT-US-2 turned off. The F-OUT-US-2 never ACTUALLY turns off, Vera just thinks it did for a few seconds and then corrects itself a few seconds later. The only issue this poses is that I had a scene in which when one device turns off (Christmas tree), two more turn off. Vera’s false reporting of the F-OUT-US-2 being turned off triggers the other two to actually turn off. So I had to alter that scene. But for basic control of a device on and off, and even reporting wattage, this thing is solid.
If anyone has any ideas on how to troubleshoot the one little issue, let me know. I’m wondering if there’s a setting somewhere to alter the polling or something so that it doesn’t do these false off reports anymore.
Vera Support – I’ve added one of these to my UI7 V+, and am having the same issue. It sees the device, but no battery status, no open/close status, just an "ARM’ or “DISARM” choice. help?
Sorry, been off the boards for a while. Mine show up perfectly with open/closed status. I did not have them initially show up as a smoke sensor. They showed up as a door/window sensor on the initial pairing. If you’re still having issues, you might remove the device and try it as another type of door/window sensor. Mine also shows as configured as the same type of devices you listed: DoorSensor:1
Also, I did create a modified json file just to switch the open/closed states, reversing the colors. My locks show red when locked, so I wanted my sensors to do the same. Red means closed or locked. But the status of opened/closed was working prior to that change.
Sengled Element Classic A19 bulbs work with vera plus. Just got two of them installed and worked like a champ. Shows up as urn:schemas-upnp-org:device:DimmableLight:1 Using minimotes for scene control of on/off and dimming.
Replaced a couple of TCPLighting bulbs I’ve been limping along with that were more trouble than they were worth.
[quote=“ListerD, post:139, topic:191115”]Sengled Element Classic A19 bulbs work with vera plus. Just got two of them installed and worked like a champ. Shows up as urn:schemas-upnp-org:device:DimmableLight:1 Using minimotes for scene control of on/off and dimming.
Replaced a couple of TCPLighting bulbs I’ve been limping along with that were more trouble than they were worth.[/quote]
Are you connecting the A19’s directly to Vera or using a hub with a plug-in?
