int8 data type (Modbus)

[GLT-IN]

DESCRIPTION

Hi,
int8 values are difficult to interpret by second devices, because they are transmitted as int16.
For example minexttemp (register offset: 51) with value "-16" is transmitted as 00 F0, but interpreted as "240".
Is it possible to send int8 as full int16?

REQUESTED INFORMATION

Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!

• Searched the issue in issues
• Searched the issue in discussions
• Searched the issue in the docs
• Searched the issue in the chat
• Provide the System information in the area below, taken from http://<IP>/api/system

  Paste System information here....

EXPECTED BEHAVIOUR

A clear and concise description of what you expected to happen.

SCREENSHOTS

[MichaelDvP]

I think it's only one small change, please try https://github.com/MichaelDvP/EMS-ESP32/releases/tag/latest
and check if all is solved.

[GLT-IN]

Hi,
int8 values are represented correctly now, but the whole system does not run stable.
Devices and entities getting lost and found randomly.

[GLT-IN]

every minute the device restarts with v3.7.2-dev.5

[MichaelDvP]

Do the restarts happen only in my version, or also in official v3.7.2-dev.5?
What happen every minute? Commands/reads sent to emsesp?

[GLT-IN]

it happens in both versions

[MichaelDvP]

This is normal after restart. It takes a while to fetch entities from the ems-bus. Trying to read a non existing entity gives this message. After a minute this should stop. But should not lead to a restart.

BTW. i see that recently some registers changes in this commit 9c3044e

[GLT-IN]

i changed the register addresses and there are no device restarts any more

[GLT-IN]

Thank you!

[MichaelDvP]

i changed the register addresses and there are no device restarts any more

Wrong address or length should only give an errormessage, but no crash.
I'v found a candidate, but not sure if it is fixed now.
Please report if you see this crash again.