Now that I received my Twists yesterday, I wanted to make use of them in Home Assistant. But alas, SDK does not support a single bit of the twisting and even in the app, I cannot use a HTTP request. Why must this be limited to the very few providers?

I am disappointed

@Emil Wish list with priority for Twist:

• SDK - as it makes everything else possible
• Home Assistant support (wonder why this is already shown on the App page but not available in the Android app... strange)

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?

@claudia thank you so much, that feature was my wish now for ages. I am very happy that you listen to your customers.

Now that I received my Hub Mini just yesterday, I realized that it does not support the SDK. As my smart home is all Home Assistant, I wonder if I bought the Hub mini for nothing. Any hints?

Joachim

PS: I know, I probably could have found out about the lack of SDK support, but when I supported the Twist + Mini on Kickstarter, I wasn't using the SDK yet.

@r_esben I can confirm as well. I have now 3 dead buttons from the very first batch some years back. They seem to get stuck somewhere. I imagine some electronics broke down and is now not able to restart after the shaky battery change. As an electronics engineer i always feel bad when replacing the battery as the connection is going on and off and on and off and on, until I finally have the flic attached again to its base. Maybe this is something the aged buttons don't like anymore?

Any recommendations on how to replace the battery in one go without the shaky connections inbetween?

@abboberg Thx, and I do know that and used it in the past. I guess I forgot about this one. So much for remembering things. Of course, this means I need to configure each and every butten separately by hand instead of using the SDK for the whole hub.

Thx anyway!
Joachim

@Emil Wish list with priority for Twist:

• SDK - as it makes everything else possible
• Home Assistant support (wonder why this is already shown on the App page but not available in the Android app... strange)

Hi Steve and Johan,

do you know of this site?
https://community.home-assistant.io/t/flic-hub-sdk-web-hook-step-by-step/390655

I successfully use this very simple approach with a matching automation
on Home Assistant.

Good luck!
Joachim

PS: Missing SDK support on the hub mini annoys me, just as the lack of Twist support in the SDK as of now. I wonder why the latter one is not just there - seems so straight forward to an outsider like me.

Now that I received my Hub Mini just yesterday, I realized that it does not support the SDK. As my smart home is all Home Assistant, I wonder if I bought the Hub mini for nothing. Any hints?

Joachim

PS: I know, I probably could have found out about the lack of SDK support, but when I supported the Twist + Mini on Kickstarter, I wasn't using the SDK yet.

Now that I received my Twists yesterday, I wanted to make use of them in Home Assistant. But alas, SDK does not support a single bit of the twisting and even in the app, I cannot use a HTTP request. Why must this be limited to the very few providers?

I am disappointed

@claudia thank you so much, that feature was my wish now for ages. I am very happy that you listen to your customers.

@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?

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?

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 762a:9c:c8:38 via enp0s31f6
Jan 6 16:31:22 xxx dhcpd[6493]: DHCPACK on 192.168.2.240 to 762a:9c:c8:38 via enp0s31f6
Jan 6 16:32:26 xxx dhcpd[6493]: DHCPREQUEST for 192.168.2.240 from 762a:9c:c8:38 via enp0s31f6
Jan 6 16:32:26 xxx dhcpd[6493]: DHCPACK on 192.168.2.240 to 762a: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.