Hello! :blush: I have received help elsewhere about this obstacle but unfortunately it's going over my head at the moment. Not...way over, about an inch, but, still - it's going over my head. I'm pretty good at "adapting" code, and adding to existing code, I've cooked up reasonably involved project…

[image] daneboomer: I don't want to pester ScruffR anymore No problem, no pester :wink: Try this one (tested and working :blush:) // name all devices with a common prefix e.g ScruffyMaster, ScruffySlave, ... #define COMMON_DEVICE_NAME_PREFIX "Scruffy" const int ledPins[] = { D7, D1, D2, A3…

@christine @daneboomer If you don’t want to use IFTTT, this bit of code works nice. Has a bit of security and works for Photons on different peoples accounts. You can probably tighten things up a bit if both photons are on the same particle.io account, then you should be able to use the private s…

Thanks @rocksetta Basically what I want to do is something like the below. I’ve sort of adapted your code into the below, but I’m sure I’ve turned it into pseudo code. I think the weakness in the below is that it would not be possible to have two buttons operating independently of each other becaus…

For two publishes you’d get two calls for your handler which don’t share the same data since they don’t overlap in time. But you will run into the rate limit for publishing in your loop() And I would strongly recommend against the use of delay(7000); inside the event handler! This is not good in …

Hi @ScruffR , I wasn’t aware I was using a delay in my loop. I had removed this (or I thought I had) in my pseudo code above? I know that as it stands the loop would be executing code far too fast, both in terms of publishing to the cloud and in terms of how fast it’s switching LEDs on and off. I sh…

No, the delay(7000) was not in your code, but in the suggested code by Rocksetta and a delay in loop is no problem but would rather help avoiding the rate violation. Oh, are you intending to use my code? I just pulled it back since I got the impression it might have been confusing and you’d much p…

Hi Scruff, it’s OK, I have a copy locally (of the code you posted). It was in a sense initially “too complicated” but I think you had built into the code a sort of automatic-demo, had you not? I am in the process of stripping it down to the bare essentials and seeing if I can use it for my purposes…

Actually it was tailor made for what I understood from your initial question and the other thread where we had discussed some options (e.g. filter own events from other devices events - hence the spark subscription). This code is intended to be as portable as possible that you only have to maintain…

It’s like ruddy Christmas. Thanks @ScruffR Quick question: is the reworked code amended due to a better understanding of what I’m trying to do? All best! :slight_smile:

Help with spark.publish / spark.subscribe, please?

General

rocksetta November 11, 2015, 4:03pm 3

Here is my suggestion:

Use IFTTT and a few simple subscribe and publish buttons. I got this code working with a group of grade 11-12 students. They could push a button on their cell phones and make the other students photon light go on. See topic at

Topic		Replies	Views
Suitability of Spark as compared to Arduino Getting Started	32	4512	June 15, 2015
Sprint 7: Particle.publish() released! Let's build a cloud-connected motion detector General	67	16870	February 24, 2016
Before I get too far, would someone mind just checking my code? General	15	3434	November 7, 2015
Would someone mind taking a look at this spark.publish / spark.subscribe code? Troubleshooting	15	1979	March 18, 2015
Subscribing to an event within a Spark Core does not work Troubleshooting	39	6704	June 15, 2015

Help with spark.publish / spark.subscribe, please?

Related topics