+- 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 - Dean Roddey - 01-15-2018
Didn't quite get a drop out today. I worked on more fixes and improvements and more on the Homeworks client side driver.
I also implemented the environmental variables support for WebRIVA. The IV system has nine special runtime values that can be set via environmental variables on each machine. The RIVA system allows RIVA clients to pass in values that they want their virtual IV engine to see, so I added that to the WebRIVA client. So they are in the form:
env1=xyz&env5=abc
and so forth, for 1 through 9. You can access these in any actions, and they allow you to implement per-client stuff in various ways.
RE: Official 5.3 Beta Discussion Thread - Dean Roddey - 01-18-2018
I've gotten back to the Z-Wave driver for a couple days. Having to be away from it a while was probably a good thing. I had time to think about it but not enough time to mess with it. So I had some good ideas to implement. I re-worked yet again the bit that handles management of msgs in and out and I won't get it back coherent until tomorrow.
But, I managed a significant reduction in complexity, assuming I'm not just fooling myself. That's the most Z-Wavey and fundamental bit of it, so having it right is important. This was one of those things were flipping the logic inside out works better. Strange how often that happens, one aspect of it seems the more important but you eventually realize that another is.
And I came up with a better scheme for how the driver waits for responses when it needs to do something synchronously (i.e. wait for the results right then.) There's an id in the sent msgs that comes back in some of the acknowledgements, but turns out if the send fails in some ways it had to be updated to a new value, so the driver thread doesn't know about these things since the re-sends are handled down in this msg I/O bit. So I created my own scheme with a nice way for the driver to unambiguously block waiting for a specific msg to be sent and acknowledged, even if other msgs are ahead of it in the queue. So it can know when its msg actually gets sent, and then wait a reasonable time for the reply. And that unique id also makes for a better way now to track in the trace log the back and forth related to a particular msg.
Anyhoo, I'm rambling, but some nice improvements.
RE: Official 5.3 Beta Discussion Thread - potts.mike - 01-19-2018
Dean,
What is your confidence in this new zwave driver serving as a secondary controller to smartthings? Since moving in December IÔÇÖve been using smartthings for the ease of setup but more advanced programming is harder to do.
Along those lines a wizard for creating triggered and scheduled events would go a long way towards simplifying CQC.
RE: Official 5.3 Beta Discussion Thread - Dean Roddey - 01-19-2018
It is designed as a secondary controller scheme, so it should work with any valid master controller.
RE: Official 5.3 Beta Discussion Thread - batwater - 01-19-2018
(01-19-2018, 09:11 AM)potts.mike Wrote: Dean,
What is your confidence in this new zwave driver serving as a secondary controller to smartthings? Since moving in December IÔÇÖve been using smartthings for the ease of setup but more advanced programming is harder to do.
I'm doing this now ST primary, VRC0P secondary.  All my actions are handled by CQC, not ST, no logic on ST. Happy with ST and ability to add community device drivers.
RE: Official 5.3 Beta Discussion Thread - IVB - 01-19-2018
(01-19-2018, 11:03 AM)batwater Wrote:(01-19-2018, 09:11 AM)potts.mike Wrote: Dean,
What is your confidence in this new zwave driver serving as a secondary controller to smartthings? Since moving in December IÔÇÖve been using smartthings for the ease of setup but more advanced programming is harder to do.
I'm doing this now ST primary, VRC0P secondary.  All my actions are handled by CQC, not ST, no logic on ST. Happy with ST and ability to add community device drivers.
do you need to use the leviton software for this?
RE: Official 5.3 Beta Discussion Thread - jkmonroe - 01-19-2018
(01-19-2018, 01:53 PM)IVB Wrote:(01-19-2018, 11:03 AM)batwater Wrote:(01-19-2018, 09:11 AM)potts.mike Wrote: Dean,
What is your confidence in this new zwave driver serving as a secondary controller to smartthings? Since moving in December IÔÇÖve been using smartthings for the ease of setup but more advanced programming is harder to do.
I'm doing this now ST primary, VRC0P secondary.  All my actions are handled by CQC, not ST, no logic on ST. Happy with ST and ability to add community device drivers.
do you need to use the leviton software for this?
Dude, you were on the SmartThings<->VRC0P webinar with me and Ben.
Unless you're talking about the z-stick, in which case ignore me.  
RE: Official 5.3 Beta Discussion Thread - Dean Roddey - 01-19-2018
I just got a clean driver startup with the new changes. Dang, that's so much cleaner now that it automatically pings frequent listeners to wake them up. The trace log is clean, no retries.
RE: Official 5.3 Beta Discussion Thread - Dean Roddey - 01-19-2018
Oh well, I had my moment of false glory, then it all went straight to hell when I tried to start doing a replication and I've still not gotten it figured out yet.
RE: Official 5.3 Beta Discussion Thread - batwater - 01-20-2018
(01-19-2018, 02:58 PM)jkmonroe Wrote:(01-19-2018, 01:53 PM)IVB Wrote:(01-19-2018, 11:03 AM)batwater Wrote:(01-19-2018, 09:11 AM)potts.mike Wrote: Dean,
What is your confidence in this new zwave driver serving as a secondary controller to smartthings? Since moving in December IÔÇÖve been using smartthings for the ease of setup but more advanced programming is harder to do.
I'm doing this now ST primary, VRC0P secondary.  All my actions are handled by CQC, not ST, no logic on ST. Happy with ST and ability to add community device drivers.
do you need to use the leviton software for this?
Dude, you were on the SmartThings<->VRC0P webinar with me and Ben.
Unless you're talking about the z-stick, in which case ignore me.  
What he said ^^^  an NO Leviton software!!!  SmartThings Smart Phone app or their web site depending...