Allow modbus address/port/register to be specified in Hex

Feature Requests
1

Many low level devices are documented using Hex notation.

To reduce effort & mistakes from integration developers converting these to decimal,
allow the modbus integration to parse address: port: and others*
to also use numbers like 0x1B34 or 3A6h

(*) Maybe slave:/status_register:/target_temp_register:

P.S. Other modules, like Bluetooth or Network, might also benefit from this sort of flexibility

2

This is already possible. Yaml accepts hex and converts everything to integers.

This:

field: 15

is the same as

field: 0x0F
3

Thanks. I thought I tested it and found that feature lacking.

(and went searching for Hex or Hex Format, and found no doco or examples)

Might propose some small doco updates

4

It’s a yaml thing, it’s not an HA thing