Appreciate any help, this add-on worked brilliantly last year. Ive just turned the tub back on for the season and it fails. Seems host is unreachable.
Perhaps ive forgotten to do something. Any help appreciated.
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[09:16:32] INFO: Starting BWALink addon...
[09:16:32] INFO: Setting addon timezone to Europe/London based on the system timezone.
[09:16:33] INFO: Starting mqtt bridge connecting tcp://192.168.0.16:8899/ to mqtt://core-mosquitto:1883
/usr/lib/ruby/gems/3.2.0/gems/balboa_worldwide_app-2.1.5/lib/bwa/client.rb:42:in `initialize': Host is unreachable - connect(2) for "192.168.0.16" port 8899 (Errno::EHOSTUNREACH)
from /usr/lib/ruby/gems/3.2.0/gems/balboa_worldwide_app-2.1.5/lib/bwa/client.rb:42:in `new'
from /usr/lib/ruby/gems/3.2.0/gems/balboa_worldwide_app-2.1.5/lib/bwa/client.rb:42:in `initialize'
from /usr/lib/ruby/gems/3.2.0/gems/balboa_worldwide_app-2.1.5/exe/bwa_mqtt_bridge:416:in `new'
from /usr/lib/ruby/gems/3.2.0/gems/balboa_worldwide_app-2.1.5/exe/bwa_mqtt_bridge:416:in `<top (required)>'
from /usr/bin/bwa_mqtt_bridge:25:in `load'
from /usr/bin/bwa_mqtt_bridge:25:in `<main>'
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[09:16:41] INFO: Starting BWALink addon...
[09:16:41] INFO: Setting addon timezone to Europe/London based on the system timezone.
[09:16:41] INFO: Starting mqtt bridge connecting tcp://192.168.0.16:8899/ to mqtt://core-mosquitto:1883
/usr/lib/ruby/gems/3.2.0/gems/balboa_worldwide_app-2.1.5/lib/bwa/client.rb:42:in `initialize': Host is unreachable - connect(2) for "192.168.0.16" port 8899 (Errno::EHOSTUNREACH)
from /usr/lib/ruby/gems/3.2.0/gems/balboa_worldwide_app-2.1.5/lib/bwa/client.rb:42:in `new'
from /usr/lib/ruby/gems/3.2.0/gems/balboa_worldwide_app-2.1.5/lib/bwa/client.rb:42:in `initialize'
from /usr/lib/ruby/gems/3.2.0/gems/balboa_worldwide_app-2.1.5/exe/bwa_mqtt_bridge:416:in `new'
from /usr/lib/ruby/gems/3.2.0/gems/balboa_worldwide_app-2.1.5/exe/bwa_mqtt_bridge:416:in `<top (required)>'
from /usr/bin/bwa_mqtt_bridge:25:in `load'
from /usr/bin/bwa_mqtt_bridge:25:in `<main>'
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[09:16:49] INFO: Starting BWALink addon...
[09:16:50] INFO: Setting addon timezone to Europe/London based on the system timezone.
[09:16:50] INFO: Starting mqtt bridge connecting tcp://192.168.0.16:8899/ to mqtt://core-mosquitto:1883
/usr/lib/ruby/gems/3.2.0/gems/balboa_worldwide_app-2.1.5/lib/bwa/client.rb:42:in `initialize': Host is unreachable - connect(2) for "192.168.0.16" port 8899 (Errno::EHOSTUNREACH)
from /usr/lib/ruby/gems/3.2.0/gems/balboa_worldwide_app-2.1.5/lib/bwa/client.rb:42:in `new'
from /usr/lib/ruby/gems/3.2.0/gems/balboa_worldwide_app-2.1.5/lib/bwa/client.rb:42:in `initialize'
from /usr/lib/ruby/gems/3.2.0/gems/balboa_worldwide_app-2.1.5/exe/bwa_mqtt_bridge:416:in `new'
from /usr/lib/ruby/gems/3.2.0/gems/balboa_worldwide_app-2.1.5/exe/bwa_mqtt_bridge:416:in `<top (required)>'
from /usr/bin/bwa_mqtt_bridge:25:in `load'
from /usr/bin/bwa_mqtt_bridge:25:in `<main>'
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[09:16:58] INFO: Starting BWALink addon...
[09:16:58] INFO: Setting addon timezone to Europe/London based on the system timezone.
[09:16:59] INFO: Starting mqtt bridge connecting tcp://192.168.0.16:8899/ to mqtt://core-mosquitto:1883
/usr/lib/ruby/gems/3.2.0/gems/balboa_worldwide_app-2.1.5/lib/bwa/client.rb:42:in `initialize': Host is unreachable - connect(2) for "192.168.0.16" port 8899 (Errno::EHOSTUNREACH)
from /usr/lib/ruby/gems/3.2.0/gems/balboa_worldwide_app-2.1.5/lib/bwa/client.rb:42:in `new'
from /usr/lib/ruby/gems/3.2.0/gems/balboa_worldwide_app-2.1.5/lib/bwa/client.rb:42:in `initialize'
from /usr/lib/ruby/gems/3.2.0/gems/balboa_worldwide_app-2.1.5/exe/bwa_mqtt_bridge:416:in `new'
from /usr/lib/ruby/gems/3.2.0/gems/balboa_worldwide_app-2.1.5/exe/bwa_mqtt_bridge:416:in `<top (required)>'
from /usr/bin/bwa_mqtt_bridge:25:in `load'
from /usr/bin/bwa_mqtt_bridge:25:in `<main>'
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
Really appreciate any update on this, be good to know if this project is dead or if perhaps theres an alternative. OR if indeed someone still has it running so that I can look to see if my problem is elsewhere.
I’d recommend @supersebbo start a new thread for that add-on to make support easier. I’ve been getting direct messages for assistance with that module.
Thats great to hear Jim, I was running your version last season. As you can see it failed when trying this year. Anything you can advise based on the errors I received? Many thanks for continuing maintenance and support?
No, that wasnt me, i was responding to another user that the Bolboa wifi module was very unreliable.
I switched to the remote serial device and everything for me from that point had been good. Also I dont run docker, so not sure how to run cron job, if your suggesting thats what I should be doing. Many thanks for help.
Jim,
I’m glad to hear the project is still alive and hoping you can help me. I have the Elfin-EW11 all set up and configured per your specs. I’m trying to install the addon but it immediately says Failed to install add-on
Unknown error, see supervisor
The Supervisor log says
2024-05-09 04:24:05.905 ERROR (MainThread) [supervisor.docker.addon] Invalid build environment, can’t build this add-on!
I’ve double checked the contents and am pretty sure I have that correct.
Any idea what I am missing?
So I tried your Docker route instead, subscribed to homie/# and expected to see activity in MQTT Explorer but don’t see anything. My Docker Compose
version: "3"
services:
bwalink:
image: ghcr.io/jshank/bwalink:latest
container_name: bwalink
restart: unless-stopped
environment:
# See https://iotbyhvm.ooo/using-uris-to-connect-to-a-mqtt-server/ for MQTT_URI format
# MQTT_URI *must* be properly URI encoded, e.g. mqtt://useename:pa##[email protected] would
# be mqtt://username:pa%23%[email protected]
# BRIDGE_IP and BRIDGE_PORT are the address and port for your serial to IP device or
# host running ser2net, socat or ESPEasy serial server
MQTT_URI: mqtt://mqtt_broker:[email protected]
BRIDGE_IP: 192.168.1.163
BRIDGE_PORT: 8899
TZ: America/Los_Angeles
LOG_LEVEL: WARN # Any of FATAL, ERROR, WARN, INFO or DEBUG
networks: {}
Using Mosquito in HA, user name is mqtt_broker, password has no special characters, Ha is on 192.168.1.110
Does the docker container start correctly? Do you get anything in the docker logs docker logs bwalink ? Set the LOG_LEVEL to INFO or DEBUG and restart the container.
[06:09:41] INFO: Starting BWALink addon...
[06:09:41] INFO: Setting addon timezone to America/Chicago based on the system timezone.
[06:09:42] INFO: Starting mqtt bridge connecting tcp://192.168.1.163:8899/ to mqtt://core-mosquitto:1883
no matter how many times I refresh. I expected something in MQTT Explorer as I’m subscribed to homie/# but nothing there. I have the Serial Port & Communication Port settings of the Elfin-EW11 set to your spec. I tried reversing the RS485 A and B wires but after a couple minutes my hot tub had a communication error so switched it back.
Another thing to note is that in the Elfin web interface Status section there are 0 bytes being sent so maybe MQTT has no data to work with?
@jshank Thanks for all the time and effort that you’ve put into this! Just about to pull the trigger and order the require parts. My tub is very similar to yours. However, a small question: You mentioned a media box / pocket. I’m assuming that’s for if you have a tub with speakers? Mine doesn’t, and I don’t see any additional boxes or pockets where it would make sense to put the wifi device. Should I get a waterproof enclosure for it then?
I was able to fit mine behind a corner trim piece between the insulation and the bracket that holds the trim in place. That way if I need to service the Wi-Fi adapter I only have to undo two screws and remove the trim to access. The cable I connected to was long enough. Is it water proof, no, but I’ve never had an issue with moisture in that spot. I have a vita spa, but it looks similar in construction to a Sinclair, so maybe all you need to do is remove a corner trim piece.
Has anyone been able to read out data from GS510DZ and vl801 display by the display cable ?
I have build the PCB from magnusPers GitHub project, but having problem getting any reliable data out of it.
Some posts back I asked if anyone had this working with a Balboa GS523DZ with a VL801D panel.
The UK weather has been so poor I have only just managed to build and try the code and setup on this link:
School boy error mounting the D1 mini not leaving enough clearance for the USB plug so notched the board as a simple quick fix.
The inside panels of my Hot Tub have foil shielding which dropped the wifi signal but still good enough to maintain a connection.
I’m now going to focus on working on the most efficient method of heating the Spa at lower cost tariff times etc… Also do some experiments dropping the temperature a deg or so and just remotely increase set temp prior.
Very interested in any thoughts on this and how people optomised the energy use.
Hi all, I’m a little late to the party here and I need a little guidance (well actually, probably a lot of guidance!!). I am not from a coding background so a lot of this is very new to me, I sort of get the basics but that’s about it. I am an electrical engineer and was in the process of putting together a solution to remotely control my hot tub via a PLC controller and a few contactors and relays etc when I came across this guide. I work with Modbus devices on a regular basis at work so I was very excited to find the hot tub communicates via RS-485 as if I can get it working I would be able to have much better control and more options when it comes to the energy saving strategy I am wanting to implement.
I have been trying to follow the guide and decided to go down the V1 route as I had an old Pi1 and a usb WiFi adaptor lying around back from when I used them to run Kodi. Everything was going well until I got to to the bwa_mqtt_bridge.service, I cannot get it to run, I keep getting the following error -
Job for bwa_mqtt_bridge.service failed because the control process exited with error code.
See “systemctl status bwa_mqtt_bridge.service” and “journalctl -xeu bwa_mqtt_bridge.service” for details.
When I run systemctl status bwa_mqtt_bridge.service I get the following
From what I have googled it looks to be an issue with the user not being found or something, I can see the service also fails while the Pi is booting up so I am assuming its a local issue on the Pi and not on the MQTT Broker end? I have tried various username and password combinations but nothing is working. This might be a very simple fix but I am stumped, I’ve been working on it on and off for about 2 days now and still no further towards a solution so I am throwing myself at your mercy
Well it looks like I managed to sort it, I merely had to change the user to the user I logged into the Pi with and it seemed to work.
Thank you to everyone that contributed to this project
Now I need to turn my attention to transposing the controls strategy I was going to use into Node-Red. The basics of it are as follows
Set HT to run at 26c when not in use (ie through the week)
Schedule from Google Calendar to set HT to target temp for use
Implement weather compensation to set target temp based on local ambient temp
Off/On/Auto selector switch, selecting On reverts back to Auto after 48hrs
Override to adjust target temp that resets at midnight
I saw further up the thread that someone had set a ‘ready in X hours’ input up, I really like that idea so will try to integrate that too
The next piece of the puzzle for the HT is to monitor the energy consumption so I can fine tune the controls strategy for maximum efficiency, I had intended to use a 0-10v split CT, I just need to work out how to integrate that into the Pi and then pull that into HA or Node-Red
And last but not least I have found a water monitor that measures PH etc that has a modbus output, if I could also integrate this that would be idea, as I could set alerts up to stay on top of the chemicals
From my side (With the esp8266) approach it has worked flawless since installation. Only this last week I have seen a few random changes in the spa set temperature value via mqtt. I’ve not resolved the reason why but for some reason older backups of HA do not seem affected. Anyway…
I’ve implemented a number of your ideas. For me I tend to use the Tub every day due to back pain which it helps with. I therefore tend to keep the tub at 37 Deg C and heat to 38 before use. It’s quite a quick heat up for one degree but you can see a general reduction in energy use over time.
The time to heat up function works well. I had to tune config to match accurate times - easy to be fair.
I like the idea of the weather compensation, will look into this.
I purchased a low cost Tuya device that clamped around the live connection which gives me a wireless power / current / energy usage that is quite accurate. It gives a good daily look at tub energy.
From an automation perspective I have one that alerts me if the temperature set level <37 Deg or >38.5 Degrees. It’s come into use a few times when someone has accidently changed the temperature putting the lid down.
I’m looking at my Electricity tariff and wondering if one of the lower cost kWh rates overnight would allow me to take advantage of a higher heat-up that would decay during the day. The tub is quite well insulated to tends to not lose too much heat when the cover is on.
It’s definitely on of the ‘best’ HA projects I’ve added.
Cheers
