JonnyBooker / split-flap

Code for split-flap display based on: https://github.com/Dave19171/split-flap
https://www.prusaprinters.org/prints/69464-split-flap-display
GNU General Public License v3.0
47 stars 7 forks source link

Compatability with Home Assistant? #10

Closed skynet01 closed 1 month ago

skynet01 commented 7 months ago

Would love to dive into this project but wanted to check to see if it's possible to make it compatible with Home Assistant? Maybe Split-Flap can receive messages on MQTT protocol? Or have a version of this firmware running on ESPHome?

The use case is that with Home Assistant it makes it REALLY easy to automate this for messages, notifications, sensor information etc.

skynet01 commented 7 months ago

Found an mqtt version here: https://github.com/nctiggy/split-flap-mqtt maybe they can be merged?

JonnyBooker commented 7 months ago

@skynet01 - Hello! You beat me to sending that link!

It is something I've considered doing but personally didn't have much use for myself as I don't run a HomeAssistant instance at home so left the idea on the backburner in favour of other projects.

It is something I can potentially look into if I manage to get some time in future, from what I've seen the implementation doesn't look too bad, and happy to post back here if I am making progress on it.

Happy to consider a PR potentially otherwise if capable!

N1c093 commented 4 months ago

I'm considering building this display as well. I use Home Assistant as well.

Is there currently no API available to transfer text to the display? Is it only possible through the web interface?

skynet01 commented 4 months ago

You would have to use MQTT integration to send messages to the Split Flap

JonnyBooker commented 4 months ago

@N1c093 - There is an "API" of sorts, you can submit a POST body to this webserver endpoint and it will update the display, however it is geared around serving the web interface so the action at the end is to redirect

But @skynet01 is correct, the typical implementation is via MQTT and that is the implementation that is followed here. I haven't got the capacity at the moment to be able to look into it unfortunately at this time, apologies. Not saying never just not at the moment.

JonnyBooker commented 1 month ago

I'm closing this issue for now as we have established it is not currently implemented. In future I may introduce a "Proper" API which can be used alongside the current implementation.

This feature will become evident through the releases :)