![]() The Pi is indoors, and the wires run through the wall. The sensors are outdoors in a small actively-ventilated enclosure I made. It's also connected to a Dallas 18B20 temperature sensor. I have a Pi connected to a BME280 breakout board that I got from Adafruit ( ). Primary motivation to do the project was so that wife can have pice of mind knowing plants are taken care of while we are away on longer trips. (though I just bought my when visiting Fry's) Non-contact Liquid Level Sensor -XKC-Y25-NPN. Key parts I ended up using for the project:Ģ. saves all metrics to sqllite db for future reference summarizes watering event and sends me notification with link to the recording and other helpful stats (temp, humidity, moisture level etc.) uploads recorded video automatically to youtube channel (if pi has internet connection) activates camera to record watering (+2s buffer to have all on the video) via usb cam connected to the pi (leveraging opencv lib) Watering duration is determined by current soil moisture level Python script activates relay to run the pump for the right duration. Soil moisture level is below certain threshold (measured by 2 soil moisture capacity sensors embedded in the plant)ģ. There is water in tank / source (checked by non-contact liquid level sensor)Ģ. Triggers for watering plant are defined as follows:ġ. ![]() Water pump is connected to a clear vinyl tube for water distribution to the plant.Īvailability of water level at source is checked by a non-contact liquid level sensor. Last night I tried adding a SmartApp to set up the static IP, and to register a child device – but no success with that so far.I'm using a cheap submersible water pump controlled via relay by a python script running on raspberry pi. … the RPi responds to the POST request over the network (via telnet from a mac) so that’s working … In the ‘My Devices’ list, the RPi shows as ‘INACTIVE’ – but so does a working power outlet, so that’s confusing.ħ:45:40 AM PST: debug POST /macros/getData HTTP/1.1Īuthorization: Basic d2ViaW9waTp3ZWJpb3Bpħ:45:40 AM PST: debug Executing hubAction on 10.0.1.225:8000ħ:45:40 AM PST: debug Headers are ħ:45:40 AM PST: debug Credentials are Basic d2ViaW9waTp3ZWJpb3Bpħ:45:40 AM PST: debug ASCII credentials are webiopi:webiopiħ:45:40 AM PST: debug Encoding credentialsħ:45:40 AM PST: debug Device Network Id set to 0a0001e1:1f40ħ:45:40 AM PST: debug Executing ‘refresh’ – do you expect it to be set by the device code? I added it manually, trying both upper and lowercase. Thanks – the hub is ‘home’ like the rest, and the device network ID is shown. I’m wondering if something changed with the hubAction call.īTW, I can take the POST request from the live logging screen and send it via telnet to webiopi on the Raspberry Pi, and get a sensible response – so that should work if the request ever got sent from the SmartThings hub. The only traffic is https between the hub and the SmartThings cloud at AWS. ![]() ![]() There is a packet sniffer + wireshark watching the link between the hub and my switch. The IP and port appear to be correct in both ascii and hex, and credentials are correct. I uncommented the extra debug lines – so in the ‘live logging’ screen, I can see that the ‘refresh’ button triggers the device to create a valid POST request to send, but the packet never makes it out of the hub. The device shows up in in the app, the RPi side seems to be working, but I don’t see any packets coming out of the hub. ![]() Unfortunately, it doesn’t quite work for me. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |