Note, we’re removing the “freq” (device frequency) parameter from the UDP device_status message in an upcoming firmware release. Just wanted to drop a heads-up to anyone who might have code that’s expecting that parameter to be there.
I frequently wondered why it frequently changed and how I could frequently use the frequency data.
I will remove it and push out the other changes so @dan.gealt can see what I may have broken.
Thanks for the heads up. I’ll have to remove it from the ISY node server.
Oh, take it easy on yourself Gary . . . I don’t think you broke anything this month yet . . .
I guess I’m not trying enough.
Can you share the technical or business reasons for doing so?
Would you consider moving some of the other non-essential data to X_debug packets? This would allow WeatherFlow to add and remove parameters that are of no use to the oversll weather data.
Also any foreseeable future non-essential parameters to be removed?
(1) it was not working correctly, (2) it doesn’t really belong in the “device” level message and (3) it is not necessary for anything.
I think adding future non-essential data to _debug messages is a great idea, but if the data in other messages isn’t wrong and isn’t hurting anything, we aren’t likely to change it proactively (ain’t broke, don’t fix).
None in the foreseeable, but probably some in the unforeseeable!