-
Notifications
You must be signed in to change notification settings - Fork 115
No MQTT being sent and WDT-Resets #6
Comments
I'm having the same issues with a regular NodeMCU dev board. I'm starting to think it's because of the DSMR 5 which sends a lot more data with shorter intervals which gives the loop no time to send data over MQTT and eventually kicking in the WDT. |
If you are using arduino ide, you could downgrade your board version to 2.5.2 and check if its is working? |
@HanSyt That seems to fix everything! Thank you. |
@HanSyt Never mind that, It seems to be spitting out CRC invalid. Is this a different issue? |
Did not notice that issue here, |
Im having exactly the same issue, when i look in my DHCP leases i can confirm it's rebooting each time. The minute i remove the RJ11 from the P1 it stopt with the reboot. I'm also using a NodeMCU. |
Having the same "CRC invalid" issue, which is most likely related to an old DSMR2.* meter with 9600 baudrate and 7E1 serial output instead of 8N1. SoftwareSerial.h only works with 8N1 |
If you are having issues on a newer meter (I wrote this for DSMR2.4 at the time), try the fork created by @daniel-jong. At the time the telegram was only send every once a minute instead of every second, so this sketch wasn't expecting so much incoming data. You can find it here: https://github.com/daniel-jong/esp8266_p1meter I will soon merge his changes into this sketch 👍 |
Has anybody got this working for Kamstrup 382 meter. It uses DSMR2.2 |
Hello, This is my first time doing anything with my smart meter and I've been trying to use esp8266_p1meter on my Wemos D1 Mini. At first I got a SoftwareSerial error and used #4 to fix it, Now I keep getting a bunch of WDT resets.
On top of all of that, I seem to be receiving data but nothing ever gets sent via MQTT.
My smart meter is an Agemcom T210-D.
Any help would be appreciated!
The text was updated successfully, but these errors were encountered: