I recently moved from a C-8 to C-8 Pro (running 2.3.9.143) and ever since I've had issues with events not triggering on subscribed events.
I use WebCore heavily (community version), and I have several pistons that I would consider very mature (no issues in at least 1.5 years), but have had intermittent problems since migrating. This happens on both location mode (e.g., when setting away), and on device attributes (e.g., a contact sensor).
Here's the most recent example: The piston should have triggered twice, once when the garage door opened (12:04:10) and a second time when it closed (12:06:49). It only executed the second time:
^^ note that the first event at 12:04:10 isn't logged (and the piston didn't execute)
The piston itself is simple:
When I checked the piston execution time (in the WebCore dashboard), between these two events, it didn't show that it had executed either. I do see the event logged to InfluxDB, which is also triggered.
Nothing in the logs.
It's possible that WebCore is swallowing the event, but I didn't see this on either the C-7 or C-8 running the same WebCore versions. I just added a log statement to the piston deviceHandler() method so I can try to diagnose. Open to any other ideas on how best to track down and fix this.
Thanks. Really appreciate all your work on webCoRE for HE, BTW!
Nothing in the logs and the devices do show in the piston (I hit done as well).
I've seen this across multiple pistons, both new (created yesterday) and old (last updated a year ago). The one above I actually just created yesterday, and the same trigger works intermittently. I'll try pausing/resuming and see if there is a change. I should also mention, I'm running the April webCoRE builds.
The odd thing is they all work, sometimes. E.g., the Location Mode the other day: it didn't trigger when it changed to Away, but triggered properly when it changed back to Home (nothing changed in the piston, or the hub). It's very intermittent, so I'll watch it the next few days and see what my logging gives me.
This very closely describes my scenario, so latching on rather than starting a new thread. Here are some of my system details:
C8 Pro ... though I observed similar behavior on my previous C7.
Firmware 2.3.9.177 ... again, not new to recent FW.
WC community app.
A representative example is a motion/bulb piston that has been behaving for months but suddenly the bulb does not turn on.
Motion is sensed, piston is triggered, and bulb received the command in the device events.
The device page controls the bulb as expected.
Either edit/save or pause/resume of the piston makes everything happy again.
This is so intermittent that it may take weeks or months for me to capture diagnostics. I will be sure to have HE logs and piston Full logs ready to go before taking countermeasures next time.
My issue was the piston never executing on a subscribed command. I've done several hub migrations and I only had this issue after I migrated from C-8 to C-8 Pro. I ended up re-saving all my pistons and it seems to be fine at this point.
I have ran into a separate issue where z-wave in particular seems to take ~10 seconds to respond in a random case, but the piston sends the command to the device, so it's not a webcore issue.
Not sure if this helps. This evening, I added a couple devices to HE and then to the webCoRE available devices. I updated FW to 2.3.9.180, so a reboot. Then I picked a piston somewhat at random. I tried pause/resume on a few pistons and each gives me this (even though they were just working):
I didn't see anything noteworthy in the HE logs with logging level Full. Please let me know if anything stands out or if I might be able to provide some additional information. I appreciate the consideration.
Just to confirm, you're saying that the piston runs, it sends the command, but the device doesn't respond? If so, this shouldn't be a WC issue. Since this is a C-7 and a bulb, I'm thinking it's a Zigbee device? Does it happen with other device types?
Got it - I suppose it's possible that the mapping to device is wrong, and re-saving the piston fixes this (I suspect this was effectively my issue where triggers were not mapped correctly after the hub migration). I would expect the logs to show an error in that case, but not certain. I don't know if there is a fast way to pause/resume everything to force this, but that's probably the best course of action.
Same ting here, after upgrading from C-8 to C-8 Pro, no Webcore piston was working. Everything was disabled (all pistons and Wifi crap) before the backup. But none piston was working. I uninstalled Webcore and I'm restoring around 230 pistons one by one. This will take couple of minutes I guess.
For what it's worth my Pro has been super stable since I got it setup and my recollection is that it is faster. I had my C-8 pretty well loaded and the Pro handles everything easily.
