@jasperruijsink When you connect a cable, you get an automatically assigned link local IP address, starting with 169.254. The DHCP server, typically running on a router, is then going to assign an available IP address to the hub. If it has no available IP address (i.e. it has run out of addresses) or otherwise doesn't give the hub one, the hub will stuck with its link local IP address.

The Hub LR runs https://github.com/NetworkConfiguration/dhcpcd, which is one of the most commonly used DHCP clients and should work with most routers or DHCP servers.

If nothing works, I suggest you to try another router, or factory reset the router and/or the Flic Hub.

@Emil Did you also add the "Copy config" function - or did I just miss it, when I suggested a backup function?

@treegartner
Seconded.. I had a reply about a bug fix in latest FW but no reply from Flic?

I made an update to our server. Please try again now.

@Emil Thanks for explanation.
Works now...
I also managed to figure out what JSON structure is going for MDM under point 3.
Basically I export pairings from dev hub and if we use those buttons on managed hub I just paste "buttons pairings" json in to the field.

@antonio-mestre the net module implements just a raw TCP socket. The secure web socket protocol uses the Websocket protocol on top of the TLS protocol on top of the TCP protocol.

Right now our sdk unfortunately does not include modules for TLS (but we have https) nor Websocket, so you would have to implement that yourself if you want to use wss, using the net module in the bottom for TCP.

@Emil said in Is firmware using DHCPRequest instead of PING by mistake?:

Hi. I have applied the patch you linked to and built a new firmware for Flic Hub LR.

@akiraK @yea @Djelibeybi please give me the serial numbers of your hubs so I can assign the new firmware if you want to test it, to see if the patch works.

@mattias-0 Why can't I use any of the flic/Wyze applets already posted. I have flic2 so I guess that's my answer but why can't your interface detect which type of flic is being pushed? I assume there must be a difference but I don't see anything to help me. What I'm trying to do is simply turn on/off a Wyze smart plug. When I try to create this I add "flic" from your menu of stuff to the "if". For the "this/then" part I add the "Turn on Wyze plug". Now I get asked to select "Options" NADA can't do anything. Tried using a Tagged flic whatever that means, doesn't ask for any options and I get "Finish". I click that and I get to title my applet which I did. Now I get "Can't create Applet, try again later". What the hell is going on? I should not have to worry about whether I have a flic or a flic 2 YOUR interface should be able to detect and take care of that, why should I? If you want your stuff to make it in this market you need to SIMPLIFY things. I have 38 years of programming experience. I could dig into this and probably figure it out, is that what you want the average Joe off the street with no programming experience to do? YOU WANT THIS TO BE EASY FOR ANYBODY, OTHERWISE YOU WILL NOT MAKE IT!

@leonardchrist I know I'm super late to the party, but the fact that the hub never ACKs the SYN ACK, plus the fact that it then re-xmits the SYN makes it seem like it never gets anything back. A couple obvious things to check would be the SN mask, and any possible ACLs/VLAN config on the switch ports. Alternatively, you could swap the PC/Hub switch ports and see if the behavior changes at all.

Alternatively, you could take a deeper look at the SYN ACK from the PC and compare it to the successful equivalent from the WiFi scenario. Hardware failure on the switchport, or hub, might cause it to fail MAC checksums.

I would like to reply that I totally agree with you. I also hoped for the hub and/or app to bee open to load/play sounds you have got on the phone or desktop (by hub). The fart thing is really funny and the preload sounds are good for a small time. I see no reply anywhere if this feature is going to be integrated. I guess this would be THE biggest improvement for all types of entertainers in the field.

I am attempting to integrate the flic button using the flic hub with noonlight API.

This is what I need to pass to noonlight using the flic hub:

curl --request POST
--url https://api-sandbox.noonlight.com/dispatch/v1/alarms
--header 'Accept: application/json'
--header 'Authorization: Bearer AO3yovlMivKQrNLp72cH5QRLoazSbMxS'
--header 'Content-Type: application/json'
--data '{"location":{"address":{"line1":"1234 Street Ave.","city":"East City name","state":"AL","zip":"92310"}},"services":{"police":true,"fire":true,"medical":true},"instructions":{"entry":"0000"},"name":"John Smith","phone":"15555555555","pin":"0000"}'

How would I format this in the flic internet request ?

Also with a web hook on the hub, like a private IFTT.

Hey Roberto, I've got it working just fine.
I assume your phone can find both the Tradfri and Flic hub?

You might want to check if both hubs are on the same network (especially if you use them over WiFi and have more than one Access Point).
I've actually connected both hubs over ethernet to the same access point (just worked out that way) but you might want to try over cable in case the above doesn't help...

Good luck!

Joey