danielwelch / hassio-zigbee2mqtt

Hass.io add-on for zigbee2mqtt
Apache License 2.0
566 stars 189 forks source link

Can't add repository in Home Assistant. #482

Closed frso80 closed 3 years ago

frso80 commented 3 years ago

zigbee2mqtt add-on version (if edge, please report commit hash): None Operating environment (HassOS, Virtual Machine, Device/platform running Home Assistant):

HassOS 4.17 running on Raspberry Pi 4 4GB.

Description of problem: Can't add the repo in Home Assistant.

Your entire configuration from the frontend (with sensitive fields redacted):

Not relevant.

Your logs from Home Assistant

20-12-02 17:18:53 WARNING (MainThread) [supervisor.store.data] Can't read /data/addons/git/7ad98f9c/zigbee2mqtt/config.json: does not match regular expression for dictionary value @ data['schema']['frontend']['host']. Got 'string?'
20-12-02 17:18:53 WARNING (MainThread) [supervisor.store.data] Can't read /data/addons/git/7ad98f9c/zigbee2mqtt-edge/config.json: does not match regular expression for dictionary value @ data['schema']['frontend']['host']. Got 'string?'
yabbah commented 3 years ago

I was just about to create an issue. Have the same issue here ..

mangant commented 3 years ago

I have same issue too.

Mr-Groch commented 3 years ago

I've added earlier, but can't reload and update, supervisor logs:

20-12-02 18:44:33 WARNING (MainThread) [supervisor.store.data] Can't read /data/addons/git/7ad98f9c/zigbee2mqtt/config.json: does not match regular expression for dictionary value @ data['schema']['frontend']['host']. Got 'string?'
20-12-02 18:44:33 WARNING (MainThread) [supervisor.store.data] Can't read /data/addons/git/7ad98f9c/zigbee2mqtt-edge/config.json: does not match regular expression for dictionary value @ data['schema']['frontend']['host']. Got 'string?'
20-12-02 18:44:34 WARNING (MainThread) [supervisor.store.data] Can't read /data/addons/git/7ad98f9c/zigbee2mqtt/config.json: does not match regular expression for dictionary value @ data['schema']['frontend']['host']. Got 'string?'
20-12-02 18:44:34 WARNING (MainThread) [supervisor.store.data] Can't read /data/addons/git/7ad98f9c/zigbee2mqtt-edge/config.json: does not match regular expression for dictionary value @ data['schema']['frontend']['host']. Got 'string?'
rickyoleary commented 3 years ago

Same issue, finally got everything delivered and ran into the issue first off, glad I'm not the only one. :)

LaurentMicrotec commented 3 years ago

Same issue!

20-12-02 19:10:20 WARNING (MainThread) [supervisor.store.data] Can't read /data/addons/git/7ad98f9c/zigbee2mqtt/config.json: does not match regular expression for dictionary value @ data['schema']['frontend']['host']. Got 'string?'
20-12-02 19:10:20 WARNING (MainThread) [supervisor.store.data] Can't read /data/addons/git/7ad98f9c/zigbee2mqtt-edge/config.json: does not match regular expression for dictionary value @ data['schema']['frontend']['host']. Got 'string?'
ciotlosm commented 3 years ago

This is a problem with the new release of the add-on. You can use https://github.com/zigbee2mqtt/hassio-zigbee2mqtt until we get this fixed here as well.

Issue was raised now as well here: https://github.com/danielwelch/hassio-zigbee2mqtt/issues/483

Update: New PR created in #484

SzemiSun commented 3 years ago

I have same issue too.

andriej commented 3 years ago

@ciotlosm will there be some kind of hand-over of repos?

ciotlosm commented 3 years ago

@andriej I'll try to outline here the steps that I had in mind:

  1. Keep both repos on at the same time until enough people test out zigbee2mqtt/hassio-zigbee2mqtt version to iron out potential problems
  2. Merge back to danielwelch/hassio-zigbee2mqtt all changes: at this stage, docker images would get consumed from dockerhub zigbee2mqtt org
  3. Reset zigbee2mqtt/hassio-zigbee2mqtt repo so it is no longer a fork of danielwelch/hassio-zigbee2mqtt
  4. Update zigbee2mqtt documentation (not the add-on) to reflect zigbee2mqtt/hassio-zigbee2mqtt repo as main
  5. Cleanup danielwelch/hassio-zigbee2mqtt code to allow only configs pointing to dockerhub zigbee2mqtt org
  6. Keep danielwelch/hassio-zigbee2mqtt as a lightweight config only version to store previous/older version in case there are severe bugs that are not solved in time (to avoid people getting problems with their significant other)
LaurentMicrotec commented 3 years ago

Wow, that's a lot of work, isn't it? I don't understand everything, I don't have the level. But we can hope with a new functional add on in how long?

ciotlosm commented 3 years ago

@LaurentMicrotec would think in around 1 month we should be able to have a transition. Maybe sooner if I get more time.

phtg commented 3 years ago

Wow, that's a lot of work, isn't it? I don't understand everything, I don't have the level. But we can hope with a new functional add on in how long?

@LaurentMicrotec the handover doesn't have much to do with the state of this addon, when this issue is fixed danielwelch/hassio-zigbee2mqtt should work again. Methinks for home assistant supervisor users it should just be a change in repositories and get the new version and stop the old. (although some entities changed when I switched from danielwelch to zigbee2mqtt)

rickyoleary commented 3 years ago

This is a problem with the new release of the add-on. You can use https://github.com/zigbee2mqtt/hassio-zigbee2mqtt until we get this fixed here as well.

Issue was raised now as well here: #483

Update: New PR created in #484

Hi, I am using this as suggested and I can download the repo and install the addon. But it just won't seem to go past:

zigbee2mqtt@1.16.1 start /app node index.js

in the logs. Everything I'm looking at online, after this line it should launch zigbee-shephard etc. But mine just stops and it's not working, is it related to the add on that has been suggested? I am using Home Assistant, version: 2020.12.2 and version 1.16.1-1 of Zigbee2mqtt as per above repo URL.

Log:

[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] socat.sh: executing... 
[10:55:18] INFO: Socat not enabled, marking service as down
[cont-init.d] socat.sh: exited 0.
[cont-init.d] zigbee2mqtt.sh: executing... 
[10:55:19] INFO: MQTT available, fetching server detail ...
[10:55:19] INFO: MQTT credentials not configured, trying to auto-discovering ...
[10:55:20] INFO: Configuring'addons' mqtt user
[10:55:20] INFO: Previous config file found, checking backup
[10:55:20] INFO: Creating backup config in '/config/zigbee2mqtt/.configuration.yaml.bk'
[10:55:20] INFO: Adjusting Zigbee2mqtt core yaml config with add-on quirks ...
[cont-init.d] zigbee2mqtt.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[10:55:21] INFO: Handing over control to Zigbee2mqtt Core ...
zigbee2mqtt@1.16.1 start /app
node index.js

Nothing further here.

Here is the configuration:
data_path: /config/zigbee2mqtt
external_converters: []
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: true
mqtt:
  base_topic: zigbee2mqtt
  username: mqtt
  password: mqtt
  server: 'mqtt://192.168.1.96:1883'
serial:
  port: >-
    /dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0014D9A4B8-if00
advanced:
  log_level: warn
  pan_id: 6754
  channel: 11
  network_key:
    - 1
    - 3
    - 5
    - 7
    - 9
    - 11
    - 13
    - 15
    - 0
    - 2
    - 4
    - 6
    - 8
    - 10
    - 12
    - 13
  availability_blocklist: []
  availability_passlist: []
device_options: {}
blocklist: []
passlist: []
queue: {}
frontend:
  port: 8099
experimental:
  new_api: false
socat:
  enabled: false
  master: 'pty,raw,echo=0,link=/dev/ttyZ2M,mode=777'
  slave: 'tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5'
  options: '-d -d'
  log: true
ciotlosm commented 3 years ago

@rickyoleary That is normal as you have no errors. If you want more logs you need to use info or debug in your config for log_level here:

advanced:
  log_level: warn