Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you may not be able to execute some actions.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

question about Variable type for child-sensor-id

yogui79 last edited by yogui79

Hello

does the protocoll allow more that one variable type for one child-sensor-id

thanks in advance for your answhere
Reply Quote 0
1 Reply Last reply
mfalkvidd Mod last edited by mfalkvidd @yogui79

@yogui79 yes. For an actual implementation, see the power meter example. It sends three values for the same child id.
Reply Quote 0
1 Reply Last reply
yogui79 last edited by

thank you for your answere @mfalkvidd
Reply Quote 1
1 Reply Last reply

3
Posts

909
Views

Log in to reply

Suggested Topics

Arduino Celebrates 10 years (Malmö/Sweden)
Announcements • • hek

1

0
Votes

1
Posts

3304
Views

No one has replied
MQTT GW on ESP8266 supporting SSL/TLS?
Development • esp8266 mqtt gw • • bgunnarb

6

0
Votes

6
Posts

27
Views

@bgunnarb I like @eiten 's solution for you. Personally, I am not a fan of using cloud/public brokers. Thus I am curious about your system and there is something about it from which I can learn. I would like to understand why you cannot deploy your own mosquitto broker. I see your set up as 3 sensor groups defined by the channel used #define MY_RF24_CHANNEL ChannelOfSensorGroup Each sensor group has some number of sensors and one MQTT GW on ESP8266. On the MQTT side, do you distinguish between gateways by using a different host name? Something like: #define MY_MQTT_PUBLISH_TOPIC_PREFIX "mygateway-nOf3-out" #define MY_MQTT_SUBSCRIBE_TOPIC_PREFIX "mygateway-nOf3-in" #define MY_MQTT_CLIENT_ID "mysensors-nOf3" #define MY_HOSTNAME "ESP8266_MQTT_GW_nOf3" //#define MY_CONTROLLER_IP_ADDRESS 192, 168, 178, 68 #define MY_CONTROLLER_URL_ADDRESS "test.mosquitto.org" #define MY_PORT 1883 I must assume your controller (aka Home Assistant) discriminates between through which gateway the data is to flow by way of the different topic names. If my "something like" is correct, then changing brokers is changing the IPaddress/URL in your gateways and in your controller (though if the controller is Home Assistant, it may be a bother because the device-id's may change which will make a mess of all the work you've done in HA. This is why I like @eiten 's solution.) I hope it's all working for you again. OSD
MYSController with MQTT Gateway (via Node Red)
Development • • slt1

1

1
Votes

1
Posts

10
Views

No one has replied
Serial Gateway woes
Development • • OldSurferDude

1

0
Votes

1
Posts

9
Views

No one has replied
(SOLVED) Sensebender Gateway and HomeAssistant: where does the battery level come from?
Development • • pikim

1

0
Votes

1
Posts

11
Views

No one has replied
Sensebender Gateway (SAMD21)
Development • • pikim

10

0
Votes

10
Posts

54
Views

Just for completeness: the right way to do this is to add the json under ~/.platformio/boards and the other files as described in https://community.platformio.org/t/how-use-a-same-chip-but-with-different-environment/18082/4

49
Online

11.4k
Users

11.1k
Topics

112.6k
Posts

Copyright 2019 Sensnology | Forum Guidelines | Privacy Policy | Terms of Service

1 / 1