hubsdk.flic.io is currently down

james.korzekwa

hubsdk.flic.io is currently down. Please fix this.

Emil

@szczepan-kuzniarz Thanks! The new ES version is more strict that "new" must be placed before a constructor. We have just released a new firmware update that is more relaxed regarding creations of new Sockets, as a workaround for users of that lib.

szczepan.kuzniarz

@Emil I use the MQTT publisher from https://github.com/id628/flic2hass. It constantly writes to console following error:

Error: Crashed
    at <anonymous> (root/MQTT/main.js:226)
    at runNextTimeout (core.js:964)

and the underlying exception is:

TypeError: class constructors must be invoked with 'new'
    at Socket (core.js:1158)
    at <anonymous> (root/MQTT/mqtt.js:418)
    at <anonymous> (root/MQTT/main.js:230)
    at require (core.js:2895)
    at requireMain (core.js:2903)
    at handlePacket (core.js:2937)
    at onPipeData (core.js:2974)

It seem the line 418 in mqtt.js:

client = require("net").Socket().connect({ host: mqo.server, port: mqo.port }, onConnect);

has to be changed to:

const net = require("net")
...
client = new net.Socket().connect({ host: mqo.server, port: mqo.port }, onConnect);

Emil

The website is up and running now. We have upgraded the js engine to a new modern one. If your previous code is not working, please share it.

szczepan.kuzniarz

In my installation SDK-based MQTT communication is the only way I use Flics, so now it is completely useless I suspect there was some Matter related update, that broke the SDK functionality.

sakari.bergen

All my SDK-based actions also stopped working yesterday, which seems related. I'll be very curious to know what happened, as I thought everything should be running locally.