BigMojo Posted August 10, 2023 Posted August 10, 2023 Have the work queue query the parameter, capture the byte size and append that dynamically to the write parameter command issued. Pro: no mismatched sizes in programs, potentially negate any device level errors due to bad incoming data. Of course the device firmware SHOULD be handling this but driving one's own ship is usually safest. Con: More zWave traffic and delayed code execution vs. "hard" writes. It's a parameter update, is code speed really a consideration? Optional: I.e. if the program contains the size, process the command unmolested, otherwise retrieve and append the size? This could be a nice differentiation for maintenance (slow) vs. production programs. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.