Tinkering; Like Guntering for the Connected Generation.

There is something not right at your router/ between your router and the AP

You can ping the camera with laptop directly connected to the AP using the 192.168.10.x address so the wireless bridge works, logically the wireless bridge is a replacement for a cable and it does this. Really the IP addresses on the nanostations are only needed for administration of them (they actually probably have another separate subnet to talk to each other). Aligning them will be no harm but just to make administration easier in future.

But with the Router connected you can't connect, in this scenario the router is not actually acting as a router at all (as in no data is being routed out of the home network). The router is doing two functions though,

1 it is acting as a switch and as such connecting the AP and the laptop to the routers switch ports should work the same as connecting directly to each other. You hardly have a cross over cable in your setup? These can cause issue with some devices, but "most" modern devices can automatically detect a crossover using Auto-MDIX (check the cable between router and AP that the plugs on both ends are wired exactly the same order)

2 the router is acting as a DHCP server, when you connect your laptop to the router do you still use the static IP or the DHCP assigned one? If DHCP what IP is it getting. Also try pinging the camera IP address with AP disconnected to rule out an IP address conflict with something else on the network. If you are using DHCP addresses and static addresses then the static addresses should be excluded from the DHCP address pool.

If in doubt with IP Addresses for any devices its probably best to:

Keep all subnet masks the same: 255.255.255.0

Gateway Addresses to your Router address (its your gateway to the internet)

DNS can be set to your routers IP, your ISP's DNS or any public DNS like Googles 8.8.8.8

Use the same subnet for all devices that you want to communicate

I've some cheaper brand CPE's here, 4 of them linked, none of them with the same subnet as the rest of the network. By default they also setup as one AP and 3 clients and form a layer 2 PTMP connection. I however have switched on AP mode on all of them so they can each act as an access point for other 5Ghz devices.

TP-link is just a brand of consumer grade IT equipment.

Look up any Ubiquity Nanostation Manual for setting up a layer 2 Bridge, the basic setup is one CPE set to AP with PTP on and the second set to Client with PTP on. Since we are talking about nanostations one can indeed be a Wireless AP and the other a Wireless Client and still form a network bridge.

Yes layer2 works with MAC address's and is IP agnostic, hence a layer 2 bridge joins 2 networks to make them appear like one network at layer 2 level.

But you are right about the circles, and the other poster had already decided he was going to move them all to the same subnet anyway.

I'm integrating farmOS with Home Assistant, so I'll have all camera feeds, sensors and farm management database accessible from a single portal.

The Home Assistant Node Red Addon is proving useful for automating farmOS tasks and importing / exporting data to other applications such as Google Calendar.

The flow above will read Google Calendar events with the term 'Cow Serviced {{Cow Number}}' and create 2 log entries in farmOS database one for Serviced Date and one for Due Date as well as create a Due Date entry in Google Calendar.

The flow can also enable some flags so the details can be verified later.

I'm also considering adding Live data beneath camera feeds, with information such as cows in pen and due dates.

I realize some of the cameras above are a bit wonky, but I'm setting up some new pens this week.

Technical enough, but if you are an IT consultant I'm sure you could figure it out. From a setup point of view it is a webserver so knowledge of maintaining a webserver with database would help. Mine is running on Docker on a Raspberry Pi, here is my initial setup https://farmer-eds-shed.com/farmos-version-2-raspberry-pi-install/. (other installs are probably more straight forward.)

There isn't necessarily a need to know any code for basic record keeping, but it can be lacking in some features specific to a livestock farm in some ways compared to some of the more well known livestock focused packages available, however it does have an API with options to interface in a number of ways including Python, Java script and Json:API. It is also free and open sourced with good support from the main Developers on https://farmos.discourse.group/. Most features it is lacking in can be more than made up for with a little coding knowledge, I'm experimenting with Node Red the last few days which is a good low code solution. It doesn't currently sync up with the DAFM AgFood portal, so I'm going to put something to work with the CSV files for importing Data.

They also have a paid hosted version https://farmier.com/

Do you mean if you create a custom module and then a farmOS update potentially breaks it?

My understanding is that it shouldn't be an issue for a long time, farmOS 2 is a distribution of Drupal 9 and modules and API's are all built to Drupal 9 standards. They have just migrated from farmOS 1 which was based on Drupal 7, there were breaking changes in regard to custom modules and even the API after that migration but its not expected with the regular upgrades of farmOS 2.x.