scooter1556/hass-addons

A collection of Home Assistant OS addons

hass-addons's Issues

Error starting glow2mqtt.py

Since v1.1.2, error starting glow2mqtt.py:

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
Using external MQTT broker.
parse error: Expected string key before ':' at line 1, column 4
[05:40:25] ERROR: Unknown HTTP error occured
Starting glow2mqtt.py...
usage: glow2mqtt.py [-h] [--glow_provider GLOW_PROVIDER] --glow_device
GLOW_DEVICE --glow_username GLOW_USERNAME --glow_password
GLOW_PASSWORD [--mqtt_address MQTT_ADDRESS]
[--mqtt_port MQTT_PORT] [--mqtt_username MQTT_USERNAME]
[--mqtt_password MQTT_PASSWORD] [--homeassistant]
[--debug]
glow2mqtt.py: error: argument --mqtt_port: invalid int value: 'null'
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

I should be using the internal MQTT broker.

OSError: [Errno 99] Address not available

I am new to home assistant so this may be my issue rather than the add on. When I start the addon I see the following in the log ... I am unsure why I would get an OS error on the address

[s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] done. [services.d] starting services [services.d] done. MQTT found in this Home Assistant instance. Starting ginlong-wifi-mqtt.py... Configuring Home Assistant... Traceback (most recent call last): File "/ginlong-wifi-mqtt.py", line 108, in <module> sock.bind((listen_address, listen_port)) OSError: [Errno 99] Address not available [cmd] /run.sh exited 1 [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal.

I have the Listen address set to 192.168.0.249 and the port 9999 .. I have set up server b in the data stick and added the ha server ip - both are fixed IP addresses (the data stick configured as fixed, the ha server as reserved). I am able to logon to the data logger with the browser.

I am running HA in a virtual box under windows

Getting errors in the log - Template variable warning: 'dict object' has no attribute

Since uninstalling and re-installing the add on today I am seeing errors in the log every minute .. for example:

2022-12-26 23:59:50.730 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'dict object' has no attribute 'gas_mtr' when rendering '{{ value_json.gas_mtr}}'
2022-12-26 23:59:50.735 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'dict object' has no attribute 'watt_now' when rendering '{{ value_json.watt_now}}'
2022-12-26 23:59:50.736 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'dict object' has no attribute 'elec_imp' when rendering '{{ value_json.elec_imp}}'
2022-12-26 23:59:50.738 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'dict object' has no attribute 'elec_exp' when rendering '{{ value_json.elec_exp}}'

My guess is I have done something when I uninstalled and re-installed but don't know what ...

As far as I can see my energy data is going to the dashboard - Smart Meter Electricity: Power seems correct and the HA energy dashboard appears to be showing the correct data ...

Any help would be appreciated.

gas_meter has unit kWh which is unsupported for device_class gas

Just installed 1.2.0 and see an error in the log for unit of measure - I am unsure if this was there before as I don't have the prior logs (2 updates today)

2022-08-16 11:20:10.064 WARNING (Recorder) [homeassistant.components.sensor.recorder] sensor.glow_441793525f6c_gas_meter has unit kWh which is unsupported for device_class gas

Mqtt username not passed inside container

Hi,

im recently discovered your addon. It works well when running from docker cmd or natively. But addon has an issue: mqtt_username not passed inside container.

00:00:00 python3 -u /glow2mqtt.py --glow_device <REDACTED> --mqtt_address 192.168.1.101 --mqtt_port 1883 --mqtt_username null --mqtt_password <REDACTED> --glow_username <REDACTED> --glow_password <REDACTED> --glow_provider HILD --homeassistant

Looks like issue here:

https://github.com/scooter1556/hass-addons/blob/main/glow2mqtt/run.sh#L13

run.sh require mqtt_user, but option named(webUI) mqtt_username

Add-on crashes and is not restarted by watchdog

I've had glow2mqtt set up and running for a couple of months (not local MQTT). Occasionally there have been hiccups with incorrect data entering the database (isolated readings of millions or billions of kWh) which I've corrected using the statistics tool in Home Assistant. However, in the last few days, the Glow2MQTT add-on has been crashing with the error log below and has not been restarting.

Home Assistant is fully updated:
Home Assistant 2022.11.3
Supervisor 2022.10.2
Operating System 9.3
Frontend 20221108.0 - latest

Running on a RPi 4B (2GB), with the GlowStick CAD for SMETS1 meters and Cloud MQTT from Hildebrand

MQTT found in this Home Assistant instance.
Starting glow2mqtt.py...
MQTT connected...
Connected to Glow MQTT broker...
Configuring Home Assistant...
{'elec_imp': 42743.259, 'watt_now': 396}
Traceback (most recent call last):
File "/glow2mqtt.py", line 240, in
mqttg.loop_forever()
File "/usr/lib/python3.10/site-packages/paho/mqtt/client.py", line 1756, in loop_forever
rc = self._loop(timeout)
File "/usr/lib/python3.10/site-packages/paho/mqtt/client.py", line 1164, in _loop
rc = self.loop_read()
File "/usr/lib/python3.10/site-packages/paho/mqtt/client.py", line 1556, in loop_read
rc = self._packet_read()
File "/usr/lib/python3.10/site-packages/paho/mqtt/client.py", line 2439, in _packet_read
rc = self._packet_handle()
File "/usr/lib/python3.10/site-packages/paho/mqtt/client.py", line 3033, in _packet_handle
return self._handle_publish()
File "/usr/lib/python3.10/site-packages/paho/mqtt/client.py", line 3327, in _handle_publish
self._handle_on_message(message)
File "/usr/lib/python3.10/site-packages/paho/mqtt/client.py", line 3570, in _handle_on_message
on_message(self, self._userdata, message)
File "/glow2mqtt.py", line 83, in process_msg
if '00' in data['elecMtr']['0702']['04']:
KeyError: '04'
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

Odd issue after 1.2.5 install

I upgraded to 1.2.5 and this stopped any updates flowing to the energy dashboard .. on investigation the current power value was not being updated (I didnt check others but assume they were the same)

I restarted the add on but noticed that the configuration showed local as off so turned it back on again and restarted again .. "local" again showed as off (but maybe I failed to save it!)...

In the log the addon showed connected to the broker but no data was being fetched.

I uninstalled the addon and reinstalled and it all sprung back into life....

Nothing really to add but wanted to record the oddness ....

Seems to connect but providing no data

MQTT found in this Home Assistance instance.
Starting glow2mqtt.py...
Configuring Home Assistant...
MQTT connected...
Connected to Glow MQTT broker...

https://dean.so/wp-content/uploads/2022/04/Screenshot-from-2022-04-17-18-03-18.png

This is what was supplied by Hildebrand:
mosquitto_sub --cafile /usr/local/etc/openssl/cert.pem -h glowmqtt.energyhive.com -u brightuser -P brightpass -t SMART/HILD/XXXXXXXXXXXX -p 8883