Change default setting for `only_publish_changed`
See original GitHub issueCurrently, this integration will publish the current state of all entities every n
seconds, regardless of whether or not this entity underwent a state change.
The intent was to make visualizing this information easier in Kibana, as missing values would not render nicely in line or area charts.
Users who only want to publish state changes need to configure only_publish_changed: true
.
Kibana recently added support for fitting functions for area and line charts (https://github.com/elastic/kibana/pull/78154), so the need for us to publish all states should be reduced.
This issue is a proposal to change the default setting for only_publish_changed
from false
to true
.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:10 (4 by maintainers)
Top Results From Across the Web
Change default programs in Windows - Microsoft Support
Select Start > Settings > Apps > Default apps. To change the default app, you can do either of the following: Set a...
Read more >How to Change Default Apps and Settings in Windows 10
To change other defaults, scroll to the bottom of the default app settings page and you'll see three more menus: Choose default apps...
Read more >7 default settings tech companies don't ever want you to change
7 default settings tech companies don't ever want you to change · 1. Apple, stop tracking my location · 2. Alexa, don't read...
Read more >Customizing preferences and defaults - Adobe Support
To set a default dictionary, close all documents, choose Edit > Preferences > Dictionary (Windows) or InCopy > Preferences > Dictionary (Mac OS) ......
Read more >Set default upload settings - YouTube Help - Google Support
Upload defaults are settings that are applied to all of your web uploads according to your choices. You can choose defaults for your...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
That’s expected if you started one of these betas with existing Elasticsearch config in your yaml file.
If you want to use the UI, then you’ll need to remove the config entry from your yaml, and restart. Next, remove the Elasticsearch integration from the integrations screen (don’t remove the code, or files).
Once that’s done, you can add the integration back through the UI. At this point, you’ll be able to use the UI to tweak your config
I will give it a shot, thank you!! FWIW I changed
publish_frequency
to 300s, and no issues yet with the Chromecasts, so either a coincidence (very possible as have a few networking related plugins), or a viable solution.