Plugin 64, APDS 9960, which "Collection"?

[oisisi]

There are Collections A through G and the respective compiled binaries. The plugin I am interested in, P 64, Gesture APDS9960, only shows as status "Collection" without any letter. Does this mean it isn't included in any binary and I need to compile it myself?

[Ath]

The 'Collection' label implies it is included in ALL Collection builds, A..G.
The same is that all 'Normal' labeled plugins are included in all Collection builds.

[oisisi]

That's nice and helpful. Thank you!

[whatsupskip]

Let me know if it will work for you as I briefly tried it the other day, but it would not enable the for me using the "G" collection and the two most recent firmware versions for the ESP8266.

[oisisi]

I can confirm it works for me. Initially, it didn't but what do you expect when you forget to hook up GND, duh. The lesson I learned is that I2C modules can be discovered even without the GND pin being connected.

[TD-er]

It can, but if it is powered from a different power supply, it can also damage your ESP or your I2C sensor.

[Ath]

The lesson I learned is that I2C modules can be discovered even without the GND pin being connected.

I've even seen a sensor being recognized with SCL and SDA swapped... (but most don't)

[oisisi]

@whatsupskip, here's an observation I made. I had to uncheck "Single event with all values" and set an interval for the plugin to get varying values for light and proximity. I now get different values with each interval and additionally when a gesture is being detected.

[whatsupskip]

Thanks I will try those settings and see if that fixes it.

[oisisi]

@whatsupskip, here's an observation I made. I had to uncheck "Single event with all values" and set an interval for the plugin to get varying values for light and proximity. I now get different values with each interval and additionally when a gesture is being detected.

This is cursed. I have to retract/correct that. When I set an interval the last registered gesture will be repeated with the interval. In sum, if I want gestures I have to disable intervals and get the unchanged light and proximity values published with each new gesture. When I want light and proximity I need to set an interval and have to ignore the gesture information.

[Ath]

This is cursed. I have to retract/correct that. When I set an interval the last registered gesture will be repeated with the interval. In sum, if I want gestures I have to disable intervals and get the unchanged light and proximity values published with each new gesture. When I want light and proximity I need to set an interval and have to ignore the gesture information.

@oisisi, I've resolved your complaints in a new PR #5016. The build is running in this GH Actions run, can you please test if this resolves your issue? You'll need to have a Github account to be able to download (creating an account is free, if you don't have one yet).
Once installed, you should enable the "Separate Gesture events" option in the plugin settings, and change your event handler (Rules) from On <taskname>#Gesture Do to On <taskname>#Swipe Do (For backward compatibility I added a new event, so for existing users all works as it was.) Though this might be the better use-case for this plugin
Also, gestures are processed when measuring R/G/B Colors, making it all in all more versatile.

[oisisi]

Thanks Ath, that wasn't necessary, thank you. I'll wait for the workflow to complete and will flash my board again. I sent a small donation your way.

[Ath]

Thank you

[Ath]

I'll wait for the workflow to complete and will flash my board again.

Have you been able to test the build?

[oisisi]

Have you been able to test the build?

Yes. I have a working rule that publishes on 'gesture#Swipe'. Additionally, for testing, I publish Light/Proximity/Gesture values every 10 seconds via the regular controller settings. Values for all parameters are being published every ten seconds. The last detected gesture number is being repeated.

I assume that "0" relates to a specific gesture and does not mean 'no gesture'.

[Ath]

Yes. I have a working rule that publishes on 'gesture#Swipe'. Additionally, for testing, I publish Light/Proximity/Gesture values every 10 seconds via the regular controller settings. Values for all parameters are being published every ten seconds. The last detected gesture number is being repeated.

That's how a Controller publish works, every Interval all values are published. We don't have a mechanism to select what values to publish. But you can now rename it and ignore it on the receiving side.

I assume that "0" relates to a specific gesture and does not mean 'no gesture'.

According to the documentation 0 = None, so your rule can use an "if" check if you want to ignore that

Edit: Link to the updated documentation (pull request)

[oisisi]

The updated documentation is very helpful, thanks. I am actually getting 0s as gesture info (from event "<device name>#Swipe").

Edit: It looks like I get a '0' where I should be getting a '5' ("Near (towards the sensor)").
Edit: I also get a '0' for unclear gestures. Perhaps my sensor is broken or I need to tweak the calibration.