This project has a multitude of features, but I really only used the irrigation features. SIP is focused on irrigation, so it was a better fit for me and it was also easier for me to contribute new features.

Yes, I was able to reuse all my hardware, depending on the hardware and features you use your mileage may vary though.

I have moved on to using Sustainable Irrigation Platform

Documentation? In my opinion there is never enough of it. Testing?

I agree, this is such a feature rich project that it would be a pity to see it fold considering the amount of work that has been put into it so far. In order for this project to continue I think it would require about half a dozen contributor (not only for coding but also for testing and documentation). I also think introducing a plugin system around an event handler like, for example, MQTT would make it very open and flexible for contributions. If the owner (Angelo?) does not have any/much time for the project any more/at the moment may be they would consider spending a little time to coordinate the work? I know a little Python but I have not really dug into the code much: I would however be willing to contribute. Would it make sense to start another discussion with a title like "Contributors required" or does the fact that there are no further responses speak for itself?

I will give your suggestion a go next week when I have a little more time and report back. According to https://www.json.org/json-en.html "123" is valid JSON.

Topic: 325A272640/io2 Value: "123"

I'm trying to reconfigure a moisture sensor. In the Hardware Configuration I'm trying to replace the path tele/HygroWiFi01/SENSOR//ANALOG/A0 with the path 325A272640/io2 The second value is a string not an integer

I have a PI Zero W with a Wifi Stick attached to the USB port.

I hope I'm not being too quick here, but I think I have solved the problem. Looking at the code, it seems that it is very opinionated in its network handling or rather its handling of wlan0. The code does its best to (re-)start wlan0, so trying to suppress this with "denyinterfaces wlan0" in /etc/dhcpcd.conf or an "@reboot ifdown wlan0" entry in the crontab does not work. The solution to this was setting "WiFi Enabled/Disabled" to "true" on the "advanced setting" page. This does not stop wlan0 being started, but somewhere along the way it is in fact disabled. Setting "Access Point time (sec):" to "0"on the same page does not in fact stop the AP from being started, but will limit its life span so less than 60 seconds after a reboot. Setting the "WiFi IP Address" to "192.168.1.4" on the same page stopped the code from trying to set the IP address to "192.168.1.172" and thus making the Pi Zero unreachable. Finally, disabling IP6 in /etc/sysctl.conf stopped the following and I presume the code trying to reset the IP address to something again making the Pi Zero unreachable hydrosys4.selectedplanmod - INFO Target IP address= 192.168.1.4. Current access point IP addresses= 192.168.1.4 2a02:8070:a28f:1300:2b83:69d2:e126:b47e So now all the inbound and outbound network traffic is limited to wlan1 which has decent connectivity to the router.