AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Openhab opensprinkler1/4/2023 ![]() ![]() Maybe once or twice I had to power cycle the device to get it to get picked up by the binding, but nothing that worried me enough to investigate. I haven’t had any problems with the online/offline detection, or if I did, I didn’t notice it. Overall the binding has been pretty good to me. After that I confirmed that the stations all work correctly and the currentDraw channel is now visible and provides the correct information. (I think it was the HTTP interface but it might have been the device Thing). I did notice that all the stations came online first and it took maybe a minute or so for the HTTP Interface to change from initializing to online. I had to restart OH3 but it was detected after that. I deleted the version of the binding that ships with OH3 and dropped your jar in the addons. What do others think about the binding and what should change?įirstly thank you for taking the interest in this binding and for addressing the issue with the currentDraw channel. ![]() #Openhab opensprinkler code#I think I have sorted the main bits of the code so I can finally look at adding some new features to this binding. Discovery is now done differently to remove apache commons library and they now list the IP they were found at.This was insane as it was fetching the same thing 8*4 = 32 times for a single 8 station unit if my understanding was correct. Cached the replies as the binding was making the same request 4 times for each station you had setup, so now it only fetches the state once per poll.Made the current sensor show up again in V3.Fixed the on and offline detection which meant doing huge amounts of code shuffling so this needs some testing to find any bugs.If anyone is interested in helping test some changes to this binding. ![]()
0 Comments
Read More
Leave a Reply. |