I would be interested in one of the PCBs if you still have them. My board uses an RJ45 connection so I believe the communication is the same as the GS series.
Looking at this now - JZ6013X1 board
The Elfin EW11A can be powered directly from the molex port ?
What is then required ?
i have MQTT set up for Solar Assistant and Glow CAD
HAOS running on thin client
I can’t find a step by step tutorial unfortunately
Regards Jeff
Hi,
Did you manage to get it all working?
I’m in a similar situation. WiFi is working but the addon is not working. Either not getting data or not updating MQTT as nothing is showing up:
These are my logs:
[13:21:37] INFO: Starting BWALink addon...
[13:21:38] INFO: Setting addon timezone to Europe/London based on the system timezone.
[13:21:38] INFO: Starting mqtt bridge connecting tcp://192.168.0.134:8899/ to mqtt://core-mosquitto:1883
/usr/lib/ruby/gems/3.4.0/gems/mqtt-homie-homeassistant-1.2.1/lib/mqtt/homie/home_assistant/device.rb:48:in 'MQTT::Homie::HomeAssistant::Device#base_hass_config': uninitialized constant MQTT::Homie::HomeAssistant::VERSION (NameError)
config[:origin][:sw_version] ||= MQTT::Homie::HomeAssistant::VERSION
^^^^^^^^^
from /usr/lib/ruby/gems/3.4.0/gems/mqtt-homie-homeassistant-1.2.1/lib/mqtt/homie/home_assistant/property.rb:183:in 'MQTT::Homie::HomeAssistant::Property#publish_hass_component'
from /usr/lib/ruby/gems/3.4.0/gems/mqtt-homie-homeassistant-1.2.1/lib/mqtt/homie/home_assistant/property.rb:50:in 'MQTT::Homie::HomeAssistant::Property#hass_button'
from /usr/lib/ruby/gems/3.4.0/gems/balboa_worldwide_app-2.3.2/exe/bwa_mqtt_bridge:164:in 'block in MQTTBridge#publish_basic_attributes'
from /usr/lib/ruby/gems/3.4.0/gems/homie-mqtt-1.8.0/lib/mqtt/homie/device.rb:60:in 'block in MQTT::Homie::Device#node'
from /usr/lib/ruby/gems/3.4.0/gems/homie-mqtt-1.8.0/lib/mqtt/homie/device.rb:158:in 'MQTT::Homie::Device#init'
from /usr/lib/ruby/gems/3.4.0/gems/homie-mqtt-1.8.0/lib/mqtt/homie/device.rb:56:in 'MQTT::Homie::Device#node'
from /usr/lib/ruby/gems/3.4.0/gems/balboa_worldwide_app-2.3.2/exe/bwa_mqtt_bridge:155:in 'MQTTBridge#publish_basic_attributes'
from /usr/lib/ruby/gems/3.4.0/gems/balboa_worldwide_app-2.3.2/exe/bwa_mqtt_bridge:51:in 'MQTTBridge#initialize'
from /usr/lib/ruby/gems/3.4.0/gems/balboa_worldwide_app-2.3.2/exe/bwa_mqtt_bridge:447:in 'Class#new'
from /usr/lib/ruby/gems/3.4.0/gems/balboa_worldwide_app-2.3.2/exe/bwa_mqtt_bridge:447:in '<top (required)>'
from /usr/bin/bwa_mqtt_bridge:25:in 'Kernel#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: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
Any ideas?
Thanks
Blockquote
Hi,
Did you get it working? I’m at the same stage. Addon installed but no data (nothing in MQTT).
Bit stuck at this point.
Been using this for a while now and works great on ESPHOME:
1 Like
Hi,
What do you have as your MQTT URI?
Your log shows
INFO: Starting mqtt bridge connecting tcp://192.168.0.134:8899/ to mqtt://core-mosquitto:1883
My log has an IP address where yours has core-masquitto, maybe try using your HA IP address.
I have these settings in yaml and it works.
bridge_ip: 192.168.200.221
bridge_port: 8899
socat: false
log_level: WARN
mqtt_uri: mqtt://bwalink:[email protected]:1883
Where …221 is the Elfin EW11, …139 is home assistant and I’ve create a user called bwalink with password bwalink on HA.
Thanks for posting back…
I tried changing the options in the config.ymal to what you suggested (using my ip ect) but still not playing ball. It got a little closer I think. The MQTT connection was made looking at the logs but still errors.
```[17:30:17] INFO: e[32mStarting BWALink addon…e[0m [17:30:17] INFO: e[32mSetting addon timezone to Europe/London based on the system timezone.e[0m [17:30:18] INFO: e[32mUsing bridge script: /usr/lib/ruby/gems/3.4.0/gems/balboa_worldwide_app-2.3.2/exe/bwa_mqtt_bridgee[0m [17:30:18] INFO: e[32mStarting mqtt bridge connecting tcp://192.168.0.134:8899/ to mqtt://core-mosquitto:1883e[0m I, to spa: #BWA::Messages::ConfigurationRequest I, from spa: #<BWA::Messages::FilterCycles cycle1 6:00@23:30 cycle2(enabled) 1:00@12:00> I, from spa: #<BWA::Messages::ControlConfiguration BP6013G1 V65.0> I, from spa: #<BWA::Messages::FilterCycles cycle1 6:00@23:30 cycle2(enabled) 1:00@12:00> I, from spa: #<BWA::Messages::FilterCycles cycle1 6:00@23:30 cycle2(enabled) 1:00@12:00> I, from spa: #<BWA::Messages::ControlConfiguration BP6013G1 V65.0> I, from spa: #<BWA::Messages::ControlConfiguration2 pumps=[2, 1, 0, 0, 0, 0] lights=[true, false] circulation_pump aux=[false, false]> E, {“event”:“bwa_mqtt_bridge_retry”,“error_class”:“NameError”,“error_message”:“uninitialized constant MQTT::Homie::HomeAssistant::VERSION”,“attempt”:1,“base_delay”:1,“max_delay”:60,“capped_delay”:1,“delay”:0.8426118231741748,“jitter”:true} I, to spa: #BWA::Messages::ConfigurationRequest I, from spa: #<BWA::Messages::ControlConfiguration2 pumps=[2, 1, 0, 0, 0, 0] lights=[true, false] circulation_pump aux=[false, false]> I, from spa: #<BWA::Messages::FilterCycles cycle1 6:00@23:30 cycle2(enabled) 1:00@12:00> I, from spa: #<BWA::Messages::ControlConfiguration BP6013G1 V65.0> E, {“event”:“bwa_mqtt_bridge_retry”,“error_class”:“NameError”,“error_message”:“uninitialized constant MQTT::Homie::HomeAssistant::VERSION”,“attempt”:1,“base_delay”:1,“max_delay”:60,“capped_delay”:1,“delay”:0.7371807867357767,“jitter”:true} I, to spa: #BWA::Messages::ConfigurationRequest I, from spa: #<BWA::Messages::FilterCycles cycle1 6:00@23:30 cycle2(enabled) 1:00@12:00> I, from spa: #<BWA::Messages::ControlConfiguration BP6013G1 V65.0> I, from spa: #<BWA::Messages::FilterCycles cycle1 6:00@23:30 cycle2(enabled) 1:00@12:00> I, from spa: #<BWA::Messages::ControlConfiguration BP6013G1 V65.0> I, from spa: #<BWA::Messages::ControlConfiguration2 pumps=[2, 1, 0, 0, 0, 0] lights=[true, false] circulation_pump aux=[false, false]> E, {“event”:“bwa_mqtt_bridge_retry”,“error_class”:“NameError”,“error_message”:“uninitialized constant MQTT::Homie::HomeAssistant::VERSION”,“attempt”:1,“base_delay”:1,“max_delay”:60,“capped_delay”:1,“delay”:0.6067847466824488,“jitter”:true} I, to spa: #BWA::Messages::ConfigurationRequest E, {“event”:“bwa_mqtt_bridge_retry”,“error_class”:“EOFError”,“error_message”:“end of file reached”,“attempt”:1,“base_delay”:1,“max_delay”:60,“capped_delay”:1,“delay”:0.5279781149180319,“jitter”:true} I, to spa: #BWA::Messages::ConfigurationRequest`
Mmm. Those error messages don’t mean anything to me, sorry, but I have just discovered something that may, or may not help.
I just updated Bwalink and it stopped working with this in the log.
> [09:18:24] INFO: e[32mStarting BWALink addon...e[0m
> [09:18:24] INFO: e[32mSetting addon timezone to Europe/London based on the system timezone.e[0m
> [09:18:24] INFO: e[32mStarting mqtt bridge connecting tcp://192.168.200.221:8899/ to mqtt://192.168.200.139:1883e[0m
> /usr/lib/ruby/gems/3.4.0/gems/mqtt-homie-homeassistant-1.2.1/lib/mqtt/homie/home_assistant/device.rb:48:in 'MQTT::Homie::HomeAssistant::Device#base_hass_config': uninitialized constant MQTT::Homie::HomeAssistant::VERSION (NameError)
>
> config[:origin][:sw_version] ||= MQTT::Homie::HomeAssistant::VERSION
> ^^^^^^^^^
> from /usr/lib/ruby/gems/3.4.0/gems/mqtt-homie-homeassistant-1.2.1/lib/mqtt/homie/home_assistant/property.rb:183:in 'MQTT::Homie::HomeAssistant::Property#publish_hass_component'
> from /usr/lib/ruby/gems/3.4.0/gems/mqtt-homie-homeassistant-1.2.1/lib/mqtt/homie/home_assistant/property.rb:50:in 'MQTT::Homie::HomeAssistant::Property#hass_button'
> from /usr/lib/ruby/gems/3.4.0/gems/balboa_worldwide_app-2.3.2/exe/bwa_mqtt_bridge:164:in 'block in MQTTBridge#publish_basic_attributes'
> from /usr/lib/ruby/gems/3.4.0/gems/homie-mqtt-1.8.1/lib/mqtt/homie/device.rb:60:in 'block in MQTT::Homie::Device#node'
> from /usr/lib/ruby/gems/3.4.0/gems/homie-mqtt-1.8.1/lib/mqtt/homie/device.rb:166:in 'MQTT::Homie::Device#init'
> from /usr/lib/ruby/gems/3.4.0/gems/homie-mqtt-1.8.1/lib/mqtt/homie/device.rb:56:in 'MQTT::Homie::Device#node'
> from /usr/lib/ruby/gems/3.4.0/gems/balboa_worldwide_app-2.3.2/exe/bwa_mqtt_bridge:155:in 'MQTTBridge#publish_basic_attributes'
> from /usr/lib/ruby/gems/3.4.0/gems/balboa_worldwide_app-2.3.2/exe/bwa_mqtt_bridge:51:in 'MQTTBridge#initialize'
> from /usr/lib/ruby/gems/3.4.0/gems/balboa_worldwide_app-2.3.2/exe/bwa_mqtt_bridge:447:in 'Class#new'
> from /usr/lib/ruby/gems/3.4.0/gems/balboa_worldwide_app-2.3.2/exe/bwa_mqtt_bridge:447:in '<top (required)>'
> from /usr/bin/bwa_mqtt_bridge:25:in 'Kernel#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
If I roll back to my backup, it works.
[09:19:06] INFO: e[32mStarting BWALink addon...e[0m
[09:19:06] INFO: e[32mSetting addon timezone to Europe/London based on the system timezone.e[0m
[09:19:06] INFO: e[32mStarting mqtt bridge connecting tcp://192.168.200.221:8899/ to mqtt://192.168.200.139:1883e[0m
W, Balboa MQTT Bridge running (version 2.3.2)
First thing to add, I’m not 100% certain I updated correctly, I just overwrote the contents of the addons folder and clicked rebuild in HA but whatever that does, it breaks it.
I just set up a new instance of HA and are trying to get BWALink to work. Got it working on two other instances without issues, but here I’m getting similar issues as listed above.
[18:16:13] INFO: Starting mqtt bridge connecting tcp://192.168.1.251:8899/ to mqtt://core-mosquitto:1883
/usr/lib/ruby/gems/3.4.0/gems/mqtt-homie-homeassistant-1.2.0/lib/mqtt/homie/home_assistant/property.rb:39:in 'MQTT::Homie::HomeAssistant::Property#hass_button': Property must have one valid enum value (ArgumentError)
raise ArgumentError, "Property must have one valid enum value" unless range.length == 1
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
from /usr/lib/ruby/gems/3.4.0/gems/balboa_worldwide_app-2.3.2/exe/bwa_mqtt_bridge:164:in 'block in MQTTBridge#publish_basic_attributes'
from /usr/lib/ruby/gems/3.4.0/gems/homie-mqtt-1.8.0/lib/mqtt/homie/device.rb:60:in 'block in MQTT::Homie::Device#node'
from /usr/lib/ruby/gems/3.4.0/gems/homie-mqtt-1.8.0/lib/mqtt/homie/device.rb:158:in 'MQTT::Homie::Device#init'
from /usr/lib/ruby/gems/3.4.0/gems/homie-mqtt-1.8.0/lib/mqtt/homie/device.rb:56:in 'MQTT::Homie::Device#node'
from /usr/lib/ruby/gems/3.4.0/gems/balboa_worldwide_app-2.3.2/exe/bwa_mqtt_bridge:155:in 'MQTTBridge#publish_basic_attributes'
from /usr/lib/ruby/gems/3.4.0/gems/balboa_worldwide_app-2.3.2/exe/bwa_mqtt_bridge:51:in 'MQTTBridge#initialize'
from /usr/lib/ruby/gems/3.4.0/gems/balboa_worldwide_app-2.3.2/exe/bwa_mqtt_bridge:447:in 'Class#new'
from /usr/lib/ruby/gems/3.4.0/gems/balboa_worldwide_app-2.3.2/exe/bwa_mqtt_bridge:447:in '<top (required)>'
from /usr/bin/bwa_mqtt_bridge:25:in 'Kernel#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
Is it possible you can share the files you are using to build the add-on so i can try them my end?