Skip to content
#

iot

Here are 10,725 public repositories matching this topic...

netdata
HolgerHees
HolgerHees commented May 17, 2019

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

averelon
averelon commented Aug 7, 2020

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

jouve
jouve commented Jun 3, 2021

Description

let's say I have an apache process group I want to control.

  • when using supervisord.running, the name must be apache:* (which is the same notation used by supervisor)
  • when using supervisord.dead, the name must be apache: (without the *)

As both states mirror each other, I expect them to use the same convention for name, the one from running since it

urh
jacobagilbert
jacobagilbert commented Sep 18, 2020

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

liuxiran
liuxiran commented Jul 27, 2021

Issue description

Environment

Bug report without environment information will be ignored or closed.

  • apisix version (cmd: apisix version): 2.7
  • OS (cmd: uname -a): Darwin Kernel Version 20.3.0
  • OpenResty / Nginx version (cmd: nginx -V or openresty -V): openresty/1.19.3.1
  • etcd version, if have (cmd: run curl http://127.0.0.1:9090/v1/server_info to get the info fro
microk8s
dstathis
dstathis commented Jul 1, 2021

When you run "microk8s add node" you get output that looks like:

From the node you wish to join to this cluster, run the following:
microk8s join 10.220.113.121:25000/199cfabfeabc905c629ad98d93be964a/d86a2309e376

If the node you are adding is not reachable through the default interface you can use one of the following:
 microk8s join 10.220.113.121:25000/199cfabfeabc905
node-serialport
SVSagi
SVSagi commented Jul 30, 2018

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

questdb
marregui
marregui commented Jul 20, 2021

Scenario

create table tab(f float);
insert into tab(f) values(4273.8);

Results in: org.postgresql.util.PSQLException: ERROR: inconvertible types: DOUBLE -> FLOAT [from=4273.8, to=f]

Expectation

Possibly enhance type compatibility check (SqlCompiler.isAssignableFrom) with extra cases for numeric types:

  • Float <- Double: if the double fits in the Float, then
wrannaman
wrannaman commented Mar 23, 2019

How are you planning on using kubeedge?

I've been looking for something like this for a long time (Currently our team uses Rancher although their product wasn't really meant for edge computing.) I'd love to hear how others in the community would like to use this so I can compile a list of use cases that kubeedge can support out of the box.

Thanks!

Improve this page

Add a description, image, and links to the iot topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the iot topic, visit your repo's landing page and select "manage topics."

Learn more