Skip to content
  • MySensors
  • OpenHardware.io
  • Categories
  • Recent
  • Tags
  • Popular
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo
  1. Home
  2. Development
  3. MySensors - Get Temperature value from another node through the Gateway

MySensors - Get Temperature value from another node through the Gateway

Scheduled Pinned Locked Moved Development
36 Posts 7 Posters 5.7k Views 6 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • J Offline
    J Offline
    Joe13
    wrote on last edited by
    #3

    Hi @mfalkvidd thanks. Yes my first post.
    I did try that, however, there is no response in the Receive part in the Serial Monitor

    void loop() 
    {
      delay(10000);
      request(12, V_VAR1,3);
      Serial.print("Requested temp from gw VAR1");
      
    
    }
    
    void receive(const MyMessage &message) {
      // We only expect one type of message from controller. But we better check anyway.
      if (message.type==V_VAR1) {
    
        
         // Write some debug info
         Serial.print("Incoming change for sensor:");
         Serial.print(message.sensor);
         Serial.print(", New status: ");
         Serial.println(message.getFloat());
       } 
    }
    

    Serial monitor output after setting Node id (3) instead of Gateway(0)

    Requested temp from gw VAR122279 !TSF:MSG:SEND,1-1-0-3,s=12,c=2,t=24,pt=0,l=0,sg=0,ft=0,st=NACK:
    Requested temp from gw VAR132287 TSF:MSG:SEND,1-1-0-3,s=12,c=2,t=24,pt=0,l=0,sg=0,ft=1,st=OK:
    Requested temp from gw VAR142296 TSF:MSG:SEND,1-1-0-3,s=12,c=2,t=24,pt=0,l=0,sg=0,ft=0,st=OK:
    Requested temp from gw VAR152303 TSF:MSG:SEND,1-1-0-3,s=12,c=2,t=24,pt=0,l=0,sg=0,ft=0,st=OK:
    Requested temp from gw VAR162311 TSF:MSG:SEND,1-1-0-3,s=12,c=2,t=24,pt=0,l=0,sg=0,ft=0,st=OK:
    
    1 Reply Last reply
    0
    • gohanG Offline
      gohanG Offline
      gohan
      Mod
      wrote on last edited by
      #4

      I would approach the problem on the opposite direction, I'd send the temperature to gateway and also to the node with display, so if your temperature node is a sleeping node it would just send when it wakes up and you get your temperature displayed

      J 1 Reply Last reply
      0
      • gohanG gohan

        I would approach the problem on the opposite direction, I'd send the temperature to gateway and also to the node with display, so if your temperature node is a sleeping node it would just send when it wakes up and you get your temperature displayed

        J Offline
        J Offline
        Joe13
        wrote on last edited by
        #5

        @gohan but isn't there a way to get the Temp from the Gateway. I am getting some sort of Receive msg (based on the my initial post) but the value is 0.
        in this way, i can request the temp from the GW whenever required and not ask the node to send the data every few mins

        1 Reply Last reply
        0
        • gohanG Offline
          gohanG Offline
          gohan
          Mod
          wrote on last edited by
          #6

          The gateway doesn't store any data. You could request data from controller if you have one running.

          J 1 Reply Last reply
          1
          • gohanG gohan

            The gateway doesn't store any data. You could request data from controller if you have one running.

            J Offline
            J Offline
            Joe13
            wrote on last edited by Joe13
            #7

            @gohan Yes that would be great. i have Domoticz running and the temp shows up there. could you let me know how I can get the temp from the controller.
            I found this link and that is the code that i initially tried https://www.domoticz.com/forum/viewtopic.php?t=9708
            but gives an O/P of 0

            1 Reply Last reply
            0
            • gohanG Offline
              gohanG Offline
              gohan
              Mod
              wrote on last edited by gohan
              #8

              I have never done it myself, but I'd start looking at the pulse energy meter as it has a function to retrieve a sensor value from controller

              The code in that post is for the old mysensors version

              J 1 Reply Last reply
              0
              • gohanG gohan

                I have never done it myself, but I'd start looking at the pulse energy meter as it has a function to retrieve a sensor value from controller

                The code in that post is for the old mysensors version

                J Offline
                J Offline
                Joe13
                wrote on last edited by Joe13
                #9

                @gohan i did convert it to the 2.1V but the result is the same. so if you were to do something like this, show all the temps from different rooms(nodes) on a central LCD placed in the hall, how would you go about it. I am just a beginner so an ideal way would be great.
                The Pulse energy meter code tell " Received last pulse count from gw:" so could it be possible to get values from GW.

                1 Reply Last reply
                0
                • gohanG Offline
                  gohanG Offline
                  gohan
                  Mod
                  wrote on last edited by
                  #10

                  As said before I'd go for the node to node communication, so send the temperature also to the lcd node, or you could also use an esp8266 and read the the mqtt messages from topic domoticz/out that domoticz sends every time there is a change in the controller data.

                  J 1 Reply Last reply
                  0
                  • gohanG gohan

                    As said before I'd go for the node to node communication, so send the temperature also to the lcd node, or you could also use an esp8266 and read the the mqtt messages from topic domoticz/out that domoticz sends every time there is a change in the controller data.

                    J Offline
                    J Offline
                    Joe13
                    wrote on last edited by
                    #11

                    @gohan thanks, but i do not have much knowledge on ESP8266 and mqtt but will give the a try to push data from the node to the LCD node

                    1 Reply Last reply
                    0
                    • J Offline
                      J Offline
                      Joe13
                      wrote on last edited by
                      #12

                      anyone who has tried pulling value from GW or controller to a different node, please let me know on how you did it. thanks

                      K 1 Reply Last reply
                      0
                      • J Joe13

                        anyone who has tried pulling value from GW or controller to a different node, please let me know on how you did it. thanks

                        K Offline
                        K Offline
                        kimot
                        wrote on last edited by kimot
                        #13

                        @joe13
                        I think, you must send temperature ( for later resending) to domoticz like V_VAR1 for storing it, and then requested it again like V_VAR1. Do not use V_TEMP for this.
                        Look at V_VAR like universal variable for storing anything.
                        At your code examples is not evident, what you put to V_VAR1 first, maybe nothing, so do not be disappointed, if you read 0 back.
                        At EnergyCounter Sensor you can see:

                        MyMessage wattMsg(CHILD_ID,V_WATT);
                        MyMessage kwhMsg(CHILD_ID,V_KWH);
                        MyMessage pcMsg(CHILD_ID,V_VAR1);    !!!!!!
                        ....
                        
                        send(wattMsg.set(watt));
                        send(kwhMsg.set(kwh, 4));  // Send kwh value to gw
                        send(pcMsg.set(pulseCount));  // Send pulse count value to gw         !!!!!!
                         .....
                        
                        request(CHILD_ID, V_VAR1);
                        
                        
                        

                        So it sends to domoticz not only W and kWh for displaying it, but pulse for storing and reading later too.

                        But like wrote gohan, I think better way is sending temperature from node twice - to domoticz and to LCD node. This will work even if domoticz will bee down.

                        J 1 Reply Last reply
                        1
                        • K kimot

                          @joe13
                          I think, you must send temperature ( for later resending) to domoticz like V_VAR1 for storing it, and then requested it again like V_VAR1. Do not use V_TEMP for this.
                          Look at V_VAR like universal variable for storing anything.
                          At your code examples is not evident, what you put to V_VAR1 first, maybe nothing, so do not be disappointed, if you read 0 back.
                          At EnergyCounter Sensor you can see:

                          MyMessage wattMsg(CHILD_ID,V_WATT);
                          MyMessage kwhMsg(CHILD_ID,V_KWH);
                          MyMessage pcMsg(CHILD_ID,V_VAR1);    !!!!!!
                          ....
                          
                          send(wattMsg.set(watt));
                          send(kwhMsg.set(kwh, 4));  // Send kwh value to gw
                          send(pcMsg.set(pulseCount));  // Send pulse count value to gw         !!!!!!
                           .....
                          
                          request(CHILD_ID, V_VAR1);
                          
                          
                          

                          So it sends to domoticz not only W and kWh for displaying it, but pulse for storing and reading later too.

                          But like wrote gohan, I think better way is sending temperature from node twice - to domoticz and to LCD node. This will work even if domoticz will bee down.

                          J Offline
                          J Offline
                          Joe13
                          wrote on last edited by Joe13
                          #14

                          @kimot that part i missed. thanks for pointing that out. I will give this option also a try. its just that the other sensors that are in the other rooms are already set in place and I do not want to pluck them out and recode them. So pulling the values from the GW would have been an advantage. But anyways, if that is the way to go, then Ill probably do that.
                          Thanks everyone for your inputs

                          1 Reply Last reply
                          1
                          • ben999B Offline
                            ben999B Offline
                            ben999
                            wrote on last edited by ben999
                            #15

                            Hi all,

                            Sorry to jump in. If my post is off-topic please say so and i will start a new thread

                            I am in the process of doing the same: a temp/hum node and a node with LCD displaying temp and hum

                            Many-many questions :

                            • all messages (even node-to-node ones) go through gateway and controller ?
                            • sending request(CHILD_ID, V_VAR1) does not mention the node's ID... i just can't get my head round this... there could be many sensors handling the same variable type with the same child id... ? So how do we know we will be getting data from the right node and sensor (child) ?
                            • sending request(CHILD_ID, V_VAR1) will actually ask the controller to ask the node to send its data? Or does it request data straight from node?
                            • isn't there a simple way for nodes to fetch data (data coming from itself and from other nodes) from controller?

                            Thanks for your help

                            rejoe2R 1 Reply Last reply
                            0
                            • ben999B ben999

                              Hi all,

                              Sorry to jump in. If my post is off-topic please say so and i will start a new thread

                              I am in the process of doing the same: a temp/hum node and a node with LCD displaying temp and hum

                              Many-many questions :

                              • all messages (even node-to-node ones) go through gateway and controller ?
                              • sending request(CHILD_ID, V_VAR1) does not mention the node's ID... i just can't get my head round this... there could be many sensors handling the same variable type with the same child id... ? So how do we know we will be getting data from the right node and sensor (child) ?
                              • sending request(CHILD_ID, V_VAR1) will actually ask the controller to ask the node to send its data? Or does it request data straight from node?
                              • isn't there a simple way for nodes to fetch data (data coming from itself and from other nodes) from controller?

                              Thanks for your help

                              rejoe2R Offline
                              rejoe2R Offline
                              rejoe2
                              wrote on last edited by
                              #16

                              @ben999 If you do node-to-node communication, the message does not necessarily need a controller; it is routed through the lowest common repeater node (this might be the gateway). Eg. if you have two nodes 5 and 6 that are communicating over node 4 with the gw, the gw may not even see the message.
                              Coding then looks like this:

                              send(SisternodeMsg.setDestination(MY_SISTER_NODE_ID).setSensor(CHILD_ID_SISTER_TEMP).set(temperature, 1));
                              

                              In case you use a controller, you would have to map the values through the controller's functionality (eg. put temperature value #2 from node 5 to value2100 on node 6 so this can be requested from node #6 using it's own ID and child ID 100 - V_VAR2.

                              In both cases you have to code appropriate receive()-functionality.

                              Controller: FHEM; MySensors: 2.3.1, RS485,nRF24,RFM69, serial Gateways

                              ben999B 1 Reply Last reply
                              2
                              • rejoe2R rejoe2

                                @ben999 If you do node-to-node communication, the message does not necessarily need a controller; it is routed through the lowest common repeater node (this might be the gateway). Eg. if you have two nodes 5 and 6 that are communicating over node 4 with the gw, the gw may not even see the message.
                                Coding then looks like this:

                                send(SisternodeMsg.setDestination(MY_SISTER_NODE_ID).setSensor(CHILD_ID_SISTER_TEMP).set(temperature, 1));
                                

                                In case you use a controller, you would have to map the values through the controller's functionality (eg. put temperature value #2 from node 5 to value2100 on node 6 so this can be requested from node #6 using it's own ID and child ID 100 - V_VAR2.

                                In both cases you have to code appropriate receive()-functionality.

                                ben999B Offline
                                ben999B Offline
                                ben999
                                wrote on last edited by
                                #17

                                If you do node-to-node communication, the message does not necessarily need a controller; it is routed through the lowest common repeater node (this might be the gateway). Eg. if you have two nodes 5 and 6 that are communicating over node 4 with the gw, the gw may not even see the message.
                                Coding then looks like this:

                                send(SisternodeMsg.setDestination(MY_SISTER_NODE_ID).setSensor(CHILD_ID_SISTER_TEMP).set(temperature, 1));
                                

                                That makes sense, big thumbs up, thanks a lot

                                On the other hand I didn't understant a word of that... sorry...
                                Could you please detail a wee bit more? And also please explain who is doing what...

                                In case you use a controller, you would have to map the values through the controller's functionality (eg. put temperature value #2 from node 5 to value2100 on node 6 so this can be requested from node #6 using it's own ID and child ID 100 - V_VAR2.

                                I should be able to do that :)

                                In both cases you have to code appropriate receive()-functionality.

                                Thanks a lot for your help

                                rejoe2R 1 Reply Last reply
                                0
                                • ben999B ben999

                                  If you do node-to-node communication, the message does not necessarily need a controller; it is routed through the lowest common repeater node (this might be the gateway). Eg. if you have two nodes 5 and 6 that are communicating over node 4 with the gw, the gw may not even see the message.
                                  Coding then looks like this:

                                  send(SisternodeMsg.setDestination(MY_SISTER_NODE_ID).setSensor(CHILD_ID_SISTER_TEMP).set(temperature, 1));
                                  

                                  That makes sense, big thumbs up, thanks a lot

                                  On the other hand I didn't understant a word of that... sorry...
                                  Could you please detail a wee bit more? And also please explain who is doing what...

                                  In case you use a controller, you would have to map the values through the controller's functionality (eg. put temperature value #2 from node 5 to value2100 on node 6 so this can be requested from node #6 using it's own ID and child ID 100 - V_VAR2.

                                  I should be able to do that :)

                                  In both cases you have to code appropriate receive()-functionality.

                                  Thanks a lot for your help

                                  rejoe2R Offline
                                  rejoe2R Offline
                                  rejoe2
                                  wrote on last edited by
                                  #18

                                  @ben999 I also had a hard time to sort things out wrt. to node-to-node communication. But in the end, its simple:
                                  You just have to use appropriate send()- and recieve() commands in the nodes. Example for the temperature part, using the node numbers from above:

                                  • For the one providing the needed info (node 5): This one is measuring temp and sends this to node 6: In the code for this node use additionally to the "normal" send() the above code and replace "MY_SISTER_NODE_ID" with 6 and "CHILD_ID_SISTER_TEMP" let's say with 101 (or use appropriate #define's).
                                  • In the receive() part of Node 6 you have to sort things by using the correspondant Child ID as follows:
                                  if (message.sensor == 101) {...
                                  

                                  I personally prefer using "speaking names" like CHILD_ID_SISTER_TEMP and define them in the header, that's what's behind the first send() code-snipplet, but that's just a question of style.

                                  Controller: FHEM; MySensors: 2.3.1, RS485,nRF24,RFM69, serial Gateways

                                  ben999B 1 Reply Last reply
                                  2
                                  • rejoe2R rejoe2

                                    @ben999 I also had a hard time to sort things out wrt. to node-to-node communication. But in the end, its simple:
                                    You just have to use appropriate send()- and recieve() commands in the nodes. Example for the temperature part, using the node numbers from above:

                                    • For the one providing the needed info (node 5): This one is measuring temp and sends this to node 6: In the code for this node use additionally to the "normal" send() the above code and replace "MY_SISTER_NODE_ID" with 6 and "CHILD_ID_SISTER_TEMP" let's say with 101 (or use appropriate #define's).
                                    • In the receive() part of Node 6 you have to sort things by using the correspondant Child ID as follows:
                                    if (message.sensor == 101) {...
                                    

                                    I personally prefer using "speaking names" like CHILD_ID_SISTER_TEMP and define them in the header, that's what's behind the first send() code-snipplet, but that's just a question of style.

                                    ben999B Offline
                                    ben999B Offline
                                    ben999
                                    wrote on last edited by
                                    #19

                                    @rejoe2 GREAT! You gave sense to all that. Is it what some clever blokes refer to "dummy sensor" method?

                                    May I ask some more @rejoe2 ?
                                    How would you retrieve a value DIRECTLY FROM the controller?
                                    Say that node 5 and 6 sleep most of their time... so they never get to speak directly to each other. Then the controller would be the mail box... I already send temp data to the controller and get it displayed in PaperUI and iOS app (using openHab). How would node 6 fetch this piece of data?

                                    Once more, thanks a lot for your time and patience (it's not easy eaducating people :D )

                                    rejoe2R 1 Reply Last reply
                                    0
                                    • ben999B ben999

                                      @rejoe2 GREAT! You gave sense to all that. Is it what some clever blokes refer to "dummy sensor" method?

                                      May I ask some more @rejoe2 ?
                                      How would you retrieve a value DIRECTLY FROM the controller?
                                      Say that node 5 and 6 sleep most of their time... so they never get to speak directly to each other. Then the controller would be the mail box... I already send temp data to the controller and get it displayed in PaperUI and iOS app (using openHab). How would node 6 fetch this piece of data?

                                      Once more, thanks a lot for your time and patience (it's not easy eaducating people :D )

                                      rejoe2R Offline
                                      rejoe2R Offline
                                      rejoe2
                                      wrote on last edited by rejoe2
                                      #20

                                      @ben999 You are welcome.
                                      For "indirect" communication you may use the V_VARx-method already mentionned. This requires the controller to have the requested info stored at the right place (eg. FHEM would store V_VAR1 of Child 101 in a reading named "value1101" of the respective device).
                                      Then just use the EnergyMeterPulse-sketch as example how to ask info from nodes side to be send from controller while not sleeping.
                                      That should do the trick.

                                      Just one remark: Having a display and a sleeping node doesn't fit to well together imo :grinning:

                                      EDIT: To make things more clear: the V_VARx has to be stored in the values of the requesting node, so if the display is attached to node 6, your controller has to provide the values as reading on node 6...

                                      Controller: FHEM; MySensors: 2.3.1, RS485,nRF24,RFM69, serial Gateways

                                      ben999B 1 Reply Last reply
                                      1
                                      • rejoe2R rejoe2

                                        @ben999 You are welcome.
                                        For "indirect" communication you may use the V_VARx-method already mentionned. This requires the controller to have the requested info stored at the right place (eg. FHEM would store V_VAR1 of Child 101 in a reading named "value1101" of the respective device).
                                        Then just use the EnergyMeterPulse-sketch as example how to ask info from nodes side to be send from controller while not sleeping.
                                        That should do the trick.

                                        Just one remark: Having a display and a sleeping node doesn't fit to well together imo :grinning:

                                        EDIT: To make things more clear: the V_VARx has to be stored in the values of the requesting node, so if the display is attached to node 6, your controller has to provide the values as reading on node 6...

                                        ben999B Offline
                                        ben999B Offline
                                        ben999
                                        wrote on last edited by ben999
                                        #21

                                        @rejoe2 Dude!!! It worked! Awesome :D Node-to-node is now understood and tested :)

                                        Now i need (for my personal benefit) to get my node to fetch data from controller
                                        FHEM seems to be some type of controller software like Openhab and so many others... ? Next move is to discover where and how data is stored within openhab...

                                        Once again @rejoe2 thank you very much for passing on your knowledge

                                        Just one remark: Having a display and a sleeping node doesn't fit to well together imo 😀

                                        I just wanted to make sure you would not lead me to any other way :D as i wanted to understand both ways of sharing data between nodes
                                        Thank you so much for that :+1:

                                        rejoe2R 1 Reply Last reply
                                        1
                                        • ben999B ben999

                                          @rejoe2 Dude!!! It worked! Awesome :D Node-to-node is now understood and tested :)

                                          Now i need (for my personal benefit) to get my node to fetch data from controller
                                          FHEM seems to be some type of controller software like Openhab and so many others... ? Next move is to discover where and how data is stored within openhab...

                                          Once again @rejoe2 thank you very much for passing on your knowledge

                                          Just one remark: Having a display and a sleeping node doesn't fit to well together imo 😀

                                          I just wanted to make sure you would not lead me to any other way :D as i wanted to understand both ways of sharing data between nodes
                                          Thank you so much for that :+1:

                                          rejoe2R Offline
                                          rejoe2R Offline
                                          rejoe2
                                          wrote on last edited by
                                          #22

                                          @ben999 said in MySensors - Get Temperature value from another node through the Gateway:
                                          Thx for reporting about getting this to work as expected!

                                          FHEM seems to be some type of controller software like Openhab and so many others... ?

                                          FHEM is - as mentionned in my signature - also a controller software. It's written in perl (which is very special) and a very flexible solution allowing a broad spectrum of hardware to be integrated, but unfortunately not very famous outside Germany (as most posts in the forum are in german). But questions in english are also answered, see fhem.de for more details, if you're interested.

                                          Controller: FHEM; MySensors: 2.3.1, RS485,nRF24,RFM69, serial Gateways

                                          1 Reply Last reply
                                          1
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          24

                                          Online

                                          11.7k

                                          Users

                                          11.2k

                                          Topics

                                          113.1k

                                          Posts


                                          Copyright 2025 TBD   |   Forum Guidelines   |   Privacy Policy   |   Terms of Service
                                          • Login

                                          • Don't have an account? Register

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • MySensors
                                          • OpenHardware.io
                                          • Categories
                                          • Recent
                                          • Tags
                                          • Popular