@andlo wrote:

My season sensor reports that is is autumn, but only few days until christmas and living in Denmark, it defently should be winter at the moment.

But how to get the sensor to report correct season ?

Posts: 5

Participants: 2

Read full topic

@Andrewa wrote:

Hi guys, i’m new here, i have create in my home a domotic project using arduino mega 2560 connect with lan and about 40 sensor, relays. Now i use blynk but i would use Home Assistant. How proceed?

Posts: 1

Participants: 1

Read full topic

@JayF wrote:

Hey guys!

Yesterday I’ve been struck by an idea of what would be the probable solution and it turns out it worked for me.

I’m running Home-Assistant on Docker from within an Intel NUC. I’ve never been able to find the Apple TV while I was able to detect it manually from outside the Docker container.

If you are running several Docker containers on the same hardware, chances are that you actually reserved the port 8123 for HA usage. If you did, then the command line in order to create the Docker container would have the -p 8123:8123 command in it.

I figured out that would be the problem as the only to communicate with the container is by going through the port 8123. Therefore, only having 8123 as a communication won’t allow any reliable discovery or anything else outside of the Docker network.

I then decided to stop all containers on my Intel NUC, deleted my HA container and recreated it --net=host and voilà, the AppleTV is now being discovered and I can control it remotely no problems!

The actual command I typed in was:
sudo docker run -d --name="home-assistant" --net=host --restart=always --device=/dev/ttyACM0 --device=/dev/ttyUSB0 -v /home/jayf/Dockerconf/HomeAssistant:/config -v /var/run/docker.sock:/var/run/docker.sock -e "TZ=America/Montreal" -p 8123:8123 homeassistant/home-assistant

The --device=/dev/ttyACM0 is being used for my Z-Wave USB dongle. Obviously, the specified port in that command will be ignored as --net=host is being used.

Hopefully it will help others!

Posts: 3

Participants: 2

Read full topic

@Tonita wrote:

Hey guys… I have a Satel Integra with ETHM-1 Plus.

I would like to make Home Assistant work to use Alexa and Siri to turn the lights on and off (also programming various events now, with the INTEGRA app, I can turn the lights on and off but it doesn’t work with alexa and siri).
Who can help me?

I searched for something here but I didn’t find anyone talking about it …

I have recently started using home assistant so I am a beginner…

Posts: 1

Participants: 1

Read full topic

@hjbotha wrote:

I’ve set up a tablet to act as a dashboard, and I’d like to add a card to it highlighting any issues which we might need to take care of.

For example, remote batteries getting low.

My current attempt uses an entity-filter card and booleans which are hidden if they are disabled. Automations in node-red will enable these booleans as they become things which we need to pay attention to.

This is not ideal for a couple of reasons:

• We could accidentally disable them from this page, so if I use this method I’d like some way to make them view-only
• I have to create a boolean for each potential issue I implement
• I can’t display more information about the issue

I’m thinking the ideal thing would probably be a text array which could be set from node-red and viewed in Lovelace. Then node-red could add to and subtract from that array as issues come and go, and lovelace could hide the card if it’s empty, but as far as I can tell there’s no entity that would allow that.

What approach have/would you take for this?

Cheers

Posts: 3

Participants: 2

Read full topic

@gromar wrote:

Hello all,

I’ve got a RF433Mhz device - EV1527 which is a relay that turns on/off lamps in my house (it’s showed in HA as light.rfcustom_524643_0 in my case).
I also have a PZEM004 electricity monitor between the relay and lamp sockets. If I start switching on and off EV1527 the status of the switched lamp may be wrong (the status in HA will be showed wrong - physical light will be ON and the status in HA will be OFF).
How can I set the right status of the relay depending of value from PZEM004 electricity monitor (sensor.pobor_pradu_swiatlo_korytarz_energy_current) - for example if I switch on light the electricity monitor will show that current is 0.2 A [higher than 0], in that case change status of light switch to ON and if current is 0 A then change status to off).

Thank you in advance for any tip!

Posts: 3

Participants: 2

Read full topic

@infiniteloop wrote:

Setting a new Raspberry 3 to host Rhasspy and LMS bring me to a strange issue:

• First attempt
  Starting with a clean Raspbian image, I’ve installed Rhasspy as per instruction and it was working flawless.
  Then I’ve installed LMS and squeezelight client cause I need to use the raspberry in a multiroom audio system via airplay.
  After LMS installation Rhasspy stopped working and the whole system became sluggish and unresponsive.

• Second attempt:
  Started from scratch I proceeded backwards.
  I’ve installed LMS and client, then Rhasspy and as soon as I’ve set which card to use (Rhasspy settings) again the system became unresponsive, LMS and Rhasspy didn’t work anymore and speakers started to buzz.
  Stopping Rhasspy docker image seems to solve the issue.

Things to note:
I’ve disabled the onboard audio card and I’m using a Respeaker 2 hat.
The issue seems to start when in Rhasspy settings I try to change from default card (for record and play) to Respeaker.
But having disabled the onboard card default card and Respeaker card are the same.

I’ve no idea what to try… Any hint is really appreciated
Thanks

Posts: 1

Participants: 1

Read full topic

@fishertimj wrote:

This is my first post about Rhasspy, having just jumped down the offline voice assistant rabbit hole. I’m only an hour or two in (installed Rhasspy on my NUC via Docker, reading a lot, buying a mic+pi setup, etc.) and color me VERY impressed! @synesthesiam, you have done something really amazing here and I can’t wait to see it continue to develop!

My first of many questions/comments are around the TTS options. The range of choices are much appreciated but none of the fully offline options “wow” me (i.e. are as good or better than Google’s - yes, for obvious reasons) but I do think some of the MaryTTS voices are pretty damn good.

When I was digging around for additional engines to suggest that you add, I came across this open source implementation of WaveNet: https://r9y9.github.io/wavenet_vocoder/. It’s a little over my head, certainly after just 5 minutes of reading, but I’m wondering if there’s an opportunity to use this in some capacity? I’m not sure if it’s a true TTS itself or another layer of processing on top of an existing TTS engine but I’d love any thoughts on it.

Thanks!

Posts: 3

Participants: 2

Read full topic

@jjdegeo wrote:

I’ve noticed after the latest MyQ fix that the cover state no longer changes to opening. As a result when you press the open button you receive no indication that the command was received. Once the door is opened fully the state changes to open. Prior to the last update I would see an immediate change by the up arrow graying out and the down arrow becoming active. Anyone else seeing this?

Posts: 3

Participants: 2

Read full topic

@jamesking wrote:

Hi,

I have a view with 3 thermostat cards, A B and C.

On my phone they show in a vertical stack.

A
B
C

on my laptop they show as 2 devices on the top row, then 1 underneath:

A C
B

I wish for them to show as:

A B
C 

on my laptop screen.

The following code does not work:
https://hastebin.com/hixirigobo.css

They continue to be laid out incorrectly as described above on my laptop.
If I add “min_columns: 2” it lays out correctly on laptop, but with each card being way smaller than it is without the min_columns line. It’s also incorrect on mobile (due to min columns being 2).

Does anyone have idea why the code on hastebin doesn’t work?

Thank you,

James

Posts: 1

Participants: 1

Read full topic

@typhoon2099 wrote:

I understand that some changes have occurred to climate entities in the 103 release. Unfortunately one of the changes seems to have been to remove the climate entity from my Devolo TRV. Without it I can’t see how I’m supposed to set the setpoint of the radiator. Do I need to rollback to 102?

Screenshot_20191215_1941301920×1080 90.9 KB

Posts: 2

Participants: 2

Read full topic

@Henrik1986 wrote:

HI!
My router dosen’t support nat loopback and i’m trying to setup dnsmasq so i can navigate to my duckdns.org when I’m home. The problem is that I can’t get it to work. This is my setup the hass.io add on.

37644×652 22.9 KB

Is the setup right and do I have to do any changes on my router?
As you hear I’m a beginner on this…

Posts: 1

Participants: 1

Read full topic

@jkkarlberg wrote:

Ok, so I’m trying to make a sensor that shows the type of garbage and the time it will be collected.
The code below I get from a curl or rest sensor

But it seems that I can’t make the sensors for it,
Anyone has any input to give?

[
  {
    "types": [
      {
        "type": "Tunna 1",
        "address": "Slånbärsvägen 1",
        "pickup_date": "2019-12-20",
        "zip_city": "Motala",
        "formatted": "20 dec",
        "has_deviating_date": false,
        "has_deviating_date_real": false,
        "message": "",
        "week_type": "Ordinarie"
      },
      {
        "type": "Tunna 2",
        "address": "Slånbärsvägen 1",
        "pickup_date": "2019-12-27",
        "zip_city": "Motala",
        "formatted": "27 dec",
        "has_deviating_date": false,
        "has_deviating_date_real": false,
        "message": "",
        "week_type": "Ordinarie"
      },
      {
        "type": "Trädgård",
        "address": "Slånbärsvägen 1",
        "pickup_date": "2020-04-07",
        "zip_city": "Motala",
        "formatted": "7 apr",
        "has_deviating_date": false,
        "has_deviating_date_real": false,
        "message": "",
        "week_type": "Ordinarie"
      }
    ],
    "address": "Slånbärsvägen 1",
    "city": "Motala",
    "has_deviating": false
  }
]

i have tried with both command line sensor and restful sensor

sensor:
  - platform: command_line
    command: "curl -XGET -H 'X-App-Identifier: 36202cbd6d9cbd54' 'https://motala.avfallsappen.se/wp-json/app/v1/next-pickup' | jq '.[] | {test:.types[]}'"
    name: test2
    value_template: "{{ value_json[0]['test']['type'] }}"

  - platform: rest
    resource: https://motala.avfallsappen.se/wp-json/app/v1/next-pickup
    headers:
      X-App-Identifier: 36202cbd6d9cbd54
      Content-type: application/json
    name: test4
    value_template: "{{ value_json[0].types[0] }}"
  #value_template: "{{ value_json[0]['type'] }}"
  #value_template: '{{ (value | from_json)[0].types }}'

i´ve tried parsing json response with jq but no luck there either.

It seems that my json respons is weird against the examples ive found by search

Posts: 4

Participants: 2

Read full topic

@Daniel-san wrote:

Hi Guys, I created a few automations to automatically turn off the lights after X amount of time.
So far… they “work” but after living with these for a few days, I’ve noticed that my code is flawed.

here’s my code:

- alias: Master BedRoom Bathroom Auto Turn OFF lights
  trigger:
  - platform: state
    entity_id: light.master_bedroom_bathroom_lights
    from: 'off'
    to: 'on'
  action:
  - delay: 900
  - service: homeassistant.turn_off
    entity_id: light.master_bedroom_bathroom_lights
  id: 5602ac6d92c44a5a92c4545454b4454dkhfge code here

What I’ve been noticing is that when I trigger my automation by turning the light on, it will turn off in 15 minutes no matter what.

Problem is, if I manually turn off the light before the 15 minutes (say 13 minutes for example) and then turn the light back on, that original 15 minutes is still counting down and will turn the light off.

How can I avoid this?
How can I cancel the 15-minute delay if I manually turn the light off? or how can I restart the 15-minute delay if I turn the light on again?

I think I need to run scripts… but I don’t know how they work, (I have none today)

Posts: 2

Participants: 2

Read full topic

@telecomguy wrote:

Yesterday I bought an Ikea TRÅDFRI Wireless control outlet to be able to pair with Home Assistant so I could use it to turn my Christmas tree lights on/off. I run HA in a docker container on unRAID, and it was running version 0.102.3 and I upgraded this afternoon to 0.103.0. I have a HUSBZB-1 connected to the server which I pass through to the docker container without any issues. I have other Ikea TRÅDFRI lights that are connected to HA without any issues. They were however paired to HA in a previous version. When I plugged the outlet in and hit the reset/pair button on it, I checked HA to see if it would show up. I did not see a new device showing under the integration, but I do see this in the logs:

2019-12-15 14:43:54 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.23387683242960] Error handling message: Unknown error
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/decorators.py", line 19, in _handle_async_response
    await func(hass, connection, msg)
  File "/usr/src/homeassistant/homeassistant/components/device_automation/__init__.py", line 215, in websocket_device_automation_list_triggers
    triggers = await _async_get_device_automations(hass, "trigger", device_id)
  File "/usr/src/homeassistant/homeassistant/components/device_automation/__init__.py", line 134, in _async_get_device_automations
    for domain in domains
  File "/usr/src/homeassistant/homeassistant/components/device_automation/__init__.py", line 108, in _async_get_device_automations_from_domain
    return await getattr(platform, function_name)(hass, device_id)
  File "/usr/src/homeassistant/homeassistant/components/zha/device_trigger.py", line 65, in async_get_triggers
    zha_device = await async_get_zha_device(hass, device_id)
  File "/usr/src/homeassistant/homeassistant/components/zha/core/helpers.py", line 142, in async_get_zha_device
    return zha_gateway.devices[ieee]
KeyError: 00:0d:6f:00:12:00:b1:81
2019-12-15 14:43:54 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.23387683242960] Error handling message: Unknown error
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/decorators.py", line 19, in _handle_async_response
    await func(hass, connection, msg)
  File "/usr/src/homeassistant/homeassistant/components/device_automation/__init__.py", line 187, in websocket_device_automation_list_actions
    actions = await _async_get_device_automations(hass, "action", device_id)
  File "/usr/src/homeassistant/homeassistant/components/device_automation/__init__.py", line 134, in _async_get_device_automations
    for domain in domains
  File "/usr/src/homeassistant/homeassistant/components/device_automation/__init__.py", line 108, in _async_get_device_automations_from_domain
    return await getattr(platform, function_name)(hass, device_id)
  File "/usr/src/homeassistant/homeassistant/components/zha/device_action.py", line 59, in async_get_actions
    zha_device = await async_get_zha_device(hass, device_id)
  File "/usr/src/homeassistant/homeassistant/components/zha/core/helpers.py", line 142, in async_get_zha_device
    return zha_gateway.devices[ieee]
KeyError: 00:0d:6f:00:12:00:b1:81

Any ideas what could be causing this? I assume now that HA doesn’t have an option to listen for new devices anymore, it’s always listening for new devices. But I don’t see a new entity showing up in HA for the outlet so it does not seem like it’s being added at all.

Posts: 3

Participants: 2

Read full topic

@liksvette wrote:

I am stumped.
Can anyone please tell me whats wrong with the value template below?

- platform: template
  sensors:
    garage_humidity_difference:
      value_template: '{{ state_attr('weather.met_no', 'humidity') - ( states('sensor.garage_sensor_humidity')|int ) }}'
      friendly_name: 'Luftfuktighet ute vs garasje'
      #entity_id: sensor.garage_humidity_difference
      unit_of_measurement: '%'

It resolves in the template editor, but when I add it to my config I get the following error:

Error loading /config/configuration.yaml: while parsing a block mapping
in “/config/sensors/garage_humidity_difference.yaml”, line 4, column 7
expected , but found ‘< scalar >’
in “/config/sensors/garage_humidity_difference.yaml”, line 4, column 39

I can’t for the life of me see what’s wrong.

Posts: 3

Participants: 2

Read full topic

@Yep wrote:

Hello fellow Home Assistant users !

I bought a Fibaro FGBS222 Smart Implant to be able to control my garage door from my phone. Basically, there’s a wall control unit where I wanted to put the Smart Implant, but I can’t get it to work…

The garage door system is a Sommer Pro+, and here’s a wiring diagram of what I did.

wiring2000×1382 469 KB

I was able to add the Smart Implant to home assistant, so that means the unit is correctly powered on, but I’m not quite sure about the wiring with the input and output. Without the Smart Implant, if I make cables C1 and C2 touch for about 1 second, the garage door opens or closes (depending on its current position). I was counting on the Smart Implant to act as I did manually, ie I need the Smart Implant to make both cables “touch” for a very short time.

I thought I did everything right, but first thing that seemed strange to me is when I modified the parameter 156 - Output 1 - auto off to 5 (which I believe gives a value of 0.5 seconds, which should be sufficient), but when I disconnected the Smart Implant (to try various things), when I got back to the Node configuration options in Home Assistant, the value seemed to go back to 0.

Then, I went to Developer Tools --> Services and tried to call the service “switch.turn_on” on the entity switch.fibaro_system_fgbs222_smart_implant_switch, but nothing happened.

Am I missing something here ? Is it the wiring that’s bad, the way I added/configured the Smart Implant, or is there something else going on ?

Does anyone have any idea on how I can begin to troubleshoot the whole thing ? I’m a bit of a beginner with Z-Wave, because I never really had problems before, the Z-Wave devices I have all work perfectly…

Thanks in advance for your help !

Posts: 1

Participants: 1

Read full topic

@Niall wrote:

Hello,

On Friday morning I woke up and my lights did not turn on as I moved around the house. Upon further digging I found that my zigbee2mqtt add-on was not working.

I have HA (0.103.0) installed on a Linux VM (Ubuntu 18 LTE) within Proxmox (proxmox-ve: 6.1-2 (running kernel: 5.3.13-1-pve)).

First I tested that Proxmox could see the USB stick:

root@pve:~$  ls -l /dev/serial/by-id
total 0
lrwxrwxrwx 1 root root 13 Dec 15 11:18 usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0018E1F5E8-if00 -> ../../ttyACM0
root@pve:~$ test -w /dev/ttyACM0 && echo success || echo failure
success

I then checked within the HA VM with the same test:

ls -l /dev/serial/by-id
total 0
lrwxrwxrwx 1 root root 13 Dec 15 11:13 usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0018E1F5E8-if00 -> ../../ttyACM0
root@home_assistant_server:~$ test -w /dev/ttyACM0 && echo success || echo failure
success

It all looked fine so I started the zigbee2mqtt add-on, my config is:

{
  "data_path": "/share/zigbee2mqtt",
  "devices": "devices.yaml",
  "groups": "groups.yaml",
  "homeassistant": true,
  "permit_join": false,
  "mqtt": {
    "base_topic": "zigbee2mqtt",
    "server": "mqtt://10.10.20.221:1883",
    "user": "mqtt_broker",
    "password": "Password"
  },
  "serial": {
    "port": "/dev/ttyACM0"
  },
  "advanced": {
    "pan_id": 6754,
    "channel": 11,
    "network_key": [
      9,
      8,
      3,
      11,
      9,
      13,
      15,
      1,
      2,
      4,
      6,
      4,
      11,
      16,
      13
    ],
    "availability_blacklist": [],
    "log_level": "debug",
    "baudrate": 115200
  },
  "ban": [],
  "whitelist": [],
  "queue": {},
  "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",
    "restartdelay": 1,
    "initialdelay": 1,
    "options": "-d -d",
    "log": false
  }
}

I got the following error:

	./run.sh: line 16: [Info] Configuration backup found in /share/zigbee2mqtt/.configuration.yaml.bk. Skipping config backup.: No such file or directory
	[Info] Socat is DISABLED and not started
	2019-12-15T11:51:39: PM2 log: Launching in no daemon mode
	2019-12-15T11:51:39: PM2 log: App [npm:0] starting in -fork mode-
	2019-12-15T11:51:39: PM2 log: App [npm:0] online
	> zigbee2mqtt@1.7.1 start /zigbee2mqtt-1.7.1
	> node index.js
	zigbee2mqtt:info  2019-12-15T11:51:41: Logging to directory: '/share/zigbee2mqtt/log/2019-12-15.11-51-40'
	zigbee2mqtt:debug 2019-12-15T11:51:41: Removing old log directory '/share/zigbee2mqtt/log/2019-12-14.23-31-31'
	zigbee2mqtt:debug 2019-12-15T11:51:41: Loaded state from file /share/zigbee2mqtt/state.json
	zigbee2mqtt:info  2019-12-15T11:51:41: Starting zigbee2mqtt version 1.7.1 (commit #unknown)
	zigbee2mqtt:info  2019-12-15T11:51:41: Starting zigbee-herdsman...
	zigbee2mqtt:debug 2019-12-15T11:51:41: Using zigbee-herdsman with settings: '{"network":{"panID":"HIDDEN","extendedPanID":["HIDDEN"],"channelList":[11],"networkKey":"HIDDEN"},"databasePath":"/share/zigbee2mqtt/database.db","databaseBackupPath":"/share/zigbee2mqtt/database.db.backup","backupPath":"/share/zigbee2mqtt/coordinator_backup.json","serialPort":{"baudRate":115200,"rtscts":true,"path":"/dev/ttyACM0"}}'
	zigbee2mqtt:error 2019-12-15T11:51:41: Error while starting zigbee-herdsman
	zigbee2mqtt:error 2019-12-15T11:51:41: Failed to start zigbee
	zigbee2mqtt:error 2019-12-15T11:51:41: Exiting...
	zigbee2mqtt:error 2019-12-15T11:51:41: Error: Error while opening serialport 'Error: Error: No such device, cannot open /dev/ttyACM0'
		at Znp.<anonymous> (/zigbee2mqtt-1.7.1/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:109:32)
		at Generator.next (<anonymous>)
		at /zigbee2mqtt-1.7.1/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:8:71
		at new Promise (<anonymous>)
		at __awaiter (/zigbee2mqtt-1.7.1/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:4:12)
		at SerialPort.serialPort.open (/zigbee2mqtt-1.7.1/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:107:49)
		at SerialPort._error (/zigbee2mqtt-1.7.1/node_modules/zigbee-herdsman/node_modules/@serialport/stream/stream.js:197:14)
		at binding.open.then.err (/zigbee2mqtt-1.7.1/node_modules/zigbee-herdsman/node_modules/@serialport/stream/stream.js:241:12)
	npm
	 ERR! code ELIFECYCLE
	npm ERR! errno 1
	npm
	 ERR! zigbee2mqtt@1.7.1 start: `node index.js`
	npm ERR! Exit status 1
	npm ERR! 
	npm ERR! Failed at the zigbee2mqtt@1.7.1 start script.
	npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
	2019-12-15T11:51:42: PM2 log: App [npm:0] exited with code [1] via signal [SIGINT]
	2019-12-15T11:51:42: PM2 log: App [npm:0] starting in -fork mode-
	2019-12-15T11:51:42: PM2 log: App [npm:0] online
	> zigbee2mqtt@1.7.1 start /zigbee2mqtt-1.7.1
	> node index.js
	zigbee2mqtt:info  2019-12-15T11:51:43: Logging to directory: '/share/zigbee2mqtt/log/2019-12-15.11-51-43'
	zigbee2mqtt:debug 2019-12-15T11:51:43: Removing old log directory '/share/zigbee2mqtt/log/2019-12-14.23-31-34'
	zigbee2mqtt:debug 2019-12-15T11:51:43: Loaded state from file /share/zigbee2mqtt/state.json
	zigbee2mqtt:info  2019-12-15T11:51:43: Starting zigbee2mqtt version 1.7.1 (commit #unknown)
	zigbee2mqtt:info  2019-12-15T11:51:43: Starting zigbee-herdsman...
	zigbee2mqtt:debug 2019-12-15T11:51:43: Using zigbee-herdsman with settings: '{"network":{"panID":"HIDDEN","extendedPanID":["HIDDEN"],"channelList":[11],"networkKey":"HIDDEN"},"databasePath":"/share/zigbee2mqtt/database.db","databaseBackupPath":"/share/zigbee2mqtt/database.db.backup","backupPath":"/share/zigbee2mqtt/coordinator_backup.json","serialPort":{"baudRate":115200,"rtscts":true,"path":"/dev/ttyACM0"}}'
	zigbee2mqtt:error 2019-12-15T11:51:50: Error while starting zigbee-herdsman
	zigbee2mqtt:error 2019-12-15T11:51:50: Failed to start zigbee
	zigbee2mqtt:error 2019-12-15T11:51:50: Exiting...
	zigbee2mqtt:error 2019-12-15T11:51:50: Error: SRSP - SYS - version after 6000ms
		at Timeout.object.timer.setTimeout [as _onTimeout] (/zigbee2mqtt-1.7.1/node_modules/zigbee-herdsman/dist/utils/waitress.js:44:24)
		at ontimeout (timers.js:436:11)
		at tryOnTimeout (timers.js:300:5)
		at listOnTimeout (timers.js:263:5)
		at Timer.processTimers (timers.js:223:10)
	npm
	 ERR! code ELIFECYCLE
	npm ERR! errno 1cl
	npm
	 ERR! zigbee2mqtt@1.7.1 start: `node index.js`
	npm ERR! Exit status 1
	npm
	 ERR! 
	npm ERR! Failed at the zigbee2mqtt@1.7.1 start script.
	npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
	npm ERR! A complete log of this run can be found in:
	npm ERR!     /root/.npm/_logs/2019-12-15T11_51_50_939Z-debug.log

I then ran the test again to see if the stick was still avaliable to the linux VM and it was not:

	root@home_assistant_server:~# ls -l /dev/serial/by-id                           
	ls: cannot access '/dev/serial/by-id': No such file or directory
	root@home_assistant_server:~# test -w /dev/ttyACM0 && echo success || echo failure
	failure

I then ran the tests on Proxmox again and it was still avaliable:

root@pve:~# ls -l /dev/serial/by-id
	total 0
	lrwxrwxrwx 1 root root 13 Dec 15 11:36 usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0018E1F5E8-if00 -> ../../ttyACM0
	root@pve:~#  test -w /dev/ttyACM0 && echo success || echo failure
	success

I checked the Proxmox syslog and I found that the USB stick is constantly disconnecting and reconnecting while the addon is active but if I stop the addon then it stays attached:

Dec 15 11:50:00 pve systemd[1]: Starting Proxmox VE replication runner...
	Dec 15 11:50:01 pve systemd[1]: pvesr.service: Succeeded.
	Dec 15 11:50:01 pve systemd[1]: Started Proxmox VE replication runner.
	Dec 15 11:50:36 pve kernel: usb 5-1.2: USB disconnect, device number 45
	Dec 15 11:50:36 pve kernel: usb 5-1.2: new full-speed USB device number 46 using xhci_hcd
	Dec 15 11:50:36 pve kernel: usb 5-1.2: New USB device found, idVendor=0451, idProduct=16a8, bcdDevice= 0.09
	Dec 15 11:50:36 pve kernel: usb 5-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
	Dec 15 11:50:36 pve kernel: usb 5-1.2: Product: TI CC2531 USB CDC
	Dec 15 11:50:36 pve kernel: usb 5-1.2: Manufacturer: Texas Instruments
	Dec 15 11:50:36 pve kernel: usb 5-1.2: SerialNumber: __0X00124B0018E1F5E8
	Dec 15 11:50:36 pve kernel: cdc_acm 5-1.2:1.0: ttyACM0: USB ACM device
	Dec 15 11:50:38 pve kernel: usb 5-1.2: reset full-speed USB device number 46 using xhci_hcd
	Dec 15 11:51:00 pve systemd[1]: Starting Proxmox VE replication runner...
	Dec 15 11:51:01 pve systemd[1]: pvesr.service: Succeeded.
	Dec 15 11:51:01 pve systemd[1]: Started Proxmox VE replication runner.
	Dec 15 11:51:37 pve kernel: usb 5-1.2: USB disconnect, device number 46
	Dec 15 11:51:37 pve kernel: usb 5-1.2: new full-speed USB device number 47 using xhci_hcd
	Dec 15 11:51:38 pve kernel: usb 5-1.2: New USB device found, idVendor=0451, idProduct=16a8, bcdDevice= 0.09
	Dec 15 11:51:38 pve kernel: usb 5-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
	Dec 15 11:51:38 pve kernel: usb 5-1.2: Product: TI CC2531 USB CDC
	Dec 15 11:51:38 pve kernel: usb 5-1.2: Manufacturer: Texas Instruments
	Dec 15 11:51:38 pve kernel: usb 5-1.2: SerialNumber: __0X00124B0018E1F5E8
	Dec 15 11:51:38 pve kernel: cdc_acm 5-1.2:1.0: ttyACM0: USB ACM device
	Dec 15 11:51:41 pve kernel: usb 5-1.2: reset full-speed USB device number 47 using xhci_hcd
	Dec 15 11:51:45 pve kernel: usb 5-1.2: USB disconnect, device number 47
	Dec 15 11:51:45 pve kernel: usb 5-1.2: new full-speed USB device number 48 using xhci_hcd
	Dec 15 11:51:45 pve kernel: usb 5-1.2: New USB device found, idVendor=0451, idProduct=16a8, bcdDevice= 0.09
	Dec 15 11:51:45 pve kernel: usb 5-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
	Dec 15 11:51:45 pve kernel: usb 5-1.2: Product: TI CC2531 USB CDC
	Dec 15 11:51:45 pve kernel: usb 5-1.2: Manufacturer: Texas Instruments
	Dec 15 11:51:45 pve kernel: usb 5-1.2: SerialNumber: __0X00124B0018E1F5E8
	Dec 15 11:51:45 pve kernel: cdc_acm 5-1.2:1.0: ttyACM0: USB ACM device
	Dec 15 11:51:50 pve kernel: usb 5-1.2: reset full-speed USB device number 48 using xhci_hcd
	Dec 15 11:51:54 pve kernel: usb 5-1.2: USB disconnect, device number 48
	Dec 15 11:51:54 pve kernel: usb 5-1.2: new full-speed USB device number 49 using xhci_hcd
	Dec 15 11:51:54 pve kernel: usb 5-1.2: New USB device found, idVendor=0451, idProduct=16a8, bcdDevice= 0.09
	Dec 15 11:51:54 pve kernel: usb 5-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
	Dec 15 11:51:54 pve kernel: usb 5-1.2: Product: TI CC2531 USB CDC
	Dec 15 11:51:54 pve kernel: usb 5-1.2: Manufacturer: Texas Instruments
	Dec 15 11:51:54 pve kernel: usb 5-1.2: SerialNumber: __0X00124B0018E1F5E8
	Dec 15 11:51:54 pve kernel: cdc_acm 5-1.2:1.0: ttyACM0: USB ACM device
	Dec 15 11:51:56 pve kernel: usb 5-1.2: reset full-speed USB device number 49 using xhci_hcd
	Dec 15 11:52:00 pve systemd[1]: Starting Proxmox VE replication runner...
	Dec 15 11:52:01 pve systemd[1]: pvesr.service: Succeeded.
	Dec 15 11:52:01 pve systemd[1]: Started Proxmox VE replication runner.
	Dec 15 11:52:03 pve kernel: usb 5-1.2: USB disconnect, device number 49

I followed all the guides I could find and made sure modemmanager was not installed in the VM or Proxmox:

root@home_assistant_server:~# systemctl |grep Modem
	root@home_assistant_server:~#
	root@pve:~# systemctl |grep Modem
	root@pve:~#

I have run out of ideas of where to look next, has anyone got any ideas?

Many thanks

Posts: 1

Participants: 1

Read full topic

@war1000 wrote:

I am really hoping someone can help me with this as this seems to be pretty common. I am trying to setup a notification with presence. I have setup the presence through my asus router.

I have read several threads and still can’t seem to figure this out…can you guys please help me? Thanks in advance

- id: '1576450548715'
  alias: Presence Notification
  description: ''
  trigger:
  - entity_id: device_tracker.mo_huawei_phone
    platform: state
  - entity_id: device_tracker.tarin_huawei_phone
    platform: state
  condition: []
  action:
  - data:
     message: |
      {% if trigger.entity_id == "device_tracker.mo_huawei_phone" %}
       {% set person = "Mo" %}  
      {% elif trigger.entity_id == "device_tracker.tarin_huawei_phone" %}
       {% set person = "Tarin" %}                                     
      {% endif %} 
      {% if trigger.to_state.state == 'home' %}
       {{ person }} is home
      {% else %} 
       {{ person }} has left home
      {% endif %}
     title: 'Home info {{ states.sensor.time.state }}'
    service: notify.notify

image872×866 32.8 KB

image868×761 43.1 KB

Posts: 2

Participants: 2

Read full topic