Charmed Quark Systems, Ltd. - Support Forums and Community
5.5 Beta Discussions 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: 5.5 Beta Discussions Thread (/showthread.php?tid=10858)

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30


RE: 5.5 Beta Discussions Thread - Dean Roddey - 09-02-2019

I need to get an external USB BD drive for the NUC to use for ripping discs I guess. Any good suggestions for that? And I guess MakeMVK is the obvious choice for Plex?


RE: 5.5 Beta Discussions Thread - Dean Roddey - 09-04-2019

I'm banging away for a new beta drop. I've been taking care of some fundamental C++ stuff lately and those changes (though very much a good thing for the future) have caused a few snafus that I've been chasing down.


RE: 5.5 Beta Discussions Thread - gReatAutomation - 09-04-2019

(09-04-2019, 02:57 PM)Dean Roddey Wrote: I'm banging away for a new beta drop. I've been taking care of some fundamental C++ stuff lately and those changes (though very much a good thing for the future) have caused a few snafus that I've been chasing down.

Ah, ye ole rabbit holes   Big Grin


RE: 5.5 Beta Discussions Thread - kblagron - 09-06-2019

This is a "nice to have", but on the AI "Explore Logs" display, the data is not displayed in any particular order that makes sense.  I would prefer chronologically, but at least on mine, I cannot tell how it is sorted on the initial display.  I always have to click the Time field at the top to see the latest log entries.


RE: 5.5 Beta Discussions Thread - Dean Roddey - 09-07-2019

Version 5.4.904 is posted. A lot of internal C++ plumbing improvements have been done, some of them working towards the longer term goal of adding Linux support. I've tested it quite a bit, but it's always possible I missed some bit here or there, so let me know if see anything that doesn't look right or isn't working right. I took care of good number of unrelated goobers that I ran across while doing that testing as well.


RE: 5.5 Beta Discussions Thread - gReatAutomation - 09-08-2019

Thanks and appreciate adding in the SMS busy field. Very helpful.


RE: 5.5 Beta Discussions Thread - Dean Roddey - 09-22-2019

I've been banging away at testing for a new drop. With all of the fairly fundamental changes I've been making I've had to do a lot more than usual and have found various things I've needed to go back and tweak. Hopefully I'm fairly close to getting it back to the straight and narrow.


RE: 5.5 Beta Discussions Thread - Dean Roddey - 09-22-2019

I posted 5.4.905. It has Insteon leak detectors (though only support so far for the first two sensors, if they check out I'll add the rest.) It has the (hopefully final worked out) Busy flag stuff for the SMS driver. It fixes the issue I introduced in the last drop of not pushing triggered / scheduled events to the event server when you save (it was only saving to the MS where they won't be seen until the next restart.)


RE: 5.5 Beta Discussions Thread - gReatAutomation - 09-23-2019

Wow.. Not sure what's going on here... Tried clicking on Customize and got this error, and most of my drivers are red. Reverting back to CQCInstSE_5_4_904. Never mind. Cannot revert back.

[Image: Screen-Shot-2019-09-23-at-20-34-15.jpg]

[Image: Screen-Shot-2019-09-23-at-20-43-10.jpg]


RE: 5.5 Beta Discussions Thread - gReatAutomation - 09-23-2019

(09-22-2019, 11:26 AM)Dean Roddey Wrote: 5.4.905
  • Update the SMS driver to better support throttling of msgs. It has a Busy flag now which will remain set for five seconds after sending a message. It will reject msgs if they are sent while the Busy flag is set. So use a Devices::WaitFieldValue() to wait for the Busy Field to be False before you send. If you send faster than then the modem or the target service or 



To clarify, when using an If statement you have to use SafeWaitFieldValue().