search

cribskip / esp8266_spa

Control for a Balboa BP2100G0 spa controller using the esp8266
47 stars 19 forks source link

No MQTT messages #7

Open w4Rd3n opened 3 years ago

w4Rd3n commented 3 years ago

Hello. Thank you all for the great work on this. I have some problems with the fork of Emmanuel: https://github.com/EmmanuelLM/esp8266_spa

I use a Wemos D1 mini Pro and this config:

#define VERSION "0.32"
#define WIFI_SSID "TP-Link_F526"
#define WIFI_PASSWORD "******"
#define BROKER "192.168.1.170"
#define BROKER_LOGIN "loxberry"
#define BROKER_PASS "********"
#define AUTO_TX true //flag for the RS485/TTL chip - i.e. do we need to pull D1 or not....

So far Wemos is connected to my wifi but i dont receive any spa message on my broker. I have subscribed to Spa/# topic.

At the moment i don't have the spa connectet to the RS485 TTL transceiver. But anyway i should get some mqtt messages, no ?

I am powering the wemos and transceiver with 5V output of my DC-DC converter

Here is a photo of the HW: IMG_20210203_153635 Mirror Image of rear view HW: IMG_20210203_155654

w4Rd3n commented 3 years ago

I don't use external Antenna on the D1 mini for now. Ping is working but usually 1 of 4 packets are lost wheni execute the command. The Webserver is not working. it keeps saying connection timeout and then reloads page

cribskip commented 3 years ago

@EmmanuelLM s fork is tested with me in PR #6 but up to now, my tests were not successful besides the code looking great.

Maybe you should try my current code first to debug potential connectivity issues as it publishes when the wemos connects to the broker.

Tidy setup btw :-D

EmmanuelLM commented 3 years ago

My fork is "work in progress" ;-)

From my experience, I had issues with the RS485 to TTL transceiver and found [and I do not know why] that the device would just not work if it didn't receive messages (c.f. issue #4 - similar symptoms to yours)...

I agree with @cribskip - test his code first :)

p.s. #define AUTO_TX true -> this should be false with your transceiver p.p.s. try connecting your Spa to A & B

w4Rd3n commented 3 years ago

Thanks for your inputs. For now i only powered the board without the spa connection. i was assuming i ll get some mqtt messages also without the spa connected. I will let you know how this continues :)

Michael0yodi commented 3 years ago

Did you ever find any solution I've similar issue, I can see that it reports to my broker

1622540317: New connection from 172.16.0.121 on port 1883. {"result": "ok", "data": {}}1622540317: New client connected from 172.16.0.121 as Spa8861 (p2, c1, k10, u'mqttuser'). 1622540332: Client Spa8861 has exceeded timeout, disconnecting. 1622540338: New connection from 172.16.0.121 on port 1883. 1622540338: New client connected from 172.16.0.121 as Spa8852 (p2, c1, k10, u'mqttuser').

But no matter if connected or not to the spa I never get any data via mqtt webserver on D1 just give me this "Not found: /" not sure if expected?

I've it running on usb power without using the dc-dc converter, but since ground is not connected on the rs485 I guess it "should" work, rxd is flashing so looks like data is received

image

EmmanuelLM commented 3 years ago

Hello, a few things as it looks like you are nearly there.

If you are powering off usb (or anything else), you need all GND to be connected together otherwise the signal 'floats' - likewise, with the hot tub GND.

if you go to the webserver, go to http://you_ip/update - nothing shows in the root as you have seen.

pato-loco commented 3 years ago

@EmmanuelLM what do you mean with "all GND to be connected together"?

EmmanuelLM commented 3 years ago

I meant that the following GND connections should all be connected together:

On Mon, 14 Jun 2021 at 15:53, pato-loco @.***> wrote:

@EmmanuelLM https://github.com/EmmanuelLM what do you mean with "all GND to be connected together"?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cribskip/esp8266_spa/issues/7#issuecomment-860749141, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHW4H37ENRFEGNK6DIQYRALTSYJWDANCNFSM4XA7V5PA .

Michael0yodi commented 3 years ago

I've tried to make sure that gnd are common with the spa using a dc-dc converter, but it still behaves the same so not sure where to start troubleshooting, any ideas are welcome

pato-loco commented 3 years ago

I've tried to make sure that gnd are common with the spa using a dc-dc converter, but it still behaves the same so not sure where to start troubleshooting, any ideas are welcome

bridge (-) from the DC-converter "in" and (-) from the DC-converter "out" directly together.

Michael0yodi commented 3 years ago

should I also connect the GND on the RS485 transceiver? I've used RS485 before with no common ground so its a bit strange that its not working at all, could of course be something else also..

tonyfitzs commented 3 years ago

hi there, I am also having issues with MQTT. as reported above, I can see in the logs of my broker that the D1 Mini running this code is trying to connect to the brocker and its trying to send a message as follows

1632863671: New connection from 10.110.x.x on port 1883. 1632863671: New client connected from 10.110.x.x as Spa1 (p2, c1, k10, u'test'). 1632863665: Client Spa1 has exceeded timeout, disconnecting.

but the subscription isnt ever completed before it disconects. i am wondering if the code I am using is the right version (VERSION "0.35"), because the webpage, dosnt do anything either, and based on above it looks like it is suposed to. if I try to hit http://10.110.x.x/update I get a page time out. perhaps I am misunderstanding the purpose of this url, because the documentation has a few gaps, is this an OTA address rather than a webpage that shows you information.

EmmanuelLM commented 3 years ago

Hey there, thanks for trying the project. In my experience with this type of issue, the problem ended up being the RS485 TTL transceiver - the chip reboots itself when it doesn't receive any messages on the bus, so the behaviour below is expected.

If you have not already, I highly recommend getting the ARCELI TTL To RS485 Adapter 485 Serial Port UART Level Converter Module 3.3V 5V for the simple reason you don't need to mess about with levels.

If you already have this chip, you can buy a cheap rs485 TTL usb debugger that you can hook up to your laptop to check messages are coming through.

Good luck!

P.s. the OTA page is just for updates but it won't be available as the device reboots itself. P.p.s. there is a newer firmware on my fork

On Tue, 28 Sep 2021, 23:21 Tony Fitzsimmons, @.***> wrote:

hi there, I am also having issues with MQTT. as reported above, I can see in the logs of my broker that the D1 Mini running this code is trying to connect to the brocker and its trying to send a message as follows

1632863671: New connection from 10.110.x.x on port 1883. 1632863671: New client connected from 10.110.x.x as Spa1 (p2, c1, k10, u'test'). 1632863665: Client Spa1 has exceeded timeout, disconnecting.

but the subscription isnt ever completed before it disconects. i am wondering if the code I am using is the right version (VERSION "0.35"), because the webpage, dosnt do anything either, and based on above it looks like it is suposed to. if I try to hit http://10.110.x.x/update I get a page time out. perhaps I am misunderstanding the purpose of this url, because the documentation has a few gaps, is this an OTA address rather than a webpage that shows you information.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cribskip/esp8266_spa/issues/7#issuecomment-929634636, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHW4H34ZA7TUAIAJFJ2A6HLUEIWVRANCNFSM4XA7V5PA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

tonyfitzs commented 3 years ago

Hi Emmanuel,

Thank you for taking the time to get back to me. I have high hopes for this project. So first, let me clarify a few things; I have purchased the hardware that you recommended on your GitHub page. That means I have a D1 mini pro, and I also have an ARCELI TTL To RS485 (https://www.amazon.co.uk/ARCELI-Adapter-Serial-Converter-Module/dp/B07DN115BZas) before I go out and mess around under my house to connect all this up to my spa (My spa is built into the floor of my rear entertainment area) I want to make sure this all works on my workbench. So I also purchased a cheap RS485 to USB (https://i.ebayimg.com/images/g/~n0AAOxyItRTefGv/s-l500.jpg) as well.

I am also going to create a small app to help me with testing using C#. This will basically replicate the spa's settings and generate a simulated message as if your spa was connected to the communication port. Once I have that all working, I will share the project because I think it will be useful for others following after us. So as the first step in that process, I am trying to get basic communications up and running between the Rs485 dongle and the D1 Mini project. This is where I am having a lot of trouble, and im trying to narrow down the variables to make sure it's not my hardware.

So what's happening is I have the d1 mini, and the ARCELI TTL To RS485 all set up, I have installed your code (VERSION "0.35") onto my d1 mini, and I have connected the A and B data lines between the TTL To RS485 and the Rs485 dongle. Once the D1 boots up after loading the code, I open the terminal to see what it is sending (this is the screenshot on the left below) I also open a terminal against the USB port (on the right), and I can clearly see that the D1 is sending messages to the USB dongle, I send a sample message (7e 20 ff af 13 00 00 ff d 2a 00 00 67 67 00 04 00 00 00 00 00 00 00 00 00 66 00 00 00 78 00 00 52 7e) I can see that the D1 mini is responding with

wdt reset load 0x4010f000, len 3460, room 16 tail 4 chksum 0xcc load 0x3fff20b8, len 40, room 4 tail 4 chksum 0xc9 csum 0xc9 v000731e0 ~ld fpm close 3 mode : sta(a0:20:a6:0d:d6:ba) add if0 scandone state: 0 -> 2 (b0) state: 2 -> 3 (0) state: 3 -> 5 (10) add 0 aid 3 cnt

So far, so good.

@. @.

The issue I am now having is that I can't seem to get it to connect to my MQTT broker,

In the broker logs, I get this message repeated over and over again 1632903370: New client connected from 10.110.10.147 as Spa1 (p2, c1, k10, u'test'). 1632903386: Client Spa1 has exceeded timeout, disconnecting. 1632903391: New connection from 10.110.10.147 on port 1883.

And I can't see a topic for the spa being generated. Based on what I can see in your code, I think it should be reporting something like Spa// but its not.

Anyway, if you can help, I would appreciate it.

Also, I would like to help you out with improving the readme you have created because there are a lot of gaps in the explanation, which makes it a lot hard when you are having trouble like I am. Once I have this all up and running, I would be very happy to re right this for you and send it to you so you can post it if that's of value to you.

Thanks for your time

From: EmmanuelLM @.> Sent: Wednesday, 29 September 2021 4:48 PM To: cribskip/esp8266_spa @.> Cc: Tony Fitzsimmons @.>; Comment @.> Subject: Re: [cribskip/esp8266_spa] No MQTT messages (#7)

Hey there, thanks for trying the project. In my experience with this type of issue, the problem ended up being the RS485 TTL transceiver - the chip reboots itself when it doesn't receive any messages on the bus, so the behaviour below is expected.

If you have not already, I highly recommend getting the ARCELI TTL To RS485 Adapter 485 Serial Port UART Level Converter Module 3.3V 5V for the simple reason you don't need to mess about with levels.

If you already have this chip, you can buy a cheap rs485 TTL usb debugger that you can hook up to your laptop to check messages are coming through.

Good luck!

P.s. the OTA page is just for updates but it won't be available as the device reboots itself. P.p.s. there is a newer firmware on my fork

On Tue, 28 Sep 2021, 23:21 Tony Fitzsimmons, @.<mailto:@.>> wrote:

hi there, I am also having issues with MQTT. as reported above, I can see in the logs of my broker that the D1 Mini running this code is trying to connect to the brocker and its trying to send a message as follows

1632863671: New connection from 10.110.x.x on port 1883. 1632863671: New client connected from 10.110.x.x as Spa1 (p2, c1, k10, u'test'). 1632863665: Client Spa1 has exceeded timeout, disconnecting.

but the subscription isnt ever completed before it disconects. i am wondering if the code I am using is the right version (VERSION "0.35"), because the webpage, dosnt do anything either, and based on above it looks like it is suposed to. if I try to hit http://10.110.x.x/update I get a page time out. perhaps I am misunderstanding the purpose of this url, because the documentation has a few gaps, is this an OTA address rather than a webpage that shows you information.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cribskip/esp8266_spa/issues/7#issuecomment-929634636, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHW4H34ZA7TUAIAJFJ2A6HLUEIWVRANCNFSM4XA7V5PA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/cribskip/esp8266_spa/issues/7#issuecomment-929886265, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AIE7PFKLVBMQFHKCDMZD3F3UEKZDBANCNFSM4XA7V5PA. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

EmmanuelLM commented 3 years ago

One quick question: the system is not yet hooked up to the Spa, correct? If that is the case, I don't think the system will work because it will reboot itself when it doesn't receive messages after a while.

On Wed, 29 Sep 2021, 10:22 Tony Fitzsimmons, @.***> wrote:

Hi Emmanuel,

Thank you for taking the time to get back to me. I have high hopes for this project. So first, let me clarify a few things; I have purchased the hardware that you recommended on your GitHub page. That means I have a D1 mini pro, and I also have an ARCELI TTL To RS485 ( https://www.amazon.co.uk/ARCELI-Adapter-Serial-Converter-Module/dp/B07DN115BZas) before I go out and mess around under my house to connect all this up to my spa (My spa is built into the floor of my rear entertainment area) I want to make sure this all works on my workbench. So I also purchased a cheap RS485 to USB (https://i.ebayimg.com/images/g/~n0AAOxyItRTefGv/s-l500.jpg) as well.

I am also going to create a small app to help me with testing using C#. This will basically replicate the spa's settings and generate a simulated message as if your spa was connected to the communication port. Once I have that all working, I will share the project because I think it will be useful for others following after us. So as the first step in that process, I am trying to get basic communications up and running between the Rs485 dongle and the D1 Mini project. This is where I am having a lot of trouble, and im trying to narrow down the variables to make sure it's not my hardware.

So what's happening is I have the d1 mini, and the ARCELI TTL To RS485 all set up, I have installed your code (VERSION "0.35") onto my d1 mini, and I have connected the A and B data lines between the TTL To RS485 and the Rs485 dongle. Once the D1 boots up after loading the code, I open the terminal to see what it is sending (this is the screenshot on the left below) I also open a terminal against the USB port (on the right), and I can clearly see that the D1 is sending messages to the USB dongle, I send a sample message (7e 20 ff af 13 00 00 ff d 2a 00 00 67 67 00 04 00 00 00 00 00 00 00 00 00 66 00 00 00 78 00 00 52 7e) I can see that the D1 mini is responding with

wdt reset load 0x4010f000, len 3460, room 16 tail 4 chksum 0xcc load 0x3fff20b8, len 40, room 4 tail 4 chksum 0xc9 csum 0xc9 v000731e0 ~ld fpm close 3 mode : sta(a0:20:a6:0d:d6:ba) add if0 scandone state: 0 -> 2 (b0) state: 2 -> 3 (0) state: 3 -> 5 (10) add 0 aid 3 cnt

So far, so good.

@. @.

The issue I am now having is that I can't seem to get it to connect to my MQTT broker,

In the broker logs, I get this message repeated over and over again 1632903370: New client connected from 10.110.10.147 as Spa1 (p2, c1, k10, u'test'). 1632903386: Client Spa1 has exceeded timeout, disconnecting. 1632903391: New connection from 10.110.10.147 on port 1883.

And I can't see a topic for the spa being generated. Based on what I can see in your code, I think it should be reporting something like Spa// but its not.

Anyway, if you can help, I would appreciate it.

Also, I would like to help you out with improving the readme you have created because there are a lot of gaps in the explanation, which makes it a lot hard when you are having trouble like I am. Once I have this all up and running, I would be very happy to re right this for you and send it to you so you can post it if that's of value to you.

Thanks for your time

From: EmmanuelLM @.> Sent: Wednesday, 29 September 2021 4:48 PM To: cribskip/esp8266_spa @.> Cc: Tony Fitzsimmons @.>; Comment @.> Subject: Re: [cribskip/esp8266_spa] No MQTT messages (#7)

Hey there, thanks for trying the project. In my experience with this type of issue, the problem ended up being the RS485 TTL transceiver - the chip reboots itself when it doesn't receive any messages on the bus, so the behaviour below is expected.

If you have not already, I highly recommend getting the ARCELI TTL To RS485 Adapter 485 Serial Port UART Level Converter Module 3.3V 5V for the simple reason you don't need to mess about with levels.

If you already have this chip, you can buy a cheap rs485 TTL usb debugger that you can hook up to your laptop to check messages are coming through.

Good luck!

P.s. the OTA page is just for updates but it won't be available as the device reboots itself. P.p.s. there is a newer firmware on my fork

On Tue, 28 Sep 2021, 23:21 Tony Fitzsimmons, @.<mailto:@.>>

wrote:

hi there, I am also having issues with MQTT. as reported above, I can see in the logs of my broker that the D1 Mini running this code is trying to connect to the brocker and its trying to send a message as follows

1632863671: New connection from 10.110.x.x on port 1883. 1632863671: New client connected from 10.110.x.x as Spa1 (p2, c1, k10, u'test'). 1632863665: Client Spa1 has exceeded timeout, disconnecting.

but the subscription isnt ever completed before it disconects. i am wondering if the code I am using is the right version (VERSION "0.35"), because the webpage, dosnt do anything either, and based on above it looks like it is suposed to. if I try to hit http://10.110.x.x/update I get a page time out. perhaps I am misunderstanding the purpose of this url, because the documentation has a few gaps, is this an OTA address rather than a webpage that shows you information.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cribskip/esp8266_spa/issues/7#issuecomment-929634636,

or unsubscribe < https://github.com/notifications/unsubscribe-auth/AHW4H34ZA7TUAIAJFJ2A6HLUEIWVRANCNFSM4XA7V5PA>

. Triage notifications on the go with GitHub Mobile for iOS < https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>

or Android < https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub< https://github.com/cribskip/esp8266_spa/issues/7#issuecomment-929886265>, or unsubscribe< https://github.com/notifications/unsubscribe-auth/AIE7PFKLVBMQFHKCDMZD3F3UEKZDBANCNFSM4XA7V5PA>.

Triage notifications on the go with GitHub Mobile for iOS< https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android< https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cribskip/esp8266_spa/issues/7#issuecomment-929951932, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHW4H354AI26SB3WV4XVLF3UELEEXANCNFSM4XA7V5PA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

tonyfitzs commented 3 years ago

Yes that's correct.

Ok that makes sense. In that case I will get my little balboa Spa simulator working and revert...

But what about the mgtt question.

Sent from my Galaxy

-------- Original message -------- From: EmmanuelLM @.> Date: 29/9/21 19:46 (GMT+10:00) To: cribskip/esp8266_spa @.> Cc: Tony Fitzsimmons @.>, Comment @.> Subject: Re: [cribskip/esp8266_spa] No MQTT messages (#7)

One quick question: the system is not yet hooked up to the Spa, correct? If that is the case, I don't think the system will work because it will reboot itself when it doesn't receive messages after a while.

On Wed, 29 Sep 2021, 10:22 Tony Fitzsimmons, @.***> wrote:

Hi Emmanuel,

Thank you for taking the time to get back to me. I have high hopes for this project. So first, let me clarify a few things; I have purchased the hardware that you recommended on your GitHub page. That means I have a D1 mini pro, and I also have an ARCELI TTL To RS485 ( https://www.amazon.co.uk/ARCELI-Adapter-Serial-Converter-Module/dp/B07DN115BZas) before I go out and mess around under my house to connect all this up to my spa (My spa is built into the floor of my rear entertainment area) I want to make sure this all works on my workbench. So I also purchased a cheap RS485 to USB (https://i.ebayimg.com/images/g/~n0AAOxyItRTefGv/s-l500.jpg) as well.

I am also going to create a small app to help me with testing using C#. This will basically replicate the spa's settings and generate a simulated message as if your spa was connected to the communication port. Once I have that all working, I will share the project because I think it will be useful for others following after us. So as the first step in that process, I am trying to get basic communications up and running between the Rs485 dongle and the D1 Mini project. This is where I am having a lot of trouble, and im trying to narrow down the variables to make sure it's not my hardware.

So what's happening is I have the d1 mini, and the ARCELI TTL To RS485 all set up, I have installed your code (VERSION "0.35") onto my d1 mini, and I have connected the A and B data lines between the TTL To RS485 and the Rs485 dongle. Once the D1 boots up after loading the code, I open the terminal to see what it is sending (this is the screenshot on the left below) I also open a terminal against the USB port (on the right), and I can clearly see that the D1 is sending messages to the USB dongle, I send a sample message (7e 20 ff af 13 00 00 ff d 2a 00 00 67 67 00 04 00 00 00 00 00 00 00 00 00 66 00 00 00 78 00 00 52 7e) I can see that the D1 mini is responding with

wdt reset load 0x4010f000, len 3460, room 16 tail 4 chksum 0xcc load 0x3fff20b8, len 40, room 4 tail 4 chksum 0xc9 csum 0xc9 v000731e0 ~ld fpm close 3 mode : sta(a0:20:a6:0d:d6:ba) add if0 scandone state: 0 -> 2 (b0) state: 2 -> 3 (0) state: 3 -> 5 (10) add 0 aid 3 cnt

So far, so good.

@. @.

The issue I am now having is that I can't seem to get it to connect to my MQTT broker,

In the broker logs, I get this message repeated over and over again 1632903370: New client connected from 10.110.10.147 as Spa1 (p2, c1, k10, u'test'). 1632903386: Client Spa1 has exceeded timeout, disconnecting. 1632903391: New connection from 10.110.10.147 on port 1883.

And I can't see a topic for the spa being generated. Based on what I can see in your code, I think it should be reporting something like Spa// but its not.

Anyway, if you can help, I would appreciate it.

Also, I would like to help you out with improving the readme you have created because there are a lot of gaps in the explanation, which makes it a lot hard when you are having trouble like I am. Once I have this all up and running, I would be very happy to re right this for you and send it to you so you can post it if that's of value to you.

Thanks for your time

From: EmmanuelLM @.> Sent: Wednesday, 29 September 2021 4:48 PM To: cribskip/esp8266_spa @.> Cc: Tony Fitzsimmons @.>; Comment @.> Subject: Re: [cribskip/esp8266_spa] No MQTT messages (#7)

Hey there, thanks for trying the project. In my experience with this type of issue, the problem ended up being the RS485 TTL transceiver - the chip reboots itself when it doesn't receive any messages on the bus, so the behaviour below is expected.

If you have not already, I highly recommend getting the ARCELI TTL To RS485 Adapter 485 Serial Port UART Level Converter Module 3.3V 5V for the simple reason you don't need to mess about with levels.

If you already have this chip, you can buy a cheap rs485 TTL usb debugger that you can hook up to your laptop to check messages are coming through.

Good luck!

P.s. the OTA page is just for updates but it won't be available as the device reboots itself. P.p.s. there is a newer firmware on my fork

On Tue, 28 Sep 2021, 23:21 Tony Fitzsimmons, @.<mailto:@.>>

wrote:

hi there, I am also having issues with MQTT. as reported above, I can see in the logs of my broker that the D1 Mini running this code is trying to connect to the brocker and its trying to send a message as follows

1632863671: New connection from 10.110.x.x on port 1883. 1632863671: New client connected from 10.110.x.x as Spa1 (p2, c1, k10, u'test'). 1632863665: Client Spa1 has exceeded timeout, disconnecting.

but the subscription isnt ever completed before it disconects. i am wondering if the code I am using is the right version (VERSION "0.35"), because the webpage, dosnt do anything either, and based on above it looks like it is suposed to. if I try to hit http://10.110.x.x/update I get a page time out. perhaps I am misunderstanding the purpose of this url, because the documentation has a few gaps, is this an OTA address rather than a webpage that shows you information.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cribskip/esp8266_spa/issues/7#issuecomment-929634636,

or unsubscribe < https://github.com/notifications/unsubscribe-auth/AHW4H34ZA7TUAIAJFJ2A6HLUEIWVRANCNFSM4XA7V5PA>

. Triage notifications on the go with GitHub Mobile for iOS < https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>

or Android < https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub< https://github.com/cribskip/esp8266_spa/issues/7#issuecomment-929886265>, or unsubscribe< https://github.com/notifications/unsubscribe-auth/AIE7PFKLVBMQFHKCDMZD3F3UEKZDBANCNFSM4XA7V5PA>.

Triage notifications on the go with GitHub Mobile for iOS< https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android< https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cribskip/esp8266_spa/issues/7#issuecomment-929951932, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHW4H354AI26SB3WV4XVLF3UELEEXANCNFSM4XA7V5PA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/cribskip/esp8266_spa/issues/7#issuecomment-930020246, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AIE7PFNIZCUTV4MNK7I3SSLUELOADANCNFSM4XA7V5PA. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Michael0yodi commented 3 years ago

If you dont want it to reset you can just comment out the hardreset(); or set #define PRODUCTION false I did however never manage to get any mqtt messages to arrive beside the debug/connect ones, I thought my rs485 adapter might be broken, (same version as yours) but never got around to order another one, so please let us know if you make any progress

EmmanuelLM commented 3 years ago

Same answer I am afraid, topics only get published once the system has retrieved the configuration from the spa.

On Wed, 29 Sep 2021, 11:57 Tony Fitzsimmons, @.***> wrote:

Yes that's correct.

Ok that makes sense. In that case I will get my little balboa Spa simulator working and revert...

But what about the mgtt question.

Sent from my Galaxy

-------- Original message -------- From: EmmanuelLM @.> Date: 29/9/21 19:46 (GMT+10:00) To: cribskip/esp8266_spa @.> Cc: Tony Fitzsimmons @.>, Comment @.> Subject: Re: [cribskip/esp8266_spa] No MQTT messages (#7)

One quick question: the system is not yet hooked up to the Spa, correct? If that is the case, I don't think the system will work because it will reboot itself when it doesn't receive messages after a while.

On Wed, 29 Sep 2021, 10:22 Tony Fitzsimmons, @.***> wrote:

Hi Emmanuel,

Thank you for taking the time to get back to me. I have high hopes for this project. So first, let me clarify a few things; I have purchased the hardware that you recommended on your GitHub page. That means I have a D1 mini pro, and I also have an ARCELI TTL To RS485 (

https://www.amazon.co.uk/ARCELI-Adapter-Serial-Converter-Module/dp/B07DN115BZas ) before I go out and mess around under my house to connect all this up to my spa (My spa is built into the floor of my rear entertainment area) I want to make sure this all works on my workbench. So I also purchased a cheap RS485 to USB (https://i.ebayimg.com/images/g/~n0AAOxyItRTefGv/s-l500.jpg ) as well.

I am also going to create a small app to help me with testing using C#. This will basically replicate the spa's settings and generate a simulated message as if your spa was connected to the communication port. Once I have that all working, I will share the project because I think it will be useful for others following after us. So as the first step in that process, I am trying to get basic communications up and running between the Rs485 dongle and the D1 Mini project. This is where I am having a lot of trouble, and im trying to narrow down the variables to make sure it's not my hardware.

So what's happening is I have the d1 mini, and the ARCELI TTL To RS485 all set up, I have installed your code (VERSION "0.35") onto my d1 mini, and I have connected the A and B data lines between the TTL To RS485 and the Rs485 dongle. Once the D1 boots up after loading the code, I open the terminal to see what it is sending (this is the screenshot on the left below) I also open a terminal against the USB port (on the right), and I can clearly see that the D1 is sending messages to the USB dongle, I send a sample message (7e 20 ff af 13 00 00 ff d 2a 00 00 67 67 00 04 00 00 00 00 00 00 00 00 00 66 00 00 00 78 00 00 52 7e) I can see that the D1 mini is responding with

wdt reset load 0x4010f000, len 3460, room 16 tail 4 chksum 0xcc load 0x3fff20b8, len 40, room 4 tail 4 chksum 0xc9 csum 0xc9 v000731e0 ~ld fpm close 3 mode : sta(a0:20:a6:0d:d6:ba) add if0 scandone state: 0 -> 2 (b0) state: 2 -> 3 (0) state: 3 -> 5 (10) add 0 aid 3 cnt

So far, so good.

@. @.

The issue I am now having is that I can't seem to get it to connect to my MQTT broker,

In the broker logs, I get this message repeated over and over again 1632903370: New client connected from 10.110.10.147 as Spa1 (p2, c1, k10, u'test'). 1632903386: Client Spa1 has exceeded timeout, disconnecting. 1632903391: New connection from 10.110.10.147 on port 1883.

And I can't see a topic for the spa being generated. Based on what I can see in your code, I think it should be reporting something like Spa// but its not.

Anyway, if you can help, I would appreciate it.

Also, I would like to help you out with improving the readme you have created because there are a lot of gaps in the explanation, which makes it a lot hard when you are having trouble like I am. Once I have this all up and running, I would be very happy to re right this for you and send it to you so you can post it if that's of value to you.

Thanks for your time

From: EmmanuelLM @.> Sent: Wednesday, 29 September 2021 4:48 PM To: cribskip/esp8266_spa @.> Cc: Tony Fitzsimmons @.>; Comment @.> Subject: Re: [cribskip/esp8266_spa] No MQTT messages (#7)

Hey there, thanks for trying the project. In my experience with this type of issue, the problem ended up being the RS485 TTL transceiver - the chip reboots itself when it doesn't receive any messages on the bus, so the behaviour below is expected.

If you have not already, I highly recommend getting the ARCELI TTL To RS485 Adapter 485 Serial Port UART Level Converter Module 3.3V 5V for the simple reason you don't need to mess about with levels.

If you already have this chip, you can buy a cheap rs485 TTL usb debugger that you can hook up to your laptop to check messages are coming through.

Good luck!

P.s. the OTA page is just for updates but it won't be available as the device reboots itself. P.p.s. there is a newer firmware on my fork

On Tue, 28 Sep 2021, 23:21 Tony Fitzsimmons, @.<mailto: @.>>

wrote:

hi there, I am also having issues with MQTT. as reported above, I can see in the logs of my broker that the D1 Mini running this code is trying to connect to the brocker and its trying to send a message as follows

1632863671: New connection from 10.110.x.x on port 1883. 1632863671: New client connected from 10.110.x.x as Spa1 (p2, c1, k10, u'test'). 1632863665: Client Spa1 has exceeded timeout, disconnecting.

but the subscription isnt ever completed before it disconects. i am wondering if the code I am using is the right version (VERSION "0.35"), because the webpage, dosnt do anything either, and based on above it looks like it is suposed to. if I try to hit http://10.110.x.x/update I get a page time out. perhaps I am misunderstanding the purpose of this url, because the documentation has a few gaps, is this an OTA address rather than a webpage that shows you information.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub < https://github.com/cribskip/esp8266_spa/issues/7#issuecomment-929634636>,

or unsubscribe <

https://github.com/notifications/unsubscribe-auth/AHW4H34ZA7TUAIAJFJ2A6HLUEIWVRANCNFSM4XA7V5PA

. Triage notifications on the go with GitHub Mobile for iOS <

https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675

or Android <

https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub .

— You are receiving this because you commented. Reply to this email directly, view it on GitHub< https://github.com/cribskip/esp8266_spa/issues/7#issuecomment-929886265 , or unsubscribe<

https://github.com/notifications/unsubscribe-auth/AIE7PFKLVBMQFHKCDMZD3F3UEKZDBANCNFSM4XA7V5PA .

Triage notifications on the go with GitHub Mobile for iOS<

https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675

or Android<

https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub .

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <https://github.com/cribskip/esp8266_spa/issues/7#issuecomment-929951932 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/AHW4H354AI26SB3WV4XVLF3UELEEXANCNFSM4XA7V5PA

. Triage notifications on the go with GitHub Mobile for iOS < https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675

or Android < https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub .

— You are receiving this because you commented. Reply to this email directly, view it on GitHub< https://github.com/cribskip/esp8266_spa/issues/7#issuecomment-930020246>, or unsubscribe< https://github.com/notifications/unsubscribe-auth/AIE7PFNIZCUTV4MNK7I3SSLUELOADANCNFSM4XA7V5PA

. Triage notifications on the go with GitHub Mobile for iOS< https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android< https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub .

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cribskip/esp8266_spa/issues/7#issuecomment-930027974, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHW4H3Z2V2FKN2BNVFMZZFTUELPINANCNFSM4XA7V5PA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

tonyfitzs commented 3 years ago

Very well…

Thank you

From: EmmanuelLM @.> Sent: Wednesday, 29 September 2021 10:01 PM To: cribskip/esp8266_spa @.> Cc: Tony Fitzsimmons @.>; Comment @.> Subject: Re: [cribskip/esp8266_spa] No MQTT messages (#7)

Same answer I am afraid, topics only get published once the system has retrieved the configuration from the spa.

On Wed, 29 Sep 2021, 11:57 Tony Fitzsimmons, @.<mailto:@.>> wrote:

Yes that's correct.

Ok that makes sense. In that case I will get my little balboa Spa simulator working and revert...

But what about the mgtt question.

Sent from my Galaxy

-------- Original message -------- From: EmmanuelLM @.<mailto:@.>> Date: 29/9/21 19:46 (GMT+10:00) To: cribskip/esp8266_spa @.<mailto:@.>> Cc: Tony Fitzsimmons @.<mailto:@.>>, Comment @.<mailto:@.>> Subject: Re: [cribskip/esp8266_spa] No MQTT messages (#7)

One quick question: the system is not yet hooked up to the Spa, correct? If that is the case, I don't think the system will work because it will reboot itself when it doesn't receive messages after a while.

On Wed, 29 Sep 2021, 10:22 Tony Fitzsimmons, @.<mailto:@.>> wrote:

Hi Emmanuel,

Thank you for taking the time to get back to me. I have high hopes for this project. So first, let me clarify a few things; I have purchased the hardware that you recommended on your GitHub page. That means I have a D1 mini pro, and I also have an ARCELI TTL To RS485 (

https://www.amazon.co.uk/ARCELI-Adapter-Serial-Converter-Module/dp/B07DN115BZas ) before I go out and mess around under my house to connect all this up to my spa (My spa is built into the floor of my rear entertainment area) I want to make sure this all works on my workbench. So I also purchased a cheap RS485 to USB (https://i.ebayimg.com/images/g/~n0AAOxyItRTefGv/s-l500.jpg ) as well.

I am also going to create a small app to help me with testing using C#. This will basically replicate the spa's settings and generate a simulated message as if your spa was connected to the communication port. Once I have that all working, I will share the project because I think it will be useful for others following after us. So as the first step in that process, I am trying to get basic communications up and running between the Rs485 dongle and the D1 Mini project. This is where I am having a lot of trouble, and im trying to narrow down the variables to make sure it's not my hardware.

So what's happening is I have the d1 mini, and the ARCELI TTL To RS485 all set up, I have installed your code (VERSION "0.35") onto my d1 mini, and I have connected the A and B data lines between the TTL To RS485 and the Rs485 dongle. Once the D1 boots up after loading the code, I open the terminal to see what it is sending (this is the screenshot on the left below) I also open a terminal against the USB port (on the right), and I can clearly see that the D1 is sending messages to the USB dongle, I send a sample message (7e 20 ff af 13 00 00 ff d 2a 00 00 67 67 00 04 00 00 00 00 00 00 00 00 00 66 00 00 00 78 00 00 52 7e) I can see that the D1 mini is responding with

wdt reset load 0x4010f000, len 3460, room 16 tail 4 chksum 0xcc load 0x3fff20b8, len 40, room 4 tail 4 chksum 0xc9 csum 0xc9 v000731e0 ~ld fpm close 3 mode : sta(a0:20:a6:0d:d6:ba) add if0 scandone state: 0 -> 2 (b0) state: 2 -> 3 (0) state: 3 -> 5 (10) add 0 aid 3 cnt

So far, so good.

@.<mailto:@.> @.<mailto:@.>

The issue I am now having is that I can't seem to get it to connect to my MQTT broker,

In the broker logs, I get this message repeated over and over again 1632903370: New client connected from 10.110.10.147 as Spa1 (p2, c1, k10, u'test'). 1632903386: Client Spa1 has exceeded timeout, disconnecting. 1632903391: New connection from 10.110.10.147 on port 1883.

And I can't see a topic for the spa being generated. Based on what I can see in your code, I think it should be reporting something like Spa// but its not.

Anyway, if you can help, I would appreciate it.

Also, I would like to help you out with improving the readme you have created because there are a lot of gaps in the explanation, which makes it a lot hard when you are having trouble like I am. Once I have this all up and running, I would be very happy to re right this for you and send it to you so you can post it if that's of value to you.

Thanks for your time

From: EmmanuelLM @.<mailto:@.>> Sent: Wednesday, 29 September 2021 4:48 PM To: cribskip/esp8266_spa @.<mailto:@.>> Cc: Tony Fitzsimmons @.<mailto:@.>>; Comment @.<mailto:@.>> Subject: Re: [cribskip/esp8266_spa] No MQTT messages (#7)

Hey there, thanks for trying the project. In my experience with this type of issue, the problem ended up being the RS485 TTL transceiver - the chip reboots itself when it doesn't receive any messages on the bus, so the behaviour below is expected.

If you have not already, I highly recommend getting the ARCELI TTL To RS485 Adapter 485 Serial Port UART Level Converter Module 3.3V 5V for the simple reason you don't need to mess about with levels.

If you already have this chip, you can buy a cheap rs485 TTL usb debugger that you can hook up to your laptop to check messages are coming through.

Good luck!

P.s. the OTA page is just for updates but it won't be available as the device reboots itself. P.p.s. there is a newer firmware on my fork

On Tue, 28 Sep 2021, 23:21 Tony Fitzsimmons, @.<mailto<mailto:@.%3cmailto>: @.<mailto:@.>>>

wrote:

hi there, I am also having issues with MQTT. as reported above, I can see in the logs of my broker that the D1 Mini running this code is trying to connect to the brocker and its trying to send a message as follows

1632863671: New connection from 10.110.x.x on port 1883. 1632863671: New client connected from 10.110.x.x as Spa1 (p2, c1, k10, u'test'). 1632863665: Client Spa1 has exceeded timeout, disconnecting.

but the subscription isnt ever completed before it disconects. i am wondering if the code I am using is the right version (VERSION "0.35"), because the webpage, dosnt do anything either, and based on above it looks like it is suposed to. if I try to hit http://10.110.x.x/update I get a page time out. perhaps I am misunderstanding the purpose of this url, because the documentation has a few gaps, is this an OTA address rather than a webpage that shows you information.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub < https://github.com/cribskip/esp8266_spa/issues/7#issuecomment-929634636>,

or unsubscribe <

https://github.com/notifications/unsubscribe-auth/AHW4H34ZA7TUAIAJFJ2A6HLUEIWVRANCNFSM4XA7V5PA

. Triage notifications on the go with GitHub Mobile for iOS <

https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675

or Android <

https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub .

— You are receiving this because you commented. Reply to this email directly, view it on GitHub< https://github.com/cribskip/esp8266_spa/issues/7#issuecomment-929886265 , or unsubscribe<

https://github.com/notifications/unsubscribe-auth/AIE7PFKLVBMQFHKCDMZD3F3UEKZDBANCNFSM4XA7V5PA .

Triage notifications on the go with GitHub Mobile for iOS<

https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675

or Android<

https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub .

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <https://github.com/cribskip/esp8266_spa/issues/7#issuecomment-929951932 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/AHW4H354AI26SB3WV4XVLF3UELEEXANCNFSM4XA7V5PA

. Triage notifications on the go with GitHub Mobile for iOS < https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675

or Android < https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub .

— You are receiving this because you commented. Reply to this email directly, view it on GitHub< https://github.com/cribskip/esp8266_spa/issues/7#issuecomment-930020246>, or unsubscribe< https://github.com/notifications/unsubscribe-auth/AIE7PFNIZCUTV4MNK7I3SSLUELOADANCNFSM4XA7V5PA

. Triage notifications on the go with GitHub Mobile for iOS< https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android< https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub .

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cribskip/esp8266_spa/issues/7#issuecomment-930027974, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHW4H3Z2V2FKN2BNVFMZZFTUELPINANCNFSM4XA7V5PA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/cribskip/esp8266_spa/issues/7#issuecomment-930109678, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AIE7PFJFEWIL4ZQD6HQRDZLUEL5WTANCNFSM4XA7V5PA. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

DutchTrickle commented 3 years ago

p.s. #define AUTO_TX true -> this should be false with your transceiver p.p.s. try connecting your Spa to A & B

How do i find whether or not this is the case for my transceiver?

EmmanuelLM commented 3 years ago

Which transceiver do you have?

On Wed, 20 Oct 2021, 19:15 DutchTrickle, @.***> wrote:

p.s. #define AUTO_TX true -> this should be false with your transceiver p.p.s. try connecting your Spa to A & B

How do i find whether or not this is the case for my transceiver?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cribskip/esp8266_spa/issues/7#issuecomment-947919027, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHW4H365EG4R4WZFXINUBL3UH4BN3ANCNFSM4XA7V5PA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

DutchTrickle commented 3 years ago

https://www.amazon.nl/gp/product/B07DJ4TGY3/

I've also noticed, that if i turn on the D1 mini, the red light on the transceiver turns off (it turns on again if i power off the D1). Is it supposed to be on or blinking when its receiving data?

EmmanuelLM commented 3 years ago

AUTOTX should be true as per the default code. Regarding the LEDs, they should be blinking when receiving data.

On Wed, 20 Oct 2021, 20:52 DutchTrickle, @.***> wrote:

https://www.amazon.nl/gp/product/B07DJ4TGY3/

Ie also noticed, that if i turn on the D1 mini, the red light on the transceiver turns off (it turns on again if i power off the D1). Is it supposed to be on or blinking when its receiving data?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cribskip/esp8266_spa/issues/7#issuecomment-947987204, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHW4H343WORUWT75FG5POZDUH4MXLANCNFSM4XA7V5PA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

DutchTrickle commented 3 years ago

AUTOTX should be true as per the default code. Regarding the LEDs, they should be blinking when receiving data. … On Wed, 20 Oct 2021, 20:52 DutchTrickle, @.***> wrote: https://www.amazon.nl/gp/product/B07DJ4TGY3/ Ie also noticed, that if i turn on the D1 mini, the red light on the transceiver turns off (it turns on again if i power off the D1). Is it supposed to be on or blinking when its receiving data? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#7 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHW4H343WORUWT75FG5POZDUH4MXLANCNFSM4XA7V5PA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Hm, when i connect only the transceiver, the RX led is blinking. I believe this is to be expected. I can then connect the power to the ESP, this appears online. So far so good. When now i connect the RX and TX, the led goes out... When i reset the esp, i see a small blip of the led, but thats it. I don't know what could be wrong, its just 2 simple wires, all other elements on their own seem to be functioning.

EmmanuelLM commented 3 years ago

Maybe a silly suggestion but can you double check Rx and TX Vs the diagram? I am wondering if they are the wrong way round? As diagnostic steps, which LEDs blink when:

  1. You connect the transceiver to the esp only?
  2. You connect the transceiver to the spa only?
  3. You connect the transceiver to both?

On Sat, 23 Oct 2021, 09:59 DutchTrickle, @.***> wrote:

AUTOTX should be true as per the default code. Regarding the LEDs, they should be blinking when receiving data. … <#m8157489711580837092> On Wed, 20 Oct 2021, 20:52 DutchTrickle, @.***> wrote: https://www.amazon.nl/gp/product/B07DJ4TGY3/ Ie also noticed, that if i turn on the D1 mini, the red light on the transceiver turns off (it turns on again if i power off the D1). Is it supposed to be on or blinking when its receiving data? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#7 (comment) https://github.com/cribskip/esp8266_spa/issues/7#issuecomment-947987204>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHW4H343WORUWT75FG5POZDUH4MXLANCNFSM4XA7V5PA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub .

Hm, when i connect only the transceiver, the RX led is blinking. I believe this is to be expected. I can then connect the power to the ESP, this appears online. So far so good. When now i connect the RX and TX, the led goes out... When i reset the esp, i see a small blip of the led, but thats it. I don't know what could be wrong, its just 2 simple wires, all other elements on their own seem to be functioning.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cribskip/esp8266_spa/issues/7#issuecomment-950120309, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHW4H3776FARU2FZ5LZTYR3UIJ2O5ANCNFSM4XA7V5PA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

DutchTrickle commented 3 years ago

Maybe a silly suggestion but can you double check Rx and TX Vs the diagram? I am wondering if they are the wrong way round? As diagnostic steps, which LEDs blink when: 1. You connect the transceiver to the esp only? 2. You connect the transceiver to the spa only? 3. You connect the transceiver to both?

Not silly at all. I appreciate the help. I wondered this myself, so i've switched them round. But still nothing. I have tx > tx and rx > rx. When i connect the transceiver to the esp only i see nothing. Only a tx blip when powering on or resetting the esp. When the transceiver is connected to the SPA, rx is blinking. When i connect both, i see nothing. You would think my esp is not working, but i can connect to the webserver, and it connects to my mqtt broker (although no messages obviously).

I'm starting to wonder, could my A and B on the transceiver be backwards? The voltage levels were very clear, and i put the higher one on the B pin.

I also tried to connect to my pc using a usb to ttl adapter. Opened the serial monitor and set baudrate to 115200. But i don't see anything dome in. Should i? I do see (garbled) messages coming in when i connect it over usb directly. Correction, this is working, When i now only connect the ESP to the transceiver i see the tx blink whenever the esp resets due to a lack of messages. About once every ~15 seconds.

EmmanuelLM commented 3 years ago

Odd, worth swapping A&B - the worse that will happen is messages get scrambled on the channel and your display will moan. Any other differences in your hardware connection vs the diagram on Github?

On Sun, 24 Oct 2021 at 09:38, DutchTrickle @.***> wrote:

Maybe a silly suggestion but can you double check Rx and TX Vs the diagram? I am wondering if they are the wrong way round? As diagnostic steps, which LEDs blink when: 1. You connect the transceiver to the esp only? 2. You connect the transceiver to the spa only? 3. You connect the transceiver to both?

Not silly at all. I appreciate the help. I wondered this myself, so i've switched them round. But still nothing. I have tx > tx and rx > rx. When i connect the transceiver to the esp only i see nothing. Only a tx blip when powering on or resetting the esp. When the transceiver is connected to the SPA, rx is blinking. When i connect both, i see nothing. You would think my esp is not working, but i can connect to the webserver, and it connects to my mqtt broker (although no messages obviously).

I'm starting to wonder, could my A and B on the transceiver be backwards? The voltage levels were very clear, and i put the higher one on the B pin.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cribskip/esp8266_spa/issues/7#issuecomment-950284548, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHW4H34HDEYRXCOBQ7FI4KTUIPAZRANCNFSM4XA7V5PA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

tonyfitzs commented 3 years ago

Can I make a suggestion.

I had much the same challenge as you are, I decided to remove as many variables as I could by setting the d1 mini and Rs485 on my work bench. I purchased a USB to 485 converter. And then loaded a basic serial monitor code onto the mini.i then sent clear text via termite to the d1 mini via the USB Rs485 interface and monitored it via the Arduino serial monitor. Initially I was getting nothing and I discovered that the screen print on the RS485 TTL device was reversed, I switched to and rx and then I could see the information was getting to the D1.

I still haven't been able to get it to work but I think there is something up with my son controller. I am writing a small app that will reproduce the spa messages for testing. But im probably 6 months from getting it done as im busy with other stuff...

Sent from my Galaxy

-------- Original message -------- From: DutchTrickle @.> Date: 24/10/21 19:38 (GMT+10:00) To: cribskip/esp8266_spa @.> Cc: Tony Fitzsimmons @.>, Comment @.> Subject: Re: [cribskip/esp8266_spa] No MQTT messages (#7)

Maybe a silly suggestion but can you double check Rx and TX Vs the diagram? I am wondering if they are the wrong way round? As diagnostic steps, which LEDs blink when: 1. You connect the transceiver to the esp only? 2. You connect the transceiver to the spa only? 3. You connect the transceiver to both?

Not silly at all. I appreciate the help. I wondered this myself, so i've switched them round. But still nothing. I have tx > tx and rx > rx. When i connect the transceiver to the esp only i see nothing. Only a tx blip when powering on or resetting the esp. When the transceiver is connected to the SPA, rx is blinking. When i connect both, i see nothing. You would think my esp is not working, but i can connect to the webserver, and it connects to my mqtt broker (although no messages obviously).

I'm starting to wonder, could my A and B on the transceiver be backwards? The voltage levels were very clear, and i put the higher one on the B pin.

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/cribskip/esp8266_spa/issues/7#issuecomment-950284548, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AIE7PFLJSFBAI7WNYN3TZ5LUIPAZRANCNFSM4XA7V5PA. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

DutchTrickle commented 3 years ago

Odd, worth swapping A&B - the worse that will happen is messages get scrambled on the channel and your display will moan. Any other differences in your hardware connection vs the diagram on Github? […]

I tried swapping them, but noting changed. AFAIK i have the exact same setup as is described. I'm using a nodemcu currently as my wemos gave up on me, but this should make any difference as far as i can tell. (am i right?). One other odd thing is, i dont get any errors on my display (NO COMMS). no matter how i connect everything. Is there something im missing?

EmmanuelLM commented 3 years ago

The only other difference I could think about is the memory size and compiler profile if your chip is not 100% the same - have a look at "platformio.ini" and adapt for your specific device (keep the lib_deps): The default is: " [env:d1_mini_pro] platform = espressif8266 board = d1_mini framework = arduino board_build.ldscript = eagle.flash.4m3m.ld board_build.filesystem = littlefs

upload_protocol = espota

upload_port = spa.local

lib_deps =

RECOMMENDED

Accept new functionality in a backwards compatible manner and patches

rlogiacco/CircularBuffer @ ^1.3.3 knolleary/PubSubClient @ ^2.8 bblanchon/ArduinoJson @ ^6.17.2

hieromon/AutoConnect @ ^1.2.2

bbx10/DNSServer @ ^1.1.0"

On Tue, 26 Oct 2021 at 13:55, DutchTrickle @.***> wrote:

Odd, worth swapping A&B - the worse that will happen is messages get scrambled on the channel and your display will moan. Any other differences in your hardware connection vs the diagram on Github? […]

I tried swapping them, but noting changed. AFAIK i have the exact same setup as is described. I'm using a nodemcu currently as my wemos gave up on me, but this should make any difference as far as i can tell. (am i right?). One other odd thing is, i dont get any errors on my display (NO COMMS). no matter how i connect everything. Is there something im missing?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cribskip/esp8266_spa/issues/7#issuecomment-951910568, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHW4H37IA2GXMXXAGS46TVTUI2XODANCNFSM4XA7V5PA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

StevieWW commented 7 months ago

Make sure you use a tranceiver with a MAX13487 Chip and not just MAX485. This was my problem since it seems that the layout of the linked board has been changed in between.