WeeWX-MQTTSubscribe | A WeeWX service and driver that receives data from MQTT
kandi X-RAY | WeeWX-MQTTSubscribe Summary
kandi X-RAY | WeeWX-MQTTSubscribe Summary
WeeWX-MQTTSubscribe is a Python library typically used in Manufacturing, Utilities, Automotive, Internet of Things (IoT), Arduino applications. WeeWX-MQTTSubscribe has no bugs, it has no vulnerabilities and it has low support. However WeeWX-MQTTSubscribe build file is not available. You can download it from GitHub.
The driver captures the MQTT payload in a separate thread. Then in genLoopPackets, every element in the queue is turned into its own packet. It is also possible to subscribe to a second topic. The MQTT payload from this topic is put into a separate queue. This queue is processed by the genArchiveRecords to create archive records (simulating hardware generation). With the combination of the two topics/queues, one can have a WeeWX instance gather the data and publish loop and archive data for other instances to receive. When generating loop packets and the queue becomes empty, the option, wait_before_retry, controls how long before an attempt is made to get data from the queue. The service can bind to either new loop packets or new archive records. In both cases a separate thread captures the MQTT payload and puts it on a queue. On new packets/records events, the main thread takes the elements from the queue and accumulates them into a single dictionary of data fields. If necessary, the data is converted to the units of the packet/record. The packet/record is then updated with the data. The elements that are processed from the queue can be controlled by various configuration options. By default, if the MQTT datetime is less than the previous packet's datetime it is ignored. This check can be ignored by setting ignore_start_time to True. It can be controlled more granularly by setting adjust_start_time to the number of seconds prior to the previous packet's datetime is allowed. Also by default, when the MQTT datetime is greater than the packet's datetime, the pocessing of the queue for this packet stops. This check can be ignored by setting ignore_end_time to True. It can be controlled more granularly by setting adjust_end_time to the number of seconds after the packet's datetime is allowed to be processed.
The driver captures the MQTT payload in a separate thread. Then in genLoopPackets, every element in the queue is turned into its own packet. It is also possible to subscribe to a second topic. The MQTT payload from this topic is put into a separate queue. This queue is processed by the genArchiveRecords to create archive records (simulating hardware generation). With the combination of the two topics/queues, one can have a WeeWX instance gather the data and publish loop and archive data for other instances to receive. When generating loop packets and the queue becomes empty, the option, wait_before_retry, controls how long before an attempt is made to get data from the queue. The service can bind to either new loop packets or new archive records. In both cases a separate thread captures the MQTT payload and puts it on a queue. On new packets/records events, the main thread takes the elements from the queue and accumulates them into a single dictionary of data fields. If necessary, the data is converted to the units of the packet/record. The packet/record is then updated with the data. The elements that are processed from the queue can be controlled by various configuration options. By default, if the MQTT datetime is less than the previous packet's datetime it is ignored. This check can be ignored by setting ignore_start_time to True. It can be controlled more granularly by setting adjust_start_time to the number of seconds prior to the previous packet's datetime is allowed. Also by default, when the MQTT datetime is greater than the packet's datetime, the pocessing of the queue for this packet stops. This check can be ignored by setting ignore_end_time to True. It can be controlled more granularly by setting adjust_end_time to the number of seconds after the packet's datetime is allowed to be processed.
Support
Quality
Security
License
Reuse
Support
WeeWX-MQTTSubscribe has a low active ecosystem.
It has 36 star(s) with 12 fork(s). There are 9 watchers for this library.
It had no major release in the last 12 months.
There are 3 open issues and 116 have been closed. On average issues are closed in 101 days. There are no pull requests.
It has a neutral sentiment in the developer community.
The latest version of WeeWX-MQTTSubscribe is v2.2.2
Quality
WeeWX-MQTTSubscribe has no bugs reported.
Security
WeeWX-MQTTSubscribe has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
License
WeeWX-MQTTSubscribe does not have a standard license declared.
Check the repository for any license declaration and review the terms closely.
Without a license, all rights are reserved, and you cannot use the library in your applications.
Reuse
WeeWX-MQTTSubscribe releases are available to install and integrate.
WeeWX-MQTTSubscribe has no build file. You will be need to create the build yourself to build the component from source.
Installation instructions, examples and code snippets are available.
Top functions reviewed by kandi - BETA
kandi has reviewed WeeWX-MQTTSubscribe and discovered the below as its top functions. This is intended to give you an instant insight into WeeWX-MQTTSubscribe implemented functionality, and help decide if they suit your requirements.
- Run the simulation
- Simulate a driver
- Generate archive records
- Simulate a driver packet
- Disconnect from RabbitMQ
- Called when a message is received
- Process a single message
- Helper function to update data
- Log an exception
- Log the current environment
- Log a debug message
- Log info about the client
- Disconnect from the server
- Return the value for a specific topic
Get all kandi verified functions for this library.
WeeWX-MQTTSubscribe Key Features
No Key Features are available at this moment for WeeWX-MQTTSubscribe.
WeeWX-MQTTSubscribe Examples and Code Snippets
No Code Snippets are available at this moment for WeeWX-MQTTSubscribe.
Community Discussions
Trending Discussions on Internet of Things (IoT)
QUESTION
Display data from two json files in react native
Asked 2020-May-17 at 23:55
I have js files Dashboard and Adverts. I managed to get Dashboard to list the information in one json file (advertisers), but when clicking on an advertiser I want it to navigate to a separate page that will display some data (Say title and text) from the second json file (productadverts). I can't get it to work. Below is the code for the Dashboard and next for Adverts. Then the json files
...ANSWER
Answered 2020-May-17 at 23:55The new object to get params in React Navigation 5 is:
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install WeeWX-MQTTSubscribe
Note: It is rare that MQTTSubscribe should be configured to run as both a service and driver. If you are augmenting an existing driver's data, run MQTTSubscribe as a service. Otherwise, run it as a driver.
$DOWNLOAD_ROOT - The directory containing the downloaded MQTTSubscribe extension.
$BIN_ROOT - The directory where WeeWX executables are located.
$CONFIG_ROOT - The directory where the configuration (typically, weewx.conf) is located.
All of the releases can be found here and this is the latest. In either case, edit the [MQTTSubscribeDriver] or [MQTTSubscribeService] stanza as required. At the very least the [[topics]] stanza must be configured to the topics to subscribe to. Other settings such as host and port may need to be changed. See, configuring MQTTSubscribe.
Download MQTTSubscribe wget -P $DOWNLOAD_ROOT https://github.com/bellrichm/WeeWX-MQTTSubscribe/archive/vX.Y.Z.tar.gz All of the releases can be found here and this is the latest.
Install MQTTSubscribe As a driver $BIN_ROOT/wee_extension --install=$DOWNLOAD_ROOT/vX.Y.Z.tar.gz $BIN_ROOT/wee_config --reconfig Note: By default when installing, the service is installed and configured, but not enabled. To not install and configure the service (only install the file(s)), set the environment variable MQTTSubscribe_install_type to DRIVER. For example, MQTTSubscribe_install_type=DRIVER $BIN_ROOT/wee_extension --install=$DOWNLOAD_ROOT/vX.Y.Z.tar.gz And then configure the driver. $BIN_ROOT/wee_config --reconfig As a service $BIN_ROOT/wee_extension --install=$DOWNLOAD_DIR/vX.Y.Z.tar.gz Note: By default when installing, the service is installed and configured, but not enabled. To enable, set the environment variable MQTTSubscribe_install_type to SERVICE. For example, MQTTSubscribe_install_type=SERVICE $BIN_ROOT/wee_extension --install=$DOWNLOAD_DIR/vX.Y.Z.tar.gz In either case, edit the [MQTTSubscribeDriver] or [MQTTSubscribeService] stanza as required. At the very least the [[topics]] stanza must be configured to the topics to subscribe to. Other settings such as host and port may need to be changed. See, configuring MQTTSubscribe.
Restart WeeWX sudo /etc/init.d/weewx restart or sudo sudo service restart weewx or sudo systemctl restart weewx
$DOWNLOAD_ROOT - The directory containing the downloaded MQTTSubscribe extension.
$BIN_ROOT - The directory where WeeWX executables are located.
$CONFIG_ROOT - The directory where the configuration (typically, weewx.conf) is located.
All of the releases can be found here and this is the latest. In either case, edit the [MQTTSubscribeDriver] or [MQTTSubscribeService] stanza as required. At the very least the [[topics]] stanza must be configured to the topics to subscribe to. Other settings such as host and port may need to be changed. See, configuring MQTTSubscribe.
Download MQTTSubscribe wget -P $DOWNLOAD_ROOT https://github.com/bellrichm/WeeWX-MQTTSubscribe/archive/vX.Y.Z.tar.gz All of the releases can be found here and this is the latest.
Install MQTTSubscribe As a driver $BIN_ROOT/wee_extension --install=$DOWNLOAD_ROOT/vX.Y.Z.tar.gz $BIN_ROOT/wee_config --reconfig Note: By default when installing, the service is installed and configured, but not enabled. To not install and configure the service (only install the file(s)), set the environment variable MQTTSubscribe_install_type to DRIVER. For example, MQTTSubscribe_install_type=DRIVER $BIN_ROOT/wee_extension --install=$DOWNLOAD_ROOT/vX.Y.Z.tar.gz And then configure the driver. $BIN_ROOT/wee_config --reconfig As a service $BIN_ROOT/wee_extension --install=$DOWNLOAD_DIR/vX.Y.Z.tar.gz Note: By default when installing, the service is installed and configured, but not enabled. To enable, set the environment variable MQTTSubscribe_install_type to SERVICE. For example, MQTTSubscribe_install_type=SERVICE $BIN_ROOT/wee_extension --install=$DOWNLOAD_DIR/vX.Y.Z.tar.gz In either case, edit the [MQTTSubscribeDriver] or [MQTTSubscribeService] stanza as required. At the very least the [[topics]] stanza must be configured to the topics to subscribe to. Other settings such as host and port may need to be changed. See, configuring MQTTSubscribe.
Restart WeeWX sudo /etc/init.d/weewx restart or sudo sudo service restart weewx or sudo systemctl restart weewx
Support
Feel free to open an issue, start a discussion in github, or post on WeeWX google group. When doing so, see Help! Posting to weewx user for information on capturing the log. And yes, capturing the log from WeeWX startup makes debugging much easeier.
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page
