@Monocle said in Cannot get it Working :-(:
@Alarm_guy1
Based on the log the gateway is still not receiving inbound requests from Alexa.
From another computer (not the gateway) try to perform a NSLOOKUP command using the FQDN (ea400744-dbb9-4a49-864a-2f31f366xxxx.mproxy.io)
nslookup ea400744-dbb9-4a49-864a-2f31f366xxxx.mproxy.ioIt should resolve to your private IP address where the gateway is running inside your network.
Is the HOST address (192.168.x.x) reported at the beginning of the log the correct IP address for this machine? The Monocle Gateway will attempt to automatically detect the IP address but sometimes if there are multiple addresses associated to the computer, it can assign the wrong one.
Are the Alexa devices are the same network as the Monocle Gateway … meaning they are not on a Guest WiFi network or isolated VLAN? The Alexa devices will need to communicate directly with the gateway on the local network.
Thanks, Robert
Right back on this for today anyway:
nslookup.jpg
The nslookup results posted.
The only issue I think is I have a Ubiquity Unifi WiFi extender but the as my router now doesnt have built in WiFi.
the Pi that monocle is on is hardwired into a switch that is connected to the switch that the Unifi is connected to…
it would be good to get this going :-)
cheers for the continued help