Electricity Bill Module Development

[sdetweil]

@SopaMaruchan get data from API

let’s call the object foo

then

this.sendSocketNotification(“fribble”, foo)

then on the module side

  receiveSocketNotification(code, data){
          if(code === 'fribble'){
                 this.savePointer = data
                 this.updateDom()
          }
   }

then

      getDom(){
               //  use  this.savePonter
      }

[SopaMaruchan]

@sdetweil I named my retreived data as “foo” and then used sendSocketNotification as you previously told me but I got this as output:

I did it this way on my node_helper file (Highlighted the lines I added):

Did I missed anything?

[sdetweil]

@SopaMaruchan ah, so much fun!

you are inside the callback of the request,so ‘this’ I pointing to some request object and not the node_helper instance…

sooooo

before request(…

add
let self = this

and change this. to self.

object oriented programming is tricky

[sdetweil]

@SopaMaruchan and {foo} is unnecessary

you could just use
res.body

it’s the same stuff, why waste memory w a new pointer only being used once

(same w info there too)

[SopaMaruchan]

@sdetweil Hahahaha true that!
Kinda fixed it guided by your recommendations but the thing is that I’m still getting the same output:
Here the code:

[sdetweil]

@SopaMaruchan hm…

sample from one of my modules

self.sendSocketNotification("SLEEP_HIDE")

[SopaMaruchan]

hmm, actually it does help. I’ll be testing around and tell you when I get it to work!
Anyways your help was a huge pilar to keep myself going with this, much thanks brother💝

[SopaMaruchan]

Does it help if I tell you that I got everything on my onstart function of the node_helper file?

[sdetweil]

@SopaMaruchan never done it in start.

I usually wait til the module sends it’s 1st request

[SopaMaruchan]

@SopaMaruchan I’m realizing that my my receiveSocketNotification is not being triggered on my MM-Module file:

I logged some text after calling receiveSocketNotification function but there’s no output on console.

node_helper:

[sdetweil]

@SopaMaruchan if the send fails like that, not sent

[sdetweil]

@SopaMaruchan
let self=this

has to be inside the getBill() function
otherwise it could be set wrong…

[sdetweil]

@SopaMaruchan maybe for debug

inside the request() callback function,

do a

console.log(JSON.stringify(self, null,2))

to see what ‘this’ was pointing to

[SopaMaruchan]

@sdetweil it’s indeed pointing to my module. Here’s the output:
and the huge LOG ends with the last 2 arguments: null & 2

[sdetweil]

@SopaMaruchan

problem is that the sockets are not connected at start time. so the sendSocketNotification is a no-op.

u need wait til the module sends a socket message

the module config is not visible to the node_helper, so the module has to send it over/down…

[mumblebaj]

@SopaMaruchan Maybe the below example would help or serve as a guide to see if you may have the send call in the wrong place.

module.exports = NodeHelper.create ({
    start: function() {
        console.log('Starting node_helper for module: ' + this.name)
    },

    getLights: async function(payload) {
        var url = "http://" + payload.bridgeip + "/api/" + payload.userid + "/" + payload.lightsOrGroups;
        
        var response = await fetch(url)
        if (!response.status == 200) {
            console.error(`Error retrieving data: ${response.statusCode} ${response.statusText}`)
            return;
        }

        var result = await response.json()
        
        this.sendSocketNotification("lightsorgroups", result)
    },````

[sdetweil]

@mumblebaj he is calling from start:

but sockets not setup yet.

he really needs to wait til the module sends the 1st notification down ( what we use to send config info from module to helper)

[mumblebaj]

@sdetweil Ah, hopefully he caught that and changes it.