Flic Hub

• 

  Is firmware using DHCPRequest instead of PING by mistake?
  flic hub dhcp requests • • yea  

  13
  0
  Votes
  13
  Posts
  319
  Views

  

  Before test, I configured DHCP and set lease time to 1h. Rechecked FW 3.0.9, DHCP REQUEST flood occurs exactly after 30 min, first re-lease timing. In FW 3.0.10, after 30 min, only 1 pair of DHCP REQUEST- DHCP ACK is logged... works as expected! As far as I watched 3 times re-lease process loop, looks stable. Thanks @emil, finally my flic buttons back to network! Hope this FW solve @yea's and @Djelibeybi's problem too.
• 

  Cant connect to hub with Fold 3
  • oskaremilsson  

  6
  0
  Votes
  6
  Posts
  19
  Views

  

  @oskaremilsson yup. Erm. So.. this is awkward. The phones BLE scanner must have gotten stuck in some bad state. A restart of the phone worked 🤦‍♂️ Didn't cross my mind that the issue could be that deep into the system. As a dev I should've tested that as #1 though 🙃 Thanks, and sorry! 😅
• 

  How do you manually set a static IP address on the Flic Hub?
  • dead.beat.native  

  1
  0
  Votes
  1
  Posts
  55
  Views

  No one has replied

• 

  eWeLink compatiabiliy
  • paul 1  

  4
  0
  Votes
  4
  Posts
  300
  Views

  

  @Emil I don't have Alexa.. here's the device info https://sonoff.tech/product/diy-smart-switch/micro/
• 

  Flic IR
  • elisalant  

  1
  0
  Votes
  1
  Posts
  63
  Views

  No one has replied

• 

  This topic is deleted!
  • jitmo  

  1
  0
  Votes
  1
  Posts
  1
  Views

  No one has replied

• 

  'Error Not Authenticated' on Update Firmware from 3.0.3
  • john.hind  

  5
  0
  Votes
  5
  Posts
  189
  Views

  

  @Emil Thanks: whatever you have done seems to have worked. My hub updated successfully to 3.0.9 and Alexa integration now seems to be working.
• 

  HTTP Home Assistant API
  • ff0000wizard  

  3
  0
  Votes
  3
  Posts
  200
  Views

  

  After refreshing the entire process and starting over (including adding more fluff to my curl command) curl -k -X POST -H "Accept-Encoding: gzip" -H "Authorization: Bearer SECRETTOKEN" -H "User-Agent: Google-HTTP-Java-Client/1.23.0 (gzip)"-H "Button-Serial-Number: SERIAL" -H "Button-Battery-Level: 53" -H "Button-Name: Flic2" -H "Timestamp: 2021-05-25T23:03:26Z" -H "Accept: */*" -H "Content-Type: application/json"-H -H "Cache-Control: no-cache" -H "Pragma: no-cache" -H "Connection: close" -d '{"entity_id":"input_boolean.flic2_singleclick"}' https://HOMEASSISTANT:8123/api/services/input_boolean/toggle To get almost matching posts (using a local netcat Listener on Port 8080 (ncat.exe can be found with nmap on windows installations) c:\PATH\TO\ncat.exe -l -p 8080 Somehow this last time around of starting all over from scratch worked, I can only assume that something was messed up in the Authorization header that was having issues (the string is so long you cant even see the delete button). I honestly have no clue why it is now working considering i've set up and deleted these api requests a couple times even with new tokens. For anyone who comes across this in the future or has issues/wants to integrate flic button HTTP requests to the Home Assistant API I will leave some notes. (this is running off a new install for a home-assistant VM). Configuration.yaml file: #flic v2 buttons input_boolean: flic1_singleclick: name: flic1_singleclick icon: mdi:checkbox-blank-circle flic1_doubleclick: name: flic1_doubleclick icon: mdi:checkbox-multiple-blank-circle flic1_hold: name: flic1_hold icon: mdi:clock input_boolean: flic2_singleclick: name: flic2_singleclick icon: mdi:checkbox-blank-circle flic2_doubleclick: name: flic2_doubleclick icon: mdi:checkbox-multiple-blank-circle flic2_hold: name: flic2_hold icon: mdi:clock Adding by Entity in the lovelace UI creates visible toggles and these can be used by Node-Red to trigger whatever you want (including MQTT messages or other triggers) Flic button Settings: Post URL: https://HOMEASSISTANTLOCATION:8123/api/services/input_boolean/toggle add a Header String with the following information Key: Authorization Value: Bearer LONGLIVEDAPITOKEN Body: {"entity_id":"input_boolean.flic2_singleclick"} Content type: application/json Timeout:10 Validate Certificates: Toggle yes (do this only if using https with a valid cert and using FQSN/DNS) Here is an example on how to get that data into node-red and making changes for an example i am using the wled2 library to change to colors on a light strip. EXAMPLE NODE-RED : The Event State node is what is used to pull the boolean value. This leads into two change nodes that set the msg.payload to either red or green based on the boolean value of true or false. (also included are 2 Debug nodes to make sure the msg.payload actually changed before it hit the switch). This leads to a switch node that sends a signal based on the msg.payload being either red or green. If red it uses the WLED2 library to set the lights to red.
• 

  Revoke of access for third-party apps
  • miko  

  1
  0
  Votes
  1
  Posts
  81
  Views

  No one has replied

• 

  Chromecast Play/Pause is not working
  • gango0  

  6
  1
  Votes
  6
  Posts
  313
  Views

  

  We have rewritten the Chromecast integration from scratch. We'll send out a new firmware update in the upcoming days. This should fix the isuse.
• 

  Flic Hub - Http Request
  hub http request • • arnaud.perray  

  16
  1
  Votes
  16
  Posts
  9277
  Views

  

  @theo I think you need to add the http:// prefix to the url.
• 

  Flic 2 button goes into standby mode
  • simonwjorgensen  

  2
  0
  Votes
  2
  Posts
  145
  Views

  

  Hi. Please use https://flic.io/support for support questions.
• 

  Flic LR range?
  • matt 2  

  6
  0
  Votes
  6
  Posts
  415
  Views

  

  @xAPPO you can have a flic paired with two hubs. When pressing the button it will simply connect to the first one that responds. The hubs otherwise don't "talk" to each other.
• 

  Seems the FLIC HUB is easily infected with malware.
  • dead.beat.native  

  2
  0
  Votes
  2
  Posts
  177
  Views

  

  Everything runs from a read-only system, so i doubt malware has gone into it. Probably just some bug in the widely used Linux OS we run on it if anything. I would be glad if you could share Wireshark logs or something of the packets you are seeing.
• 

  Hub communication with external bluetooth devices
  • simonwjorgensen  

  2
  0
  Votes
  2
  Posts
  99
  Views

  

  It has a built-in Bluetooth Classic radio inside the wifi chip, but for now we are not using it for anything. Maybe in the future.
• 

  How to use my flic buttons with Homekit AGAIN ?
  homekit hub resetting • • business2  

  1
  0
  Votes
  1
  Posts
  157
  Views

  No one has replied

• 

  Flic ir blaster signal doesn’t turn on/off old philips tv
  • A Former User  

  1
  0
  Votes
  1
  Posts
  102
  Views

  No one has replied

• 

  "Could not add user to Hub" - Not working and persistent alert in iOS App. Please help.
  hub troubleshoot add user • • stockers  

  21
  0
  Votes
  21
  Posts
  1191
  Views

  

  Hi @Emil , Thank you. I confirmed at the site visit and this was not our problem. We just weren't connected to the wifi. Thank you for looking into it!
• 

  New WEMO plugs not being recognized in the flic app
  • adam.hamel  

  7
  0
  Votes
  7
  Posts
  286
  Views

  

  @Emil awesome my phone is working with it. When does the flic hub update comes?
• 

  This topic is deleted!
  • Swedishflicker  

  1
  0
  Votes
  1
  Posts
  1
  Views

  No one has replied