I’ve read this thread:
Can’t send from Cloud to Device
and have the same issue.
I’ve finally got the Hologram Nova up and running using CLI commands (after turning off the NB-IoT with AT commands through Screen). I’m on a raspberry pi 3 B+, using the latest builds of the hologram SDK and Raspbian.
I can send messages out to the dashboard from the pi/nova with
sudo hologram send "message". But it seems like receive just won’t happen most of the time. In fact, after trying for the last two hours, I finally decided to join this forum and ask this question. Only on the very last try, did it manage to send a message to the device. So rhavourd, I guess I’m someone who’s done it on the NovaM.
Order of operations:
- Put the nova into receive mode from CLI. It indicates it is waiting for a message on port 4010.
- On the dashboard, send a simple message “via cloud data” on port 4010 using TCP.
- Within seconds, the dashboard console shows
socket error: timed out, with topic
_API_RESP_, as the last poster in the previous thread indicated.
That is, until it just started working as I typed this post, for no apparent reason. I’ve changed no settings between not working/working.
I’m connected to “AT&T Hologram”, signal strength “29,99”
Any ideas on why sending messages to the nova seems fragile? What are some failure points of this connection? Maybe it takes a certain amount of time after connecting to a network? Just shooting in the dark here…
Has anything changed on Hologram’s end since Dec 2018 on how timeouts are handled (this was mentioned by Reuben in the other thread?