When the OPNpool device connects to the WiFi access point, it will be assigned an IP address. Only the access point and the device know this address. Other hosts can access the device by its mDNS name opnpool.local.
This relies on service auto-discovery using the Multicast DNS (mDNS) protocol. Note that mDNS’ use of multicast packets is designed to work within a single IP subnet. That implies that in general your computer/phone need to be on the same subnet as the OPNpool device for the mDNS protocol to work.
HTML
As you may have seem in the video in the Deploying chapter, the OPNpool device can be controlled through a simple HTML UI. This allows the user to monitor the state of the pool controller, pump and chlorinator.
This UI is accessed through the URL http://opnpool.local/. The unsecure connection implies that security solitary relies on your WiFi credentials. If you want to access the device from the public internet, I urge you by tunneling into your LAN instead of simply opening a port on your router.
To conserve memory, the OPNpool device only contains the minimum HTML code that refers to an external site for the Stylesheet and the replacement element that refers to the JavaScript.
Some examples of the UI are shown below
The raw state of the pool controller is accessible through
The IP address of the OPNpool device can be found using the
Notes on going dark
data-theme="a" data-content-theme="a" to data-theme="b" data-content-theme="b" in replace-body.js, and
.rs-bg-color from white to #2b2b2b in index.css.
data-theme in the HTML , and
JSON
http://opnpool.local/json. The HTML page uses this internally, but you can also poll this state from home automation systems. However, if your home automation supports MQTT, I suggest using MQTT as described in the Home Assistant chapter.
http://opnpool.local/json
Who
http://opnpool.local/who page. An example is shown in illustration below.
http://opnpool.local/who