![]() |
Official 5.3 Beta Discussion Thread - Printable Version +- Charmed Quark Systems, Ltd. - Support Forums and Community (https://www.charmedquark.com/vb_forums) +-- Forum: General Discussion (https://www.charmedquark.com/vb_forums/forumdisplay.php?fid=3) +--- Forum: Beta Discussions (https://www.charmedquark.com/vb_forums/forumdisplay.php?fid=12) +--- Thread: Official 5.3 Beta Discussion Thread (/showthread.php?tid=10397) |
RE: Official 5.3 Beta Discussion Thread - potts.mike - 04-09-2018 Dean, I noticed that the zwave appliance are showing as light switches for the semantic type. Is that intentional? When can we expect the Motion sensors I sent over to work? RE: Official 5.3 Beta Discussion Thread - Dean Roddey - 04-09-2018 Which specific ones are we talking about? I just added the Eco 2.0 PIR and Aeotec ZW-100 just now, plus a number of others. RE: Official 5.3 Beta Discussion Thread - potts.mike - 04-09-2018 Those would be them. I assume IÔÇÖll need to upgrade? RE: Official 5.3 Beta Discussion Thread - Dean Roddey - 04-09-2018 Yeh, in a bit here when I get 907 uploaded. RE: Official 5.3 Beta Discussion Thread - Dean Roddey - 04-09-2018 OK, 5.2.907 is posted, with yet more Z-Wave unit type support. Thermostat support is all but done, but there aren't any to test with yet. But I wanted to get it worked out since it is one of the more complex ones, and it did drive some necessary changes. RE: Official 5.3 Beta Discussion Thread - batwater - 04-09-2018 Hi Dean, Just installed .907, one of my Yale locks showed up correctly x07 but x06 which is an identical lock is showing up as a Cooper┬áRF9540-NAW ???? ┬á ┬á ┬á ┬á Name: Unit_6 ┬á ┬á ┬á ┬á ┬á Id: 6 ┬á ┬á ┬áDevType: Routing Slave ┬á ┬á ┬áGenType: EntryCtrl ┬á ┬á SpecType: 3 ┬á ┬á ┬á ┬á Make: Cooper ┬á ┬á ┬á ┬áModel: RF9540-NAW ┬á ┬á ┬á ┬áFlags: Beaming FreqListen┬á ┬á ┬á ┬á ManIds: 129 2 0 ┬á ┬á CppClass: TDimmerUnit ┬á ┬á Classes:┬á ┬á ┬á ┬á ┬á ┬á ┬á ┬á Association (1) ┬á ┬á ┬á ┬á ┬á ┬á ┬á Config (1) ┬á ┬á ┬á ┬á ┬á ┬á ┬á ManSpec (1) ┬á ┬á ┬á ┬á ┬á ┬á ┬á MLSwitch (1) ┬á ┬á ┬á ┬á ┬á ┬á ┬á Naming (1) ┬á ┬á ┬á ┬á ┬á ┬á ┬á Notification (1) ┬á ┬á ┬á ┬á ┬á ┬á ┬á PowerLev (1) ┬á ┬á ┬á ┬á ┬á ┬á ┬á SceneAct (1) ┬á ┬á ┬á ┬á ┬á ┬á ┬á SceneActConf (1) ┬á ┬á ┬á ┬á ┬á ┬á ┬á SwitchAll (1) ┬á ┬á ┬á ┬á ┬á ┬á ┬á Version (1) Extra Info:┬á ┬á ┬á ┬á ┬á IOType=ReadWrite ┬á ┬á ┬á ┬á ┬áDimCC=MLSwitch ┬á ┬á ┬á SwitchCC=MLSwitch How do you want to diagnose this?┬á I did not delete anything just loaded the new version of the code. -Ben RE: Official 5.3 Beta Discussion Thread - Dean Roddey - 04-09-2018 That has to be some sort of one off, or index vs. id thing. I'll look at it. In the meantime, force it to rescan (drop down menu for that unit) and see if it picks it up right. If so, then the one off thing has to be happening during the initial scan on start up or something. The fact that the one that's wrong is one value off short it argues for that as well. RE: Official 5.3 Beta Discussion Thread - batwater - 04-10-2018 Yup, rescan corrected the issue RE: Official 5.3 Beta Discussion Thread - Dean Roddey - 04-10-2018 Have you actually tried using any of this stuff, just through the raw driver monitor tab is fine, to see if things correctly respond to field writes, and that the field updates in response to changes made at the device? RE: Official 5.3 Beta Discussion Thread - batwater - 04-10-2018 I just was able to lock / unlock one of my Yale locks, state change was reflected.┬á┬á Bug note: Driver field unit name is not reflected from unit name change in Client side driver, neither the Lock true/false or the battery field reflect a name change. Where do I get the the message from the lock, e.g. which user code was used to unlock the lock?┬á Both are capabilities of the VRC0P Z-Wave driver. I was able to turn the Fibaro RGBW on and off.┬á Haven't tried yet to change the color... |