search

tp1de / ioBroker.ems-esp

EMS-ESP Adapter
MIT License
18 stars 4 forks source link

FEATURE REQEST: ReadOut Dallas sensors #1

Closed alexpthe1 closed 2 years ago

alexpthe1 commented 2 years ago

It would be nice if the connected dallas sensors would be reported to iobroker

tp1de commented 2 years ago

I am preparing an update with dallas sensors read. Since I have done other major coding changes it will take some days until I will release the new version.

tp1de commented 2 years ago

@alexpthe1 The new version 0.9.8 is supporting dallas sensors. Please test if it's working.

alexpthe1 commented 2 years ago

first of all, thank you for your great work and fast response! Unfortunately it is not working. The IDs are Reported but the value not (stays NULL)

https://paste.pics/3329d5a0b02b8d965661279edcd3b15f https://paste.pics/ebacf7540dd52ae18c92c72b378ed7fa

tp1de commented 2 years ago

What is returned by http://ems-esp/api/dallassensor/ ?

tp1de commented 2 years ago

That is my data: { "sensor1": { "id": "28-FF04-CFC4-1604", "temp": 25.6 }, "sensor2": { "id": "28-FF3B-04C5-1604", "temp": 25.4 }

alexpthe1 commented 2 years ago

// 20211124230239 // http://ems-esp/api/dallassensor/

{ "28-C808-07D6-013C": 43, "28-4012-07D6-013C": 83.5 }

tp1de commented 2 years ago

That's the reason for the null values. Which ems-esp-version are you using?

alexpthe1 commented 2 years ago

EMS-ESP Version v3.2.1

with a Device (Platform / SDK) ESP32 / v3.3.5-1-g85c43024c

tp1de commented 2 years ago

@proddy seems to have changed the api format for dallassensors. Actual dev version is v3.3.0b10 that's what I use. I will try to adjust the ioBroker adapter to accept the "old" format as well.

tp1de commented 2 years ago

I just uploaded an updated version. Please check if it is working now?

alexpthe1 commented 2 years ago

yep! thank you, again great work and even greater support

tp1de commented 2 years ago

I learned that it is quite a challenge to permanently adjust the adapter to all the changes done by @proddy .....

I will close this issue now.

proddy commented 2 years ago

That is a probably a mistake in EMS-ESP.The format should be the same. I'll look into it.

edit I checked and it's correct in 3.0 and was a bug in 3.2.1 (which is about 5 months old). You may want to inform users of your plugin that it's only compatible with EMS-ESP v3.3 and higher