my Core stops working today.
I have checked spark status and everything should be up and running, but I cannot get values from the cloud and functions registered also do not work.
I have reset my AccessToken and try it once again, but nothing. Code works now for >2month. So there should be no issue.
It should work, I can see the core in my routers DHCP Table. I donĀ“t want to reset it, because my WiFi password is >32 it works only with spark-cli and that is really circumstantial. And again it worked over >2month without any problems. No changes on my sideā¦ just stops working.
Just to be sureāin your example above COREID is long hex number, CORENAME is the name you gave your core, and ACCESSTOKEN is a long hex number, right?
In other words, you have edited the post above just to protect your privacy but in the real stuff you have real numbers.
You would be surprised how often I have to ask this!
@bko: No need to explain I know those mistakes. But sadly it is only for privacy reasons.
@kennethlimcp: Not a really good option, as I said before. This is same as āmy car stops working and I try to change the engineā. DonĀ“t get me wrong but I want to knwo whats happening.
led is ābreathingā as normal, and is definitely connected to my network, as it is still communicating with another device on the local network, (pushing its status to my home automation controller when I turn my tv on or off, )but seemingly not reachable via api.spark
Itās inside my TV and Iād really rather not take it apart if itās not a problem at my end.
Sorry, I was off duty this morning but Iām seeing this now. Can you PM me your device id that is malfunctioning and Iāll check it out? Iāll tweak some things from my end and see if I can fix the issue.
It looks like there was a brief window last night where there were some issues with one of our databases. Although things self-healed for most devices, some devices got caught in a ghosted state. I restarted some things internally and it looks like the error counts are back to normal. Sorry about the delay! We have a few people on duty today for the holiday, but the error counts were low enough that it didnāt seem like an anomaly.
Iāll look into why it didnāt fully self-heal for all devices so we can avoid that in the future.