roarfred / amstomqttbridge Goto Github PK

Hi!

Sadly there is no power outlet close by the power meter so I would primary look at a
self contained solution and then for one which has some good power saving so it could
run a longer time on (rechargeable-)batteries.

From how I see it the only power source here is the USB port. Is there a way to power it
via HAN, somewhere I read that this port should also be able to supply some power.

Just a few suggestions;

• Edit silkscreen so it's easier to see orientation of TSS721A
• Add RX/TX/Gnd silkscreen etc to programming header
• Change SW1/SW2 to Reset/Flash
• Change MicroUSB to a normal barrel connector (Only Gnd and Positive is used) for easier soldering
• Add 5V trace to programming pin, this way a 5V programmer can be used directly instead of both programmer and power supply separately
• Replace JP1/JP2 with DIP-switches instead of jumpers

There is probably a reason why things are done the way they are, I'm just wondering if these changes could make it easier for newbies.

• Should allow secured or unsecured WiFi connection
• Should allow secured or unsecured MQTT connection
• Store parameters in EEPROM
• Allow force boot as AP (read input of pin). Can we re-use the prog button, making a loop at start-up that allow user to press the prog button for a few seconds?

Hei. Sitter å leser gjennom tråden din (https://www.hjemmeautomasjon.no/forums/topic/1982-lesing-av-ams-data-amshan-iot/ )

Og ser du legger inn knapper for å reprogrammere ESPen. Har du prøvd Arduino-OTA? Den funker kjempe bra. Raskere og enklere å reprog, kan gjøres in-situ. Kan også anbefale WiFiManager.

Jeg kommer til å benytte meg av denne mot Aidon måleren. Kjører elbil så det kan være en ide å styre ladeeffekt basert på en gitt maksgrense og forbruket i nuet.

The .ino files in the examples folder did not compile, as these are based on an older type of list/obis definitions.

The linear regulator listed doesn't seem to be available anymore...
At the moment there are "0" available, and no one seems to know if they will be available again.

Are there alternatives, or does the PCB have to be redesigned to fit other parts?

Update:
This seems to be a perfect replacement:
LMS8117AMP-3.3/NOPBCT-ND

Hi!

This looks like a cool and useful project.
Is this where I can order your ready made last version PCBs ?: https://aisler.net/roarfred/my-project-repository/han-esp-tss721
Or do you sell them here in norway?

Roger

I originally forked this code, but have now detached the fork and restructured the code to my preference so that it's easier for me to keep a fairly active development on this project. It will still be a bit on and off depending on workload in my daily job though, so I hope others can pitch in as well every now and then. I have opened for issue tracking on my repository to get some input from the community on bugs to fix and features to add. Also added continuous build with PlatformIO on GitHub Actions which in return provide the project with pre-built firmware binaries on the release page.

https://github.com/gskjold/AmsToMqttBridge

https://ci.appveyor.com/project/RoarFredriksen/amstomqttbridge/build/1.0.18:

Build started
git clone -q https://github.com/roarfred/AmsToMqttBridge.git C:\projects\amstomqttbridge
git fetch -q origin +refs/pull/37/merge:
git checkout -qf FETCH_HEAD
Specify which project or solution file to use because the folder contains more than one project or solution file.

If debugging on a 2400 baud serial, the loop that logs the received data might be very close to the 1s limit for the WDT on ESP8266

The main readme should give:

• A short description of the project
• Some neat graphics for HAN -> ESP -> WiFi -> MQTT -> UI presentation
• A TOC describing content of the following
  • Electrical designs
  • Code
  • Documentation
  • Samples

Hi. I have started on designing an alternative circuit. The main planned differences are:

• The schematic and drawings are made with KiCad (free GPL tool), which brings the benefit that everyone can change and update the schematics and PCB¹.
• Focus on robustness and reliability. I do not trust the simple voltage divider bus signal converter and want to use the industry standard TSS721 chip, fully optocoupled to avoid any ground loops.
• Available as an Arduino shield to be a flexible building block in whatever monitoring system you want to make.
• Support for sending data over wire (serial/usb/ethernet).
• Support daisy-chaining.

The question is how to cooperate on this. I can create a separate repository that you just link to or use as a submodule. Or I can fork this and make a pull request into a Electrical2 directory or better, reorganise the Electrical into containing two subdirectories.

What do you prefer?

¹ Currently you have a PCB that cannot (easily) be modified and you have to post notes like "R8 should not be used" instead of just updating it. That is not very good.

Listen for specific MQTT message, with url for binary to update from

There's been a few changes to the HanReader, ref #29 and the examples needs to be updated. Possibly we should also split the examples into separate for each meter type?

Hi. This looks like a great project and I am looking forward to start testing this together with my Home Assistant setup (Hass.io).
First of, Im no electronics guy and like to use NodeMCU boards in my projects.
By looking on the schematics I hope that by using the NodeMCU board I have lying around I can simplify the project a bit. Could any of you confirm that I just need to build the HAN to TTL part with the attached RJ45 contact and connect this directly to the NodeMCU RX/TX? Schematics. Or even simplify even more?

I suggest the following improvements on your "boot as AP first" code.

• Set the MQTT port to 1883 by default
• In addition to the "Boot as AP on GPIO 0, add a "Clear EEPROM" function on another GPIO

And of course, FOTA :)

When booting as AP an selecting meter, the numbers are:

1: kaifa
2: Aidon
3: Kamstrup

But in the switch (ap.config.meterType) Aidon is 3 and Kamstrup is 2.

Also, I don't see where you set the hanreader to SERIAL_8N1 for Kamstrup.

Hei!

Vil anbefale OpenMUC til logging/lagring av verdier.

www.openmuc.org

Open source logger som har DLMS/COSEM driver, og utvikles fortløpende. Kan kjøre på både windows og linux (f.eks raspberry pi). Har også en fin REST-service for data til eksterne systemer og logging, samt kan konvertere data med gateway extension til andre protokoller som BACnet/IP, modbus, MQTT osv.

Mvh
Benjamin Kruger

Ouput:

"lv":"KFM_0","id":"69706314017539","type":"MA304H","P":845,"Q":0,"I1":1639,"I2":2666,"I3":2916,"U1":2384,"U2":2384,"U3":2384

Should be MA304H3E

There's a challenge with data changed from the latest Kamstrup meter. From the documentation, there's a 0x09 byte that was intentionally removed and it is unclear why.

Problem is now that we need to find a good way to parse the header in a safe way. The Kaifa meter still has this 0x09 byte here. We are having a bit of trouble understanding how this can be detected without forcing a headerLength field into the meter OBIS code files.

I will try to better document this, but in the mean time, there's some information about the discovery (in norwegian) here: https://www.hjemmeautomasjon.no/forums/topic/1982-lesing-av-ams-data-amshan-iot/?do=findComment&comment=32850
(Read from here and about 10 posts ahead to get the picture)

I connected the board with USB to the computer to get power to ESP8266.
I then connected the 3.3V programmer with USB to the same computer.

After a while it started smoking, and the red light on ESP8266 turned off, and I could see that the USB plug had melted on one of the pins!

The cable is destroyed, and the one pin as well. There is nothing wrong with the cable..

The web page should have existing values set in form controls when loaded. To avoid a heavy string-concatenation thing, I think the best will be to create a new route that provides a json structure with existing config (or good defaults), and load these from a javascript. This should cover one part of issue #40

Sadly, the author of this project has passed away in April. :(

He's done a great job with this project and many people are using it!
It would be great to continue this project in a fork, but with 10 forks already (and probably more will come), it's difficult for people to know which one is "active" and in continued development.

Are there any "collaborators" added to this project, that has access to modifying the ReadMe without a PR? Based on the commits, @hlovdal might? If so, it would be great to make an "official" fork of this project and point to it in the ReadMe. :)

Here's also an active (Norwegian) forum thread about this project, started by @roarfred himself: https://www.hjemmeautomasjon.no/forums/topic/1982-lesing-av-ams-data-amshan-iot/

Maybe the DigiKey cart should be updated with metal film resistors rather than carbon?
Will probably not be a big difference in reliability, but 1% tolerance vs 5% does make sense when working with digital electronics.

The price difference is nothing or minimal when ordering a handful.

Mulig å designe Board 2 med mulighet for PoE på den?

Hullene kan være optional å montere så den vil ikke øke kostnaden for de som ikke ønsker å bruke POE

https://www.silvertel.com/images/datasheets/Ag9700-Datasheet-low-cost-isolated-Power-over-Ethernet-PoE-module-solution.pdf

I think it would be great to rename the boards to a more intuitive convention:

• Board001 -> SimpleMBus_ESP8266
• Board002 -> TSS721_ArduinoShield
• Board003 -> MBus_Simulator

@hlovdal, do you approve? I am open to other names, just more readable