Feature Request: Description for Dallas sensors

[alexandergeiler]

I have 9 Dallas sensors connected to my EMS-ESP.
It is hard to distinguish them because you only see the ID and it is hard to remember IDs.

I would like to have a description field for each sensor (see screenshot)

This will make it much easier to identify which sensor is taking which readings

I would be great to have the description also available at MQTT (see screenshot)

[MichaelDvP]

You know that v2 for esp8266 will not get any new enhancements, the 8266 is to memory limited and with some more ems-devices like your system access to webpage is critical. Better switch to esp32 and v3 with more features.

We had discussed this before, the id is not very intuitive and the number can change, an alias would help. I've made an approach to replace the id by a name in all fields (web/mqtt/HA/terminal) and also add an offset calibration to sensors. But for now there is only a terminal command to set the name sensor [id] [name] [offset], sensor list the names, sensor id clears an id-entry, sensor id name set a name, sensor id name offset sets name and offset, name can be "" to leave it as id. The sensor-format selection is enhanced to by number/by id/by name
I'm thinking about an easier way to set the names, so it is not in the official build, only in my test.

[alexandergeiler]

Ohhh, I posted it in the wrong project. I have a esc32 :-)
Don´t know how to move that feature request in the correct project...

Nice to hear that there is already an idea to implement something.
then I'll wait until this is available as an official feature.

[MichaelDvP]

I've integrated it in the official v3.1.2b4. In terminal use sensorname command and you can switch in web-Settings the Dallas Format to by Name, affects mqtt, api and web.

Don´t know how to move that feature request in the correct project...

Close this and reopen in eps32 if it does not work as expected. I also don't know a way to move.

[proddy]

I can move it when I'm back this weekend!

[MichaelDvP]

I've tested a bit, a suggestion for setting the names from the web is this:

[proddy]

I was thinking about this during my holiday. Instead of showing the Sensor #, ID and Temperature like we have now with :

We rename "ID" to "Name". Then on the left side of the row add the pencil icon which allows you to rename the "Name". The name is defaulted to that long ID.

[MichaelDvP]

Ok, i've used a button around the number, but pencil is better to remove for non-admin.
As you see i also added the analog (if activated).
I can push, or push a feature-build after testing the last changes.

[MichaelDvP]

[MichaelDvP]

I've only done some short tests, all seems to work. I've pushed to dev, some more testers with many dallas are welcome.
Web forces to names, the setting id/no/name is for api/mqtt only. Mqtt does not like spaces in names, i use the space to seperate name and offset. Console command sensorname can be called with id (any) or sensornumber (sensor has to be connected).

I like to automatic reload values after setting a value or name, but did not get managed it for now. Documentation needs also an update.

[proddy]

@MichaelDvP really excellent work, love it. We could enhance the dialog box to not allow spaces in the names, and have the offset as a separate field. If you want any help with coding let me know. I'm self-isolating for the next 7 days so may have odd bits of spare time

[proddy]

@MichaelDvP really excellent work, love it. We could enhance the dialog box to not allow spaces in the names, and have the offset as a separate field. If you want any help with coding let me know. I'm self-isolating for the next 7 days so may have odd bits of spare time

I'm making these changes and doing a bit of refactoring along the way

[proddy]

@MichaelDvP really excellent work, love it. We could enhance the dialog box to not allow spaces in the names, and have the offset as a separate field. If you want any help with coding let me know. I'm self-isolating for the next 7 days so may have odd bits of spare time

I'm making these changes and doing a bit of refactoring along the way

finished with the changes. The edit screen has a small update. most of the changes were internal