Bugs - IoT Guru Forum

REST API functionality....

OnPa — Tue, 05 Oct 2021 14:10:30 +0000

Hi,

is API REST working now ?

Thanks,

Ondrej

Device selection is missing when we create a new chart

Dunaparty — Mon, 08 Jun 2020 12:37:30 +0000

Hello,

When we create a new chart on the dashboard, we need to select the node name, which can be problematic if we use the same node names across multiple devices.

Thanks!

Bad time label

Dunaparty — Mon, 08 Jun 2020 12:09:13 +0000

Hello,

As you can see in the attached screenshot, `:30:00` is visible as timestamp on the x axis. I guess it should be `23:30`.

Is it UTC? It would be better to visualize charts according to the timezone of the phone.

Thanks!

No subscribe echo when publishing via MQTT

Jasonb — Sat, 07 Mar 2020 01:02:43 +0000

Using the PAHO online MQTT over WebSocket test client

I connect and subscribe to sub/{user short identifier}/#.

Any message I publish to pub/{user short identifier}/{device short identifier}/{node short identifier}/{field name} using the Paho test client never appears in the "Last Messages" section. However if I use the android app and the "MQTT On/Off" widget the messages appear as expected.

I have confirmed that using the Paho client publish, the values do appear under "Last Values" on the field screen, therefore the publish is succeeding.

In the MQTT tutorial it states "We will route your published messages from pub/* topic to sub/* topic. " therefore I am expecting to see a subscribe message for every publish message sent through the Paho test client or am I misunderstanding?

Change request for Range check

Jean-Luc — Fri, 28 Feb 2020 14:05:20 +0000

Hi,

When there is an "out of range" for a certain field, iotguru robot sends a message. When it is back to the normal range we receive another message from the robot.

This is fine and very useful. Actually the robot provides the node name and fiel name which triggers the alert.

There is only a thing which might be helpful, it is to provide also the device name. If we have several devices with the same node name, we have to search which one has triggered the alert.

Example of message received:

============================

Hi,

The measurement value of DHT22 - temperature is in the NORMAL RANGE. It was out of range for 1 hour 22 minutes.

The range is between 15 and 27, the last value was 15.8.

Best regards,

IoT GURU Alert Robot

=============================

As an example a message including the device could be:

The measurement value of Bedroom - DHT22 - temperature is in the NORMAL RANGE. It was out of range for 1 hour 22 minutes.

There is another way: we can include the device name inside the node name, but it seems to me less clean.