esphome / esphome/feature-requests

way for sml / obis to accept 1.8.0 instead of 1-0:1.8.0 (so no prefix)

Open
#1,867 4 comments 0 reactions 0 assignees View on GitHub
component: dsmr
Dominant language
No language data
Stars
450
Forks
29
PR merge metrics
No merged PRs in 30d

Description

**Describe the problem you have/What new integration you would like**

I'm trying to migrate from tasmota, i just like esphome better, but the smart meter interface is still impossible to me as my meter uses obis codes as espohome recognises. Ie. "1-0:1.8.0" is what esphome except as obis, but "1.8.0" is what I get from electrical meter. Do you know how this could be solved with some workaround?

output from tasmota
![image](https://user-images.githubusercontent.com/8813196/189961459-fb383ac9-2587-4dc1-ab76-1c5e34b2c658.png)

**Please describe your use case for this integration and alternatives you've tried:**

I tried various custom OBIS reader external components

**Additional context**

Also to wake up meter the string /?! (hex 2F3F210D0A) at 300 baud needs to be sent, but it seems that rest of the communication could be done on 9600. But I'm currently running everything at 300 in tasmota and it works too.

Contributor guide

No contributing guide indexed for this repository

Research direction

No file or test is named. Start by locating the ESPHome OBIS reader and its configuration entry point, then compare its expected "1-0:1.8.0" value with the meter's "1.8.0" value. Done means the no-prefix form is accepted while existing OBIS input continues to work; the issue also mentions meter wake-up at 300 baud and later communication at 9600.

Written by the indexing model from the issue text.

Assessment

Domain
embedded-iot
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.