Community

flic r

@xAPPO thx for asking. I started out with the following MQTT implementation (without having tried anything yet):

https://www.npmjs.com/package/mqtt/v/2.9.0#browserify

I couldn't find a simple "publish" javascript implementation for use - that would have been my ideal solution.

Any ideas or hints?

flic r

I checked out the JavaScript mqtt.js module but that comes to a total of 16.000 lines of JS code and as I am not an expert in JS programming, I was wondering if it is really worth to copy&paste this into the module on the hub and try to get it running from there.

My purpose would be just to publish MQTT requests directly to a MQTT broker. Nothing fancy. (this would be better than using a HTTP-to-MQTT gateway).

Any hints?

PS: Better would be to have MQTT already there.

PPS: Node.js is the basis for the SDK, as I understand, so why not implement MQTT from Node.js as well?

flic r

I observe the same thing with repeated DHCP requests from both flic hubs I am running. I run a regular debian based isc-dhcp daemon on the server, and no issues except for flic hubs. Something is strange with the flic hub implementation.

@Emil: can you elaborate on what flic hub expects? Is it possible that flic hubs expects an answer from the Wifi router? In my case, and possibly in yea's case, the DHCPD is running on a different machine, so the MAC address could be different.

Here an example:
Jan 6 16:31:22 xxx dhcpd[6493]: DHCPREQUEST for 192.168.2.240 from 76:ee:2a:9c:c8:38 via enp0s31f6
Jan 6 16:31:22 xxx dhcpd[6493]: DHCPACK on 192.168.2.240 to 76:ee:2a:9c:c8:38 via enp0s31f6
Jan 6 16:32:26 xxx dhcpd[6493]: DHCPREQUEST for 192.168.2.240 from 76:ee:2a:9c:c8:38 via enp0s31f6
Jan 6 16:32:26 xxx dhcpd[6493]: DHCPACK on 192.168.2.240 to 76:ee:2a:9c:c8:38 via enp0s31f6

The DHCPACK comes right away. Is it possible, that the server is to fast for flic hub to get the message?

Thanks for any pointer. It is really annoying to see all this internal traffic.

flic r

@flic r

Posts made by flic r