Anyway, I'd like to see if I could gain from the forum's collective knowledge on how to choose hardware and platform for my project and if there is someone out there that'd like to take on the project, then I'd be happy to grease the wheels with a bit of money. Plus you'd get to be the first developer commissioned via this forum, so basically also eternal bragging rights.
The basic gist is that I have about 1200 square feet divided up into 5 rooms along with a central hallway. In 4 of the rooms, I'd like to be able to push a button that would trigger events on a display housed in the central hallway and an equivalent display (with slightly different functionality) in the 5th room. Each button/room would have its own channel in whichever button system you choose (and if phase I goes well, it'd be great to be able to expand to 8-10 total channels)
The buttons would be used to start, stop and mark events throughout a specified time period. Here are the basic steps:
I hope that makes sense. It is essentially 4 timers running concurrently on two displays with fancy 'lap' features and each timer is controlled by a separate button.
Button hardware needed?
Ok, what do you think? I'll take any sort of advice and/or bids. Thank you!
This is how I'd approach it, at a high level.
Since I'm unsure how the Pucks' signal would fare over the distances and through walls I'd suggest each of the four rooms has Puck button and a Raspberry Pi Zero W acting as a receiver. Pucks could be carried in a similar fashion to your remotes around and between rooms.
Each Pi Zero W could listen on BLE for the Puck associated with its room, or probably better, to all Pucks to ensure good coverage. Pi Zero W boards are all connected via LAN.
Puck button events are relayed to Pi Zero W. A received confirmation could be sent back over to the puck over the same service. - probably UART would suffice to simply light up the LED. The Pi Zero W relay events over MQTT (or similar), to a server application on one of the Pi Zeros (primary) attached to a display running a web or console based UI there.
Second display probably runs another Pi Zero W as a slave and listens for update signals from primary to update it's own web or console based UI. Websockets will do here.
There's a starter for ten. Maybe others can finesse the approach.
Thank you very much for the suggestions! It does seem like I will have to have a receiver in each room and I hadn't looked into the Pi Zero W yet. Looks like a cost-effective choice
What hardware and communications to pick depends also on the means / skills that are or have to be made available for the building, operating and maintaining and the physical constraints for 'the button'. About the latter you have not elaborated much yet.
As @Ollie points out, Bluetooth BLE may not work across the whole space because of the obstructions. Therefore, at one point you need Wifi.
The lesser variation in hardware and communication you have, the 'easier' and more cost effective is it to build, operate and maintain your system.
If you do not have real physical constraints for 'the button', I would use only as hardware just Espruino-Wifi run by two standard/exchangeable 18650 LiIon batteries. All this fits in a small box you still can carry in you pocket. Espruino-Wifi is 30mm x 23mm (1.2 x 0.9 inch), 18650 LiIon is 18mm diameter x 66mm long (in inches: 0.7 diameter x 2.6 long). All in all about 1.5 x 3.6 x 0.8 inch. All buttons look the same, have the same software installed, etc. On power up, a sequence of (electrical) button presses makes the buttons to be what they supposed to be: button in rooms, button on bearers, 'button' in hallway as monitoring central station.
For display, you have multiple options:
For central station:
If you want to have a dedicated display, you may connect (plug-in) a TDF or OLED or LCD display.
If you want to spend a display on all buttons, put an OLED or LCD display in every device. If you pick a TFT, it uses a bit more power, but has the advantage of having a (resistive) touch screen... and the things are cheap.
With an OLED or LCD -but not touch - in each button, a 4 way with enter button fits and you may make it even a 'game boy'...
Since batteries can be exchanged, you can have enough charged spares available, and to operate reliably, you just built 10..12 buttons.
As a last comment: take a look at upcoming Espruino Pixl.js - just too bad that runs BLE only - but would have all what you need... Adding the batteries and a cheap ESP8266 ESP-01 serially connected with the Pixl.js will also give what you need... more than you need... and it is really a cool thing... see the fun NodeConf badge by @Gordon ... you will enjoy and be inspired... (and choose how to move forward).
This is fantastic! Thank you very much. It seems clear that WiFi is the way to go.
I used this information to beef up my project description and have now found someone to take on the job. I hope to have this up and running soon so thank you quite a bit!
Great, looking forward to progress reports... in this thread / msg ;-)
Don't worry about formatting, just type in the text and we'll take care of making sense of it. We will auto-convert links, and if you put asterisks around words we will make them bold.
For a full reference visit the Markdown syntax.
© Espruino, powered by microcosm.
Report a problem