search

dlashua / ewelink-mqtt

Connect eWeLink Cloud to MQTT
11 stars 2 forks source link

ReferenceError: log is not defined #1

Open andres934 opened 5 years ago

andres934 commented 5 years ago

I'm trying to build the project with the config, when i run i get:

`log("Initialization skipped. Missing configuration data."); ^

ReferenceError: log is not defined at new eWeLink (ewelink-mqtt\node_modules\node-ewelink-cloud\index.js:17:9)`

i build the myconfig.js as said in the example, but no luck

dlashua commented 5 years ago

It looks like there's a bug in the node-ewelink-cloud library that is causing it to be unable to report the error to you correctly. I'll look at it and get it fixed. However, in the meantime, if you fix the error in your configuration, it should still work.

The following configuration elements need to be supplied, at a minimum: email password imei mqtt

andres934 commented 5 years ago

thank you for your response, i already fill the myconfig.js file with those fields, but still the same

andres934 commented 5 years ago

nevermind i found what was causing it, edited the config.js too

andres934 commented 5 years ago

is the library capable of detecting RF Bridge events and send the notification to mqtt?

dlashua commented 5 years ago

I'm not sure. I don't have the RF Bridge device, so I don't have it to test. This library literally exposes everything that is shown in the API to MQTT. Beyond that, it doesn't do much else. So, if the data you want is in the cloud API, then it should be available in MQTT as well once this is running.

andres934 commented 5 years ago

For now the only way i could see that listener can work is with actual data on the Cloud Api, get your get devices, if a bridge is available, you can see last trigger of the bridge by what device, so maybe listening on that "last trigger" change, could be a way