[BUG] with multiple units news are distributed to wrong unit

[moehrem]

Dear @moehrem,

First of all – thanks for adding the new feature to send News.
It works perfectly when using only one unit, and I am really happy with this new possibility.

However, since extending the setup to multiple units, I noticed an issue:
I am using the integration with a user who is a member of multiple units. The user has all necessary rights for each unit. For each unit, there is a corresponding group of people who should receive the News.

When sending News for each unit, I specify the individual cluster_id and the respective group_id.

The News is indeed sent, but all News items arrive only at one unit.

Specifically:

• Unit 1 receives News for Unit 1 and for Unit 2.

• Unit 2 receives no News at all.

I trigger the News through separate automations, all at the same time.

Additional information:

• With just one unit, News sending works flawlessly.

• I verified that the correct cluster_id and group_id are used in each automation.

• The user’s API token is valid and has permissions for all units.

Could you please advise if this is a known limitation or if there is a recommended way to handle News for multiple units with one user?

Thank you!

Originally posted by @ricman01 in #71

[moehrem]

I will have a look into that issue the next weeks.

[moehrem]

Hi @ricman01

i found the issue but I can't solve it:
Each api-call needs a key of a user, which is permitted to use the api endpoint. These api-keys are user specific - not specific per unit. DiverControl searches for the correct api key based on the cluster_id you enter in the service call. This api key is the same for both of your units. And heres the point: There is no parameter to tell the endpoint WHICH unit I want to address. I am not able to identify as a specific unit upon calling the divera api.
So from the point of view of Divera its always the same user who's creating news, thus the news will be created at the first unit.

And to make it even worse: The same issue pops up with every other api call...

I will create a ticket at Divera. Lets cross fingers I am wrong. Or Divera is able to fix it.

I'll keep you updated.

Edit: As a quickfix you may use a single user per unit only.

[moehrem]

After consulting Divera, it turns out, that I am able to identify the unit. Kind of irritating documentation, nut non the less: I will fix the issue as soon as possible.

Furthermore these news solve some other issues I had with other functions in the past. Maybe that lead to some deeper changes in data handling in the future.

[moehrem]

Hi @ricman01

I finished development and am testing the changes. As I changed service handling and api calls fundmentally, testing will take some days. But hopefully I can get v1.2.0 out before weekend.

I used the time to implement proper UI support. Heres a little sneak peak, developer tool actions and automation UI:

---

---

[moehrem]

Hi @ricman01,

just release v1.2.0, which includes a fix for that issue. Please have a look on that, if you still face any issues, please let me know.

Thank you!

[ricman01]

Hi @moehrem,

and thanks a lot for the great work! The screenshots look very promising, and I'm really looking forward to trying everything out. However, I'll only be home for the next 2 days and then I'll be traveling for almost 3 weeks, so I won't be able to rebuild the automations until after I get back.
Everything I currently need is working fine, so there's no urgency. But I'll definitely dive into the changes once I'm back!

Thanks again, and talk to you soon!

[moehrem]

Hi @ricman01,

I take your silence as a good sign :)
We used the updated version with our units since Oct'25 and did not hat that problem again. So I'll close that issue.

Cheers!