Brand new - not an engineer, etc. Testing a Boron idea. In the console event log for a device, there is an option to view events in a terminal. I used that once just to see it. The console event log stopped reading the Particle.publish() events, which was ok because I was seeing it in a terminal.
I’d been advised by @Rftop that I might reach my 1-second rate limit. At that time, I was using a delay(1000) in the code, but since have upped that to delay(1500), and the console has not at any time indicated I had any rate-limited events. So I think I’m ok there.
Now, however, I want to go back to the console, but the same code that is publishing to the console in a Xenon still will not publish in the Boron.
If there is something in the docs about it, please point me to it. But in looking at the Console doc, it skips that “see in a terminal” option altogether.
The code for that section:
if (command=="on") {
n = 0;
Particle.publish("LED Status = ", "Full Power");
digitalWrite(led1,HIGH);
digitalWrite(led2,HIGH);
return 1;
}
else if (command=="off") {
n = 0;
Particle.publish("LED Status = ", "Shutting Down");
digitalWrite(led1,LOW);
digitalWrite(led2,LOW);
return 0;
}
else if (command=="blink") {
n = 1;
while (n == 1) {
cnt_publish = cnt_publish + 1;
// To blink the LED, first we'll turn it on...
digitalWrite(led1, HIGH);
digitalWrite(led2, HIGH);
// We'll leave it on for 1 second...
if (cnt_publish == 5) {
Particle.publish("LED Staus = ","1");
}
delay(1500);
// Then we'll turn it off...
digitalWrite(led1, LOW);
digitalWrite(led2, LOW);
// Wait 1 second...
if (cnt_publish == 5) {
Particle.publish("LED Staus = ","0");
cnt_publish = 0;
}
delay(1500);
}
return n;
}
else {
return -1;
}
You should always use the PRIVATE switch for your publishes unless you explicitly need other users to see your events.
If that function is part of a Particle.function() callback, you should not run the blinking loop inside of that function but rather set a flag and deal with the blinking via loop().
I guess I overlooked the actual “Events” (console.particle.io/events) section - and that one is getting the events. But still doesn’t show up under the Device.
I just added the PRIVATE switch, as advised. But I know the blink loop needs to move. That one throws an error in the Console that the function call failed, since the return n; is outside the loop and never answers. But even there, I get the event in the console.particle.io/events.
What’s the difference between the two places events get displayed? Or since it’s in the Events section, just not worry about it for now?
The /events page will show all your events from all your devices while the /devices/... page should only show the events of that one device. So if you do get the event in the all-events-list you should also see it in the device's list, unless you are looking at the wrong device.
Each event should also contain a device_id field that tells you what device has published the event. Double check if they really match.
Confirmed that the devices are the same. This is where the part of my question about using a terminal comes up, if even relevant. If that is used, does it stop showing in the device-specific event log?
I’ve continued to work, adding a voltage check (no battery currently connected) to the loop().
void loop()
{
// Nothing to do
// Batt Testing
if(millis() - old_time > 60000) {
float voltage = fuel.getVCell() * 0.0011224;
Particle.publish("voltage", String::format("%.2f",voltage), PRIVATE);
old_time = millis();
}
// End Batt Testing
}
That event shows up in the ALL event log, but not in the device. In the attached screen shot, I am looking at the ALL events log, but it’s the same feature in the device log. A couple days ago, I used that command from the DEVICE event log, and the events haven’t show up there since.
The same code (minus the voltage check in loop() ) running on a xenon, using the functions including the blink, will show events in the device event log.
Correct - Chrome is as expected. Safari only showed a couple errors:
[Error] Failed to load resource: the server responded with a status of 404 () (ldclient.min.js.map, line 0)
[Error] Failed to load resource: the server responded with a status of 404 () (project.js.map, line 0)
I’m out of my league on this part. I just know Chrome is working, I’ll stick with it.
Not much help to other users looking at this post, huh?
Thanks again for the help. If this is a DOM or other bug in Safari browsers, would it be helpful and/or standard with this forum’s audience to mark it as “solved”?
Looks like you and Scruff were able to determine it to be an issue with Safari specifically that is the issue. We appreciate you both helping uncover this. We’ll be sure to make a note to our internal team to see about addressing this.
There might be a bit of a delay on getting around to it, as we are still on holiday break. As a short term fix, it looks like using Google Chrome for now is best. Hopefully that isn’t too much of a hassle!
No problem at all to use Chrome. The only oddity in this scenario is that on the Boron, I had used the “view events in a terminal” option in the DEVICE event log. I have not tried using that feature for my 4 Xenons or Argon in their Device specific logs.
icon in the post that explains the solution best, that post will be quoted in the opening post as solution.