I received my almond today, but I'm not thrilled about how the device operates. I have a cable modem, firewall, switches and everything else a network needs to have functional networking, and wanted the almond+ to provide functionality for wifi and z-wave stuff. The way the default almond operations works is it has a lan segment with multiple ports and a wan segment with a single port. I guess the idea is that you would connect the almond+ WAN port to your cable modem or other network gateway directly, and then connect your hosts behind it on one of the LAN ports.. The problem is, I have real switches hooked up to a firewall hooked up to the cable modem, and I don't need the almond+ to be in between these communications. I have placed the almond on a dmz switch that connects to a port on my firewall allowing wifi clients a path out and in. I have disconnected the WAN port, and added a static route (for default) on the almond+ so that the wifi clients and the AP itself knows what path to take to other networks.
The problem is, the almond+ website/software expects the clients to egress through the WAN port. I wouldn't even care ultimately, if I could add sensors to the device using the web interface through the LAN connection, but I can't. With the LAN port disconnected, the website doesn't see my almond+ as online, and won't let me do anything with the sensors I have. There must be some way to tell the almond+ to connect to the external website VIA the LAN interface, so that functionality will be available when I need it. How do I do this?
Also, it would be great if we could add sensors to the device from the web management console.