You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey,
I saw in another thread that you were looking for a way to track how many Senseo are running your firmware. I think I might help with that. I can write a little public dashboard in python with plotly dash that accept post requests from SenseoWifi and display the number of active senseo on diagram. Then all what we need to do in the firmware is to push a request to that server every now and then with a unique ID (a CRC of the MAC address should do the trick).
This raise a few concerns, though :
We need somewhere to host the dashboard
If we do that in amazon (or any similar service), it will cost a small fee every month
If we host that ourself, it means that our public ip will become available in the source code
In the esp firmware we'll need to contact the server regulary, maybe once a day or once every coffee. I don't know the state of HTTP libraries in the esp, but if those calls are blocking it might become an issue, especially if the server is slow or sometimes down.
The text was updated successfully, but these errors were encountered:
Hey,
I saw in another thread that you were looking for a way to track how many Senseo are running your firmware. I think I might help with that. I can write a little public dashboard in python with plotly dash that accept post requests from SenseoWifi and display the number of active senseo on diagram. Then all what we need to do in the firmware is to push a request to that server every now and then with a unique ID (a CRC of the MAC address should do the trick).
This raise a few concerns, though :
The text was updated successfully, but these errors were encountered: