What dashboard are you using? (Web, iOS, Android)
Web
What OS? (Jessie, Wheezy)
Jessie
What Model Pi?
B model 1
Please describe the bug / issue. Attaching any relevant screenshots would be very helpful!
I was busy at work and didn’t rin my Pi/Cayenne for a couple of weeks. Yesterday connected, but Cayenne dashboard shows Pi offline, though I’ve left it for the whole day. On the same laptop I can ping and ssh to the Pi, from Pi itself I can resolve cayenne’s URL and traceroute to it:
I seem to get this from time to time as well. In fact the other day I plugged in my Pi after being unplugged for a while and it was showing as offline. If you still have the .sh installer just run that again and it should update everything for you and bring it back online.
I think @ats1080s has the first step to solving this.
My thinking: We had a pretty nasty bug a couple weeks where the agent that was installed on your Pi would show as offline. We have since released fixes. Since your Pi was still using an old agent and could not connect to myDevices cloud, it could not update to the improved agent.
My hope is this will be fixed once you run the installer again. It’s the sudo sh rpi_xxxxxxxxx -v text, where rpi_xxxxxxxxxx is your unique install.
Thanks for advice, Adam and Benny, unfortunately even after running the sh installer, for that last 3 hours it still shows off-line…Any ideas what could be wrong?
I seem to be having the same issue. I ran the installer again, but no luck. The installer said it was installing 1.0.0.19003. The web agent says 1.0.0.18727. Same situation, mine’s been off for a few weeks, turned it on and it’s not connecting.
I noticed my pi had gotten a new IP address from my router, the android app still showed the old address which wouldn’t connect. So I statically assigned the old IP… no change. I can’t connect from either the web dashboard or the android app. It would be helpful if we had something to ping from the pi for testing. At this point I don’t know where else to go but a complete reload.
I was able to resolve this in my case. It turns out at some point my id changed in “/etc/myDevices/AppSettings.ini”. I’m not sure if it was the original problem, or a result of running the installer again. I edited “/etc/myDevices/AppSettings.ini” changing it back to the old id, which I got off the web dashboard, “- CayenneV03-XXXXXXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX”.
J,
Very glad to hear you were able to solve your problem! I’m sorry you didn’t get much response from the group, but in my case I couldn’t figure what might be wrong. Very much appreciate that you took the time to explain what you had, what you did, and that you found a resolution. Now we have your experience available should we find ourselves in similar situation.
@jhovak thanks you so much for providing the resolution steps and investigating! This should not have happened, I’ll bring this up to the team tomorrow (Monday) and once I can provide more info as to our fix I’ll update this thread.
@mac_ha Perhaps try jhovak’s work around until we can spend time investigating???
Thanks again @jhovak , and sorry about the inconvenience.
I have a similar problem. My solution was to ‘sudo nano /etc/resolv.conf’ and make sure I had a legitimate dns server ip there. Typically, I’ll find the internal ethernet base ip of 192.168.137.1 and replace it with OpenDNS’s 208.67.222.222. Unfortunately, the change reverts under some unknown condition and I have to redo periodically.
I ping ‘www.google.com’ and if the connection times out or something less than a millisecond count occurs, I know to redo the edit. I’m next going to try the ‘chown’ command on the file to see if that makes the edit permanent.
Just FYI,
I have my Pi3 setup through a wireless repeater and it has been working fine for more than a month.
Today I moved the Pi3 to the basement and it connected directly to the router’s wireless connection (not though the repeater) with the same IP address.
As mentioned above, everything was working, except for Cayenne web and Android constantly showing “offline”. I checked the “/etc/myDevices/AppSettings.ini” settings and they had NOT been changed.
Only after forcing the Pi3 to use the original (much weaker) wireless repeater signal, could I get it back to work.
