Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I noticed a bug where the updates weren't being forwarded to the sensor. You can see this when you insert an UUID into the PollenType objects when they're created, and look at which UUID is being used to send out the updates. This has also been discussed in #2
The very first run creates a UUID for the PollenType object
0409b222-11cc-4b3b-8700-4de58c5b8c29
.The next update creates a brand new PollenType (UUID
efd1dd15-5d2c-4bf3-8bd3-44bbb8fd4afd
), but the sensor ("Getting level from pollen type"), still references0409b222-11cc-4b3b-8700-4de58c5b8c29
.To fix this, I've made the sensor objects not reference region objects and pollen objects directly, but instead it looks them up from the Pollen_DK object.