Tinkering; Like Guntering for the Connected Generation.

I added a touch screen in the Kitchen, with access to Home Assistant to monitor the House and Farm.

I like the Wavin pipe mod, simple but effective. Did you consider beam breaks? or just nothing available for Tuya eco system?

The reason why I started using Home Assistant is its ability to mix devices from different IOT eco systems which gives far more choice , also in the case of Tuya with some third part integrations its possible to control the devices locally so they still work if the cloud servers or your internet connection go down.

I've been using some image processing from my Hikvision DVR to send alerts to Home Assistant, but I'm using fairly basic cameras and it only supports smart detection on one camera and basic area detection on the others. I've the smart detection setup for the front gate and it rarely has false alarms, but the area detection on other cameras can be triggered by leaves on a windy day. I'm considering using Frigate with a dedicated processor for proper person and object detection.

Having said that, sometimes you just can't beat simple, I have a few spare PIR's lying around so might give your idea to narrow the field ago.

plan B went up in smoke, due to under rated Resistors 🔥 😧

Plans A and B will be revisited later but here is Plan C. I was avoiding this one as I thought it might not be accurate enough but initial tests are promising.

A non contact EMF sensor, surprisingly easy to make with just a resistor and a short length of wire.

Sensitivity could probably do with some adjustment, but its just a matter of using different resistor values.

Adafruit lora32u4, Has built in LoRa Module and a LiPo battery socket with USB input and battery charging circuit, I'm hoping it will be a simple job to add a small Solar panel like the micro USB ones for Cameras like Reolink use.

#define MY_DEBUG
#define MY_RADIO_RFM95
#define MY_DEBUG_VERBOSE_RFM95
#define MY_RFM95_RST_PIN 4
#define MY_RFM95_CS_PIN 8
#define MY_RFM95_IRQ_PIN 7
#define MY_RFM95_IRQ_NUM digitalPinToInterrupt(7)
#define MY_RFM95_MODEM_CONFIGRUATION RFM95_BW125CR45SF128
#define MY_RFM95_FREQUENCY (RFM95_868MHZ)


#define MY_NODE_ID 84


#include <MySensors.h>
#include <Arduino.h>




uint32_t SLEEP_TIME = 30000; // Sleep time between reports (in milliseconds)


#define CHILD_ID_LIGHT 0
#define LIGHT_SENSOR_ANALOG_PIN 0


MyMessage msg(CHILD_ID_LIGHT, V_LIGHT_LEVEL);

// EMF


int aVal=0;
int VL=0;








void presentation()
{
    // Send the sketch version information to the gateway and Controller
    sendSketchInfo("EMF Sensor", "1.0");


    // Register all sensors to gateway (they will be created as child devices)
    present(CHILD_ID_LIGHT, S_LIGHT_LEVEL);
}


void loop()
{
    aVal=analogRead(LIGHT_SENSOR_ANALOG_PIN);
   // if (aVal > 1 ) {
        VL=map(aVal,1,100,1,255);
        Serial.println(VL);
        send(msg.set(VL));
  //  } 


    


    // Sleep until interrupt comes in on motion sensor. Send update every two minute.
   //sleep(SLEEP_TIME);
}

Initial Arduino Sketch for testing. It is setup a a light sensor, as Home Assistant and MySensors don't have an EMF option.

Possible maybe, but probably not very simple or practical either. By the time you add required safety functionality for the high torque motors and sensors suitable for that sort of environment you'd be as well off building from scratch. There may well be open source projects that would provide a more suitable platform for a machine of that scale.

😁

I've worked on a few Joz robotic scrappers, they are a simple enough machine mechanically.

Building a decent DIY one though probably wouldn't be too cheap by the time you build the chassis, aquire appropriate motors and build the charging station, the electronics wouldn't actually be the hardest part, although software could be tricky but ROS would probably be a good starting place.

https://www.ros.org/blog/getting-started/#

I'd love to spend some time building a robot of similar scale but I think unless I find some sort of cheap donner machine for parts/chassis it's not likely for a while. I was thinking of a field robot for spot spraying weeds using openCV to recognize weeds like ragwort.

I don't think it would be a major issue to fabricate, but think it will be costly enough by the time all the mechanical parts are fitted.

Not sure a drone would really be more practical in practice.

Licensing for Autonomous drones is more complicated for a start.

A slow moving land vehicle for pasture weeds, would have better battery life possibly extended with solar panels, be able to carry more chemical and waste less due to better identification of weeds and better shielding due to drift. Drones probably better suited to tall craps and a slightly wider broadcast of chemical targeting problem areas of a field but probably not individual plants.

Your Automated world will still take a fair bit of administration and maintenance, I like to imagine it would leave more time for family. It could also provide more time for actually looking after the animals too, but I suppose it could go either way on many farms. I like the idea of devices for animal health monitoring as an aid rather than replacement for regularly checking and handling animals. Having recently given up working off farm, I'm beginning to wonder how I ever found time to farm.

No end indeed.

But choosing the right places may save time and animal health which ultimately may save money.

Just be careful not to allow the sheep to chew on your thingamajig! 🤣

Are all addresses static? nothing set by DHCP?

Router Address 192.168.10.1

Camera Address 192.168.10.194

What is laptop Address?

Setup is Router +++Lan Cable++++ AP ///////Wireless//////// Client ++++Lan Cable++++ PTZ Camera ?

In order for your laptop to connect from the router to the PTZ camera it needs to be in the same range 192.168.10.x

The fact that your Nano stations have IP's of 192.168.15.x shouldn't matter. This is either just their management IP's or the Bridge IP's. How did you get these IP's? Can you logon to either of the Nanostations?

You can access the camera when connected directly to AP? So the wireless link is up?

By Default traffic is not routed from 192.168.10.x to 192.168.15.x , I assume your laptop's static IP is 192.168.10.x range, so it won't be able to ping the Client CPE but should be able to ping the attached Camera.

To me it seams something has changed at the Router? is it definitely 192.168.10.1?

OK so the nanoStation IP's are the management IP's they don't strictly need to be in the same subnet, unless you want to manage them without changing your laptops subnet. They should just forward all traffic on their LAN ports across the wireless bridge to the other nanoStations LAN port. The bridge seems to work because you can ping the camera.

For local network traffic DNS servers are not needed as they translate Domain names into IP addresses, you are already working directly with the IP addresses. Likewise the default gateway is the gateway to the internet i.e. your router so only the camera needs this and it should be your router IP.

I'd bring the laptop out to the client nanoStation and try the opposite, disconnect the CCTV and see if the Laptop can reach the router and the internet using the 192.168.10.x network and the client nanostation using 192.168.15.x network.

As for reaching the camera with its IP but not the client software, if the camera is setup using P2P then it must have an internet connection before the client software will connect as it uses a remote server to handle this connection even when used on the same LAN.

Another thing to try is bring the camera to the router and plug it in to make sure it is not the issue. You could try a different DNS server on the Camera like googles 8.8.8.8 and 4.4.4.4

Just to rule out, the new ISP owner did not replace the router by any chance? They could also be blocking certain types of traffic, but that wouldn't affect the local traffic.

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