iot

Hi,

first thanks for this awesome software. But I have some trouble and I don't know how to proceed. First I try to find out what else I could provide for this report to be a good bug report.

First, I use the latest version (v1.14.0) from openSUSE build Service. I know, I should compile it by my self to avoid any other causes for this behavior. But for now I still use this package from there

Can anyone please help me out. I'm getting error while generating KONG client credentials on HTTP port 8000.

{ "error_description": "You must use HTTPS", "error": "access_denied" }

I have added trusted_ips = 0.0.0.0/0,::/0 in kong.conf also, but it didn't work.

In document "TAOS SQL" section:
https://github.com/taosdata/TDengine/blob/develop/documentation20/cn/12.taos-sql/docs.md

The Chinese translation for "downsampling" is "降频", which has meaning "reduce frequency". The original meaning for English word "downsampling

The uncompensated temperature of the BMP180 is incorrectly converted to a 16-bit signed value, instead of a 32-bit signed value (long). Since the data is 16-bits wide and can therefore not be negative, the easy fix would be to do the following:

sip.js(1128): uncompensated = uint16(data[0], data[1]);

Please see page 15 of the manual of the BMP180 chip:
https://ae-bst.resource.bosch.com/media

Describe the solution you'd like
It would be nice to have a way to control whether a VM starts on boot or not. Maybe a new autostart option to salt.states.virt.running and/or salt.states.virt.defined? Or maybe a new function?

Describe alternatives you've considered
I'll probably use salt.modules.virt.set_autostart for now.

A common protocol structure is to have a header containing a length field, followed by data of length bytes, followed by additional protocol fields such as a CRC. If the length field is variable, the position of subsequent URH-specified protocol fields defined by fixed position will not be in the correct location.

I do not know the best way to address this, but quick and easy way to support

Improved or typo fixed.

Global rule doc may mistakenly define the scope of plugin.

Solution

Please correct global rule doc.

• macOS Big Sur 11.5.1
• microk8s 2.1.0 installed from home-brew today
• 'microk8s inspect' not working (will raise a different issue on this)
• Additional features installed including 'dashboard' (no apps/customization yet)

Experienced an issue #2507 so went to gather output from 'microk8s inspect'.

However whilst this seemed to work, no file output was evident (could be long location, i

Summary of Problem

Not able to open port with stopbits as 1.5

I am currently building a desktop client using electron, where the COM port receives data correctly for values: baudRate: 2400, dataBits: 7, stopBits: 1.5, parity: 'none'

I found from the node-serialport documentation, stopBits Must be one of these: 1 or 2. But, should 1.5 be supported as well? especially for old & slow

Is your enhancement proposal related to a problem? Please describe.
Refer to: zephyrproject-rtos/zephyr#28932

Describe the solution you'd like
Refer to: zephyrproject-rtos/zephyr#28932 (comment)

Describe alternatives you've considered
NA

Additional context
NA

Is your feature request related to a problem? Please describe.
So I'm working on a product that should allow schema-less ingestion out of the box. So my default ingestion method is via the influx line protocol.

But my challenge is that I also need to add indexes to some of the tags (symbols) after table creation. The problem is that the Influx Line protocol holds a lock to the table makin