Electricity Bill Module Development

[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.