So the wifi by my mixing station has always been a problem, even when I had the prototype Star connected to my little access point bridge. Now with the Cloud hub, it's become more annoying. At least with the standalone controller it would do its thing, with or without wifi. Anyway, I'm going to work on a script to reboot it with IFTT that I had working previously with the Dlink power plug I have attached to it. At the same time, I've ordered the Netgear Orbi AC5000. So hopefully some improved wifi signal will help.

Pegboard is here and Roberto gave me some test code for non-blocking connection to the portal.

Now to integrate that into the WiFIAlert class...

Also, I've been playing with an OpenWRT access point. Before we had the remote upload feature in the Bootloader, the plan was to use one of these to download from the portal and burn the firmware. As I sometimes need to test library code, I think I'm going to hook this up permanently with the new controller so I have the ability to do that without ripping out the controller to hook up to my computer. I think I'm going to get another one for the cloud hub too.

Basically it just becomes a little Linux box in order to run avrdude or maybe I'll use it for a Serial Monitor if I need to debug things too

Well having a serial monitor and a way to test the libraries and being able to do it when this box is upstairs is great. The OpenWRT device is definitely nice addition. I ordered one for the cloud hub as well.

I integrated the code Roberto gave to me into the WiFiAlert class. It now can do both Serial or Ethernet. If you have an RA Start it should go to the Ethernet and if you have the RA+ the Serial.println is still active (and acts like a debug if you have the Star).

If you are using the WiFiAlerts (probably not too many of you..), it will behave the same as the Serial sends automatically whereas if you are using the Ethernet, you will need to add a alert.send(); call in persistence or at least for a little while after you call an alert.

So if an alert is stateless and for a one time event, you will have to continue calling Send while the alert object processes the message. If you have an alert for something with state then, you won't need to do that unless it's something that flaps a lot. Anyway, if you make sure Send(). It won't process anything once it's been sent until another Send call with a message (ie. alert.Send("Test"); If you want to send right away regardless of delay, pass true as the second argument).

So a push request is forthcoming after a bit of testing, but so far very good. I just have one issue with a sticky relay switch that I'm chasing. It's just the relay I'm using to trigger a test event. Overall good progress today

Alright, all the issues with the WiFiAlerts are now resolved. It's working great now and the star has been running very well running the same program I'm running on the RA+. I was very tempted to swap out last night. I feel like I'm missing a few more things before I can start the build. There will be pictures (I hope)

Waiting for a few power strips and some elastic cord. I guess I'm going to have to wait till I'm back. Still a few more days, so let's see. I happened across a nice shelf made for a locker that I think will work perfectly to hold up my ATO reservoir (after some reinforcement) and give me a ton of space underneath for storage.