Posts made by abboberg

@Emil i added a request

I have four Flic2's connected to the FlicHubLR.
One of my Flic2's is draining any battery.
Normally i use normal noname CR2032, last time i used an expensive Duracell CR2032. But even that battery was low in a few weeks. It is located about 5m from the hub.

In the mean time i also reset my FlicHub and had to re-assign all my Flic2's to the hub (in the app).
The other three are working fine and one of them i replaced the battery a month ago. No problems since.
It is even further away from the hub and on another floor of my house.

What could be wrong with the Flic2? Is there a debug-mode to see if / why it is on all the time?

It works!

The problem was

• old firmware (could not update myself)
• with new firmware the 'sdk-switch' in the flic-app was turned off, by default
  -> red dot in the sdk-login-screen
• turning sdk-switch to on
  -> green dot in the sdk-login-screen
  -> login works!

thanks @Emil for the directions

@Emil a red dot! That is on the login-screen, next to the found Hub with its IP-adress

@Emil I am now on Hub version (firmware) 3.0.10. But still 'Could not connect'.
Tried on Brave-chrome-browser (with shields off) and Edge.

update:
did a hardware - reset, deleted flic2-buttons and hub from the app
reconnected to the FlicHub, added a button to the app (firmware was not changed)
connecting with password from the back of the hub; logging in with the app works
entered wifi-credentials again, at router (and in app) new ip-adres visable
but still message 'Could not connect' when logging in @ flic.io

same from desktop (wired lan) as mobile phone with Chrome

After an unexpected power-down i can't login to the SDK.
I did not change the Hub-password (at the back)

I do get login-screen at https://hubsdk.flic.io/ and Hub is detected.
After putting password in there is a message 'Could not connect' in a red box.

With the app on my phone i can connect to the Hub.
I am using firmware 2.0.19-sdk2
There is an option/button to change the password .."succesfull changed",
but still the 'Could nog connect' message at sdk-login.