Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

How to send temperature and address/other(device) to coordinator in real time. #11151

Closed Answered by kiansiong85
kiansiong85 asked this question in Q&A
Discussion options

Hi P-R-O-C-H-Y

This is great i saw your example.
Zigbee_Thermostat.ino
Zigbee_Temperature_Sensor

I am able to link and communication with each other.
I got a question,

1)what if I have multiple devices to connect? In addition to receiving the temperature, I also need to know real times which device the temperature comes from except the temperature?

void recieveSensorTemp(float temperature) {
Serial.printf("Temperature sensor value: %.2f°C\n", temperature);
sensor_temp = temperature;
}

Are there any similar examples available?

You must be logged in to vote

Thanks and appreciate a lot your reply PROCHY. I did make a feature request.

Feature Request: Support endpoint identification from multiple Zigbee devices
Background:
Current Zigbee library examples focus on one-to-one communication. In real use cases, like mine, we often connect multiple end devices (e.g. 5) to a single coordinator. However:

No endpoint/device information is displayed when receiving data (e.g. temperature).

It is difficult to identify which device sent the data.

The existing temperature (I tried to modify 2 devices connected, the second one took a long time) example does not show how to scale to multiple devices.

Suggested improvements:

Show the sender's endpoint or devi...

Replies: 3 comments 3 replies

Comment options

Hi @kiansiong85,
As the Zigbee library is now, there is no way of knowing which endpoint did send the temperature.
But I can see a possible way to implement that. Can you please convert this discussing into a feature request so I will have this in my backlog? Thanks

You must be logged in to vote
0 replies
Comment options

Thanks and appreciate a lot your reply PROCHY. I did make a feature request.

Feature Request: Support endpoint identification from multiple Zigbee devices
Background:
Current Zigbee library examples focus on one-to-one communication. In real use cases, like mine, we often connect multiple end devices (e.g. 5) to a single coordinator. However:

No endpoint/device information is displayed when receiving data (e.g. temperature).

It is difficult to identify which device sent the data.

The existing temperature (I tried to modify 2 devices connected, the second one took a long time) example does not show how to scale to multiple devices.

Suggested improvements:

Show the sender's endpoint or device address when receiving data.

Add an example of multiple devices sending data to one coordinator.

You must be logged in to vote
1 reply
Comment options

I will close this discussion as a feature request is now open for this functionality :)

Answer selected by P-R-O-C-H-Y
Comment options

Dear Jan Procházka, Any update for below? Already update to feature request last times. Thanks! Best Regards, KS
...
________________________________ From: Jan Procházka ***@***.***> Sent: Thursday, March 20, 2025 10:19 PM To: espressif/arduino-esp32 ***@***.***> Cc: kiansiong85 ***@***.***>; Mention ***@***.***> Subject: Re: [espressif/arduino-esp32] How to send temperature and address/other(device) to coordinator in real time. (Discussion #11151) Hi @kiansiong85<https://github.com/kiansiong85>, As the Zigbee library is now, there is no way of knowing which endpoint did send the temperature. But I can see a possible way to implement that. Can you please convert this discussing into a feature request so I will have this in my backlog? Thanks — Reply to this email directly, view it on GitHub<#11151 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AYIRFIOBFPRA7BATTKTHAKT2VLE53AVCNFSM6AAAAABZMT3ANSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENJWGQ4TANA>. You are receiving this because you were mentioned.Message ID: ***@***.***>
You must be logged in to vote
2 replies
Comment options

I also need this feature. I tried using some bits of the tsens value to encode an ID onto the payload but that didn't really work, because the tsens float is capped to 16 bits as it gets converted to a unit16_t

Comment options

Hi everyone, the feature request is currently in progress. I am now testing the changes if everything works fine.
I will link a PR to the feature request when available #11168

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet

AltStyle によって変換されたページ (->オリジナル) /