@Yuran wrote:

Has anyone tested to connect HA to a 4G router and then connect to it remote? Work ok?

Posts: 3

Participants: 2

Read full topic

@tercelkisor wrote:

Hi, I’m still in the research phase of all of this and I just want to make sure what I have in my mind is possible. I am looking at repurposing an old Dell tower into an unraid server that has dockers for HA, Plex, Associated media stuff, and Shinobi. I’m sure just messing with it will answer some of my specific questions, so I’ll leave those out until I get my hands in the setup.

I’m currently leaning towards wyze cams with the rtsp enabled firmware for 5-6 security cameras with motion detection recording with shinobi. I also want to be able to cast the streams to displays in my home and remotely with over VPN server (another docker container?) Are there any known issues with doing this or minor changes I can make to this plan that would save me a bunch of headache?

Anything else I should consider?

Posts: 1

Participants: 1

Read full topic

@dror-israel wrote:

hello,
My z-wave network respond very slow, so I installed z-wave graph to see the connections.
This is what I saw on the graph:

image1399×454 47.6 KB

Is the slow z-wave network is because the nodes are not connected?

Posts: 1

Participants: 1

Read full topic

@Guijar wrote:

Hi all,

I don’t know if here is the correct place to ask about this issue, but I’ve been working on this for a couple of days and still haven’t found a solution.

I can run a rermote shutdown between my Windows computers, but when I try to run the commands from the Home Assistant Linux server to shutdown my windows 10 pc I got allways the same error:

This is the command I run:
net rpc shutdown -I “Windows_IP” -U “User”%“Pass”

And the output error:

Could not connect to server 192.168.1.10
Connection failed: NT_STATUS_CONNECTION_RESET
Could not connect to server 192.168.1.10
Connection failed: NT_STATUS_CONNECTION_RESET

Does anyone know how to solve this??

Thanks!!

Posts: 1

Participants: 1

Read full topic

@hmoffatt wrote:

Does anyone have a custom gauge or other ideas for a gauge that can go negative? Ideally, zero would be in the center and the coloured bar would go left from the center for negative and right from the center for positive.

I’d like to display my current net energy usage, which may be negative due to my solar power system.

The standard gauge card allows the minimum to be set below zero, but it doesn’t seem to work, and the bar always starts from the far left anyway.

Posts: 1

Participants: 1

Read full topic

@hmoffatt wrote:

I have some input_* entities in an entities card. Can I make this non-modifiable somehow?

Posts: 1

Participants: 1

Read full topic

@oneteam wrote:

I hope you can help me with my problem.
For 2 days now, a sensor hasn’t given any values from Grafana.
I found an influx error in the logfile.
Unfortunately the error message doesn’t tell me what possibilities I have to fix the error.

• Is this a crash of the database for this entry?
• Is there a possibility to repair the database?
• Or is there another way to fix the error?
  Thanks for your help.

2020-06-09 23:31:32 ERROR (InfluxDB) [homeassistant.components.influxdb] Write error: 400: {“error”:“partial write: unable to parse ‘kWh,domain=sensor,entity_id=energy_spent_poolpumpe friendly_name_str=“energy_spent_poolpumpe”,icon_str=“mdi:chart-histogram”,source_str=“sensor_verbrauch.poolpumpe”,value=nan 1591738228934721024’: invalid number dropped=0”}

Home Assistant: 0.110.6
InfluxDB: 3.7.1

Posts: 1

Participants: 1

Read full topic

@Mariusthvdb wrote:

having fixed almost all user errors, my HA log is cleaning up nicely
still, and even with the improved logging of templates I see this in my log regularly:

Schermafbeelding 2020-06-10 om 11.58.091090×426 36.8 KB

Ive already set logger to debug on the helpers.condition, but the error stays as useless as it is.

In my logbook, nothing happens at that time:

Schermafbeelding 2020-06-10 om 11.55.101154×1364 188 KB

so I am rather clueless what to do/where to go and find the issue…other than it being a template condition, in any of the automations and scripts I have running.

Anyone with the golden suggestion?
thanks for having a look.

Posts: 1

Participants: 1

Read full topic

@sd_dracula wrote:

I am thinking of building one of these https://www.pi-shop.ch/modmypi-pi-pir-motion-sensor-camera-box-zero and getting the camera feed and the PIR sensor (ideally a LUX sensor too) as entities in HA.
Has anyone done something like that? Is it possible?
I am assuming the camera can be added via generic camera integration, not sure on the sensor.

Posts: 1

Participants: 1

Read full topic

@omega_elite wrote:

Hi

I am new to HA so please forgive me if this is a stupid question………what I would like to do is send a TCP packet to HA and that trigger an action…is this possible ??? how do I do it ???, I basically have a device that is a touch panel that has button that when pressed send data to an ip address and port number i.e. when I press a button on the TS called “on” it sends “POW\r” the ip, port and data are configurable

thank you your help

Posts: 2

Participants: 2

Read full topic

@home_builder wrote:

Hi all

I have troubles getting GPIO extender to work over I2C in Home Assistant. I’m using IO PI Plus that is based on mcp23017, therefore I’m using the configuration below.

switch:
- platform: mcp23017
i2c_address: 0x20
pins:
1: Light1
3: Light3
5: Light5
7: Light7
9: Light9
11: Light11
13: Light13
15: Light15

Environment used:

• RPI 3 B+
• IO PI Plus extender
• HomeAssitant 0.110.70 - installed into venv
• I2C configured

Scenario:

• After a fresh start i can found I2C addresses (displayed instantly <1s)

(homeassistant) homeassistant@raspberrypi:/srv/homeassistant $ i2cdetect -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: – -- – -- – -- – -- – -- – -- –
10: – -- – -- – -- – -- – -- – -- – -- – --
20: 20 21 – -- – -- – -- – -- – -- – -- – --
30: – -- – -- – -- – -- – -- – -- – -- – --
40: – -- – -- – -- – -- – -- – -- – -- – --
50: – -- – -- – -- – -- – -- – -- – -- – --
60: – -- – -- – -- – -- – -

• I can also successfully run my test python script controlling IO PI Plus with a relay board.

• after starting ./hass from env it starts. Regular gpios works fine, however I2c pins are not detected and I get an error in the log.

Log Details (ERROR)

Logger: homeassistant.components.switch
Source: components/mcp23017/switch.py:42
Integration: Switch ([documentation](https://www.home-assistant.io/integrations/switch), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+switch%22))
First occurred: 10:32:47 AM (1 occurrences)
Last logged: 10:32:47 AM

Error while setting up mcp23017 platform for switch

Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/adafruit_bus_device/i2c_device.py", line 184, in __probe_for_device self.i2c.writeto(self.device_address, b"") File "/usr/local/lib/python3.7/site-packages/busio.py", line 86, in writeto return self._i2c.writeto(address, buffer, stop=stop) File "/usr/local/lib/python3.7/site-packages/adafruit_blinka/microcontroller/generic_linux/i2c.py", line 38, in writeto self._i2c_bus.write_bytes(address, buffer[start:end]) File "/usr/local/lib/python3.7/site-packages/Adafruit_PureIO/smbus.py", line 308, in write_bytes self._device.write(buf) TimeoutError: [Errno 110] Operation timed out During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/adafruit_bus_device/i2c_device.py", line 190, in __probe_for_device self.i2c.readfrom_into(self.device_address, result) File "/usr/local/lib/python3.7/site-packages/busio.py", line 76, in readfrom_into return self._i2c.readfrom_into(address, buffer, stop=stop) File "/usr/local/lib/python3.7/site-packages/adafruit_blinka/microcontroller/generic_linux/i2c.py", line 44, in readfrom_into readin = self._i2c_bus.read_bytes(address, end-start) File "/usr/local/lib/python3.7/site-packages/Adafruit_PureIO/smbus.py", line 179, in read_bytes return self._device.read(number) TimeoutError: [Errno 110] Operation timed out During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 178, in _async_setup_platform await asyncio.wait_for(asyncio.shield(task), SLOW_SETUP_MAX_WAIT) File "/usr/local/lib/python3.7/asyncio/tasks.py", line 442, in wait_for return fut.result() File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run result = self.fn(*self.args, **self.kwargs) File "/usr/src/homeassistant/homeassistant/components/mcp23017/switch.py", line 42, in setup_platform mcp = MCP23017(i2c, address=i2c_address) File "/usr/local/lib/python3.7/site-packages/adafruit_mcp230xx/mcp23017.py", line 64, in __init__ super().__init__(i2c, address) File "/usr/local/lib/python3.7/site-packages/adafruit_mcp230xx/mcp230xx.py", line 48, in __init__ self._device = i2c_device.I2CDevice(i2c, address) File "/usr/local/lib/python3.7/site-packages/adafruit_bus_device/i2c_device.py", line 69, in __init__ self.__probe_for_device() File "/usr/local/lib/python3.7/site-packages/adafruit_bus_device/i2c_device.py", line 192, in __probe_for_device raise ValueError("No I2C device at address: %x" % self.device_address) ValueError: No I2C device at address: 20

- After that momentI2C interface also gets stuck even when when homeassistant is shutdown (now discovery takes >10s)

homeassistant@raspberrypi:/srv/homeassistant $ i2cdetect -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: – -- – -- – -- – -- – -- – -- –
10: – -- – -- – -- – -- – -- – -- – -- – --
20: – -- – -- – -- – -- – -- – -- – -- – --
30: – -- – -- – -- – -- – -- – -- – -- – --
40: – -- – -- – -- – -- – -- – -- – -- – --
50: – -- – -- – -- – -- – -- – -- – -- – --
60: – -- – -- – -- – -- – -- – -- – -- – --
70: – -- – -- – -- – --

• Also a tutorial that worked before, stops working…

(homeassistant) homeassistant@raspberrypi:/srv/homeassistant $ python3 /home/pi/src/tutorial/tutorial2.py

Traceback (most recent call last):
File "/home/pi/src/tutorial/tutorial2.py", line 4, in <module> bus = IOPi(0x20)
File "/srv/homeassistant/lib/python3.7/site-packages/IOPi/IOPi.py", line 110, in __init__ self.__bus.write_byte_data(self.__ioaddress, self.IOCON, self.__conf)
File "/srv/homeassistant/lib/python3.7/site-packages/smbus2/smbus2.py", line 434, in write_byte_data ioctl(self.fd, I2C_SMBUS, msg) OSError: [Errno 121] Remote I/O error

• Interface recover’s only after reboot.

Help very appreciated on getting hass working with the extender.

Posts: 1

Participants: 1

Read full topic

@pschneider87 wrote:

Hi there,

I’m trying to use the Service ‘homematicip_cloud.set_active_climate_profile’ for Homematic IP Cloud.
It’s working fine to change profiles, however, when the Climate Group is in Manual Mode (because someone changed the temperature on the thermostate) it’s not working.

Anybody got an idea how to override manual mode with a climate profile?

Cheers,
Philipp

Posts: 1

Participants: 1

Read full topic

@fitim wrote:

Hi,
I have a Xiaomi lightsensor which isn’t updating its state anymore. Everything worked perfect until now. I tried to delete the sensor, and add it again, but its always having the same state (1495 Lux).

Any idea what I can do? For me it seems, like its “stuck”. The led on the sensor is working, that’s why I don’t think that it is broke. Also if I delete the sensor from the mesh via VNC, it is just coming back without doing anything. How can I delete the sensor totally from the database? I think deconz has a database too?

I’m talking about this sensor:

Posts: 1

Participants: 1

Read full topic

@Murder3D wrote:

Hi,

I’m new to HA, so I’m sorry if this is something that has been asked previously.

I made a 3D floor plan of my house inside a Picture Elements Card, and each room consist in two layers with lights on and off. In every room I placed a ‘mdi:lightbulb-on-outline’ icon so I can click on it and turn the corresponding light on or off.

The room turns on when the light is on and goes back to dark when the light is off.

The ‘mdi:lightbulb-on-outline’ icon is grey when the light is off and turns yellow when the light is on.

I am trying to replicate the same behavior for my living room, where I have 3 different switches that toggle 3 different lights. I want to be able to toggle all the lights in my living room with just one switch, so I can have my ‘mdi:lightbulb-on-outline’ icon changing color from grey to yellow, as well as my living room image layers switching between dark and illuminated.

I created the following script:

device_id: 38a6462cbafb499b8c37c85a6bc5b4d0
domain: switch
entity_id: switch.livingroomlights1
type: toggle

device_id: 38a6462cbafb499b8c37c85a6bc5b4d0
domain: switch
entity_id: switch.livingroomlights2
type: toggle

device_id: 38a6462cbafb499b8c37c85a6bc5b4d0
domain: switch
entity_id: switch.livingroomlights3
type: toggle

Then I added that script inside my Picture Elements Card on my lovelace UI. I changed the script icon to ‘mdi:lightbulb-on-outline’ and the lights turn on and off correctly, but my '‘mdi:lightbulb-on-outline’ remain grey.

I would like to know if there is a way to change the color of the living room icon according to the on / off state, just like in the other rooms of the house.

Any help is gretly appreciated!

Marco

Posts: 2

Participants: 2

Read full topic

@WimFC wrote:

I want to control 2 hue lights with a switch connected to a shelly 1. I use the binary sensor on/off from the shelly 1 as the trigger (the switch input from the shelly is detached fro the output relay). I want the lights to have a different brightness overday then overnight, herefore I created a day and night scene.
So I made 3 different automations with the same triggers but different conditions:

- id: '1591709584039'
  alias: schakelaar eetkamer dag aan
  description: ''
  trigger:
  - device_id: 7134c5268f7748818bb5667dcf1c61af
    domain: binary_sensor
    entity_id: binary_sensor.shelly_shsw_1_f394bc_switch
    platform: device
    type: turned_on
  - device_id: 7134c5268f7748818bb5667dcf1c61af
    domain: binary_sensor
    entity_id: binary_sensor.shelly_shsw_1_f394bc_switch
    platform: device
    type: turned_off
  condition:
  - condition: device
    device_id: 69a64803b3b048e2a17fc657771386fa
    domain: light
    entity_id: light.eetkamer_lamp_1
    type: is_off
  - condition: and
    conditions:
    - condition: device
      device_id: 5458656273f043d4baced937c2505b4c
      domain: light
      entity_id: light.eetkamer_lamp_2
      type: is_off
  - after: sunrise
    before: sunset
    condition: sun
  action:
  - scene: scene.eetkamer_dag
- id: '1591726413131'
  alias: schakelaar eetkamer uit
  description: ''
  trigger:
  - device_id: 7134c5268f7748818bb5667dcf1c61af
    domain: binary_sensor
    entity_id: binary_sensor.shelly_shsw_1_f394bc_switch
    platform: device
    type: turned_on
  - device_id: 7134c5268f7748818bb5667dcf1c61af
    domain: binary_sensor
    entity_id: binary_sensor.shelly_shsw_1_f394bc_switch
    platform: device
    type: turned_off
  condition:
  - condition: or
    conditions:
    - condition: device
      device_id: 69a64803b3b048e2a17fc657771386fa
      domain: light
      entity_id: light.eetkamer_lamp_1
      type: is_on
  - condition: or
    conditions:
    - condition: device
      device_id: 5458656273f043d4baced937c2505b4c
      domain: light
      entity_id: light.eetkamer_lamp_2
      type: is_on
  action:
  - device_id: 69a64803b3b048e2a17fc657771386fa
    domain: light
    entity_id: light.eetkamer_lamp_1
    type: turn_off
  - device_id: 5458656273f043d4baced937c2505b4c
    domain: light
    entity_id: light.eetkamer_lamp_2
    type: turn_off
- id: '1591726962429'
  alias: schakelaar eetkamer nacht
  description: ''
  trigger:
  - device_id: 7134c5268f7748818bb5667dcf1c61af
    domain: binary_sensor
    entity_id: binary_sensor.shelly_shsw_1_f394bc_switch
    platform: device
    type: turned_on
  - device_id: 7134c5268f7748818bb5667dcf1c61af
    domain: binary_sensor
    entity_id: binary_sensor.shelly_shsw_1_f394bc_switch
    platform: device
    type: turned_off
  condition:
  - condition: device
    device_id: 69a64803b3b048e2a17fc657771386fa
    domain: light
    entity_id: light.eetkamer_lamp_1
    type: is_off
  - condition: and
    conditions:
    - condition: device
      device_id: 5458656273f043d4baced937c2505b4c
      domain: light
      entity_id: light.eetkamer_lamp_2
      type: is_off
  - after: sunset
    before: sunrise
    condition: sun
  action:
  - scene: scene.eetkamer_nacht

Overday the automation works as expected. After sunset it does nothing. And the automation for switching off the lights only works when both lamps are on.
When I trigger the automations from the GUI they all work as expected.
What is going wrong?
Or can I only do this with scripts? (I am a homeassistant noob so I have no experience at all with scripts)

Posts: 1

Participants: 1

Read full topic

@Mariusthvdb wrote:

having not used 2 groups in my Lovelace frontend before (only used them for backend logic) Ive now added them to a card, and am surprised to see them having a toggle, and not showing the state. Is this to be expected?

Schermafbeelding 2020-06-10 om 15.07.27764×980 63.4 KB

lovelace:

  - type: entities
    title: At home
    entities:
      - entity: binary_sensor.family_home
        secondary_info: last-changed
      - entity: sensor.family_home
        secondary_info: last-changed
      - type: divider
      - entity: group.family
        secondary_info: last-changed
      - entity: group.family_home
        secondary_info: last-changed
      - type: divider
      - entity: binary_sensor.daughters_home
        secondary_info: last-changed
      - entity: sensor.daughters_home
        secondary_info: last-changed
      - type: divider
      - entity: group.daughters
        secondary_info: last-changed
      - entity: group.daughters_home
        secondary_info: last-changed

the 2 groups are defined as:

  family_home:
    name: Familie Home
    icon: mdi:home-heart
    entities:
      - group.daughter_1
      - group.daughter_2
      - group.daughter_3
      - group.daughter_4
      - group.she
      - group.me

and

  daughters_home:
    name: Daughters Home
    icon: mdi:human-child
    entities:
      - group.daughter_1
      - group.daughter_2
      - group.daughter_3
      - group.daughter_4

(… edited the actual names )

of course these groups exist of yet multiple entities again)

why the toggle, because when toggling an error is displayed it cant find a service device_tracker/turn_on, which is correct of course. and, though the toggle does change position, the entity doesnt change state.

so, I am somewhat confused…

Posts: 3

Participants: 2

Read full topic

@Mariusthvdb wrote:

even though this was solved way back: https://github.com/home-assistant/core/issues/28894

updating today to 110.7 makes the

5: Requested entity was not found.

google cloud error re-appear. Anyone else seeing this

Schermafbeelding 2020-06-10 om 15.28.03842×454 51.5 KB

thanks for having a look.

Posts: 1

Participants: 1

Read full topic

@monsterstepdad wrote:

HI All, I’m trying to follow a tutorial on hackster for a doorbell using Raspberry pi 3B. however i get this error

2020-06-10 15:56:48 ERROR (SyncWorker_0) [homeassistant.util.yaml.loader] mapping values are not allowed here
in “/home/homeassistant/.homeassistant/configuration.yaml”, line 33, column 13
2020-06-10 15:56:48 ERROR (MainThread) [homeassistant.bootstrap] Failed to parse configuration.yaml: mapping values are not allowed here
in “/home/homeassistant/.homeassistant/configuration.yaml”, line 33, column 13. Activating safe mode
2020-06-10 15:58:37 WARNING (MainThread) [homeassistant.components.webhook] Received message for unregistered webhook 8d0f2666a07ebc534455abf44b8b1c609a246674c99f0eb7d80a68f88ae29085 from 192.168.1.103

The only thing it refers too is the trigger function which i can’t seem to figure out what is wrong as it looks fine from reading the documentation on home assistant triggers.

Here is my config.yaml file

# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:

# Text to speech
tts:
  - platform: google_translate

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
mqtt:
  broker: localhost
camera:
 - platform: mqtt
   topic: dev/camera
dev_publish_on_script: 
 sequence: 
   - service: mqtt.publish 
     data: {"topic":"dev/test", "payload":"ON"} 
script.dev_publish_on_script: 
 friendly_name: 'Capture doorcam photo' 
 icon: mdi:camera 
# Telegram Bot send messages
notify:
  - name: Telegram
    platform: telegram
    api_key: 2354345@4f34f3245g46465yh4th44
    chat_id: 1113241523
automation:
  - alias: Doorbell_pressed_automation 
     trigger: 
      platform: mqtt 
      topic: dev/test
      payload: 'Capture!' 
   action: 
    -  service: automation.turn_off 
       entity_id: automation.doorbell_pressed_automation 
    -  service: script.turn_on 
       entity_id: script.doorbell_pressed_script 
    -  delay: "00:00:5" 
    -  service: automation.turn_on 
       entity_id: automation.doorbell_pressed_automation 

Any help would be awesome thank you in advance.

Posts: 1

Participants: 1

Read full topic

@gr4z wrote:

I want to have a sensor for displaying how long my coffee machine has been on for. I have used the following code with the history_stats field:

  - platform: history_stats
    name: Coffee On
    entity_id: switch.coffee
    state: 'on'
    type: time
    start: '{{ now().replace(hour=0, minute=0, second=0) }}'
    end: '{{ now() }}'  

But this just totals up the amount its been on for the entire day. My coffee machines takes a minimum of 20 minutes to warm up, so just want to query how long its been on for at any time. If it’s currently off then the sensor should say ‘off’.

How would I do this?
Thanks

Posts: 1

Participants: 1

Read full topic

@Madivad wrote:

I’m running hass.io in a docker on a synology box (installation instructions here: Hass.io on Synology DSM (native package) )

I have installed the mqtt add-on and after much stuffing around I am finally able to see some items pop up but having a hard time managing them.

For one I’m getting errors that entity_id’s aren’t unique, but I can’t finding where those ids exist anywhere else. I eventually logged into the sonoff device and changed friendly names and mqtt settings thinking that should help, but that just made it worse, now there’s two devices, one with an “_2” and one without (which is now old and removed). Through a few searches I was able to “hide” the old entry, but the new one still claims the entity_id isn’t unique.

The second problem I’m having with this unit is that it is identifying as a “switch” and coming up as “switch.laundryth” (laundry because that’s where it is, and th because it is a sonoff TH model)

I have the mqtt addon installed, but I can’t see any interaction anywhere in the logs or history between HA and MQTT and the sonoff.

I’ve been trying to get the temperature and humidity readings from it and I can’t determine what to enter where to even poll the device and see what the readings are. In the mqtt debug tools all I can see is listed under states and that is the fact it is a status of being on or off. There’s nothing there about the devices other values.

I’ve been clutching at this for a couple of days now and am pulling my hair out. It appears nothing I enter into the publish a packet field can find its way to the sonoff, I realise I’m just not entering the right text/mqtt query, so any help would be appreciated.

Oh and obviously the mqtt signals are working as I can turn the device on and off without issues (it is slow, it it does do it).

1. what packet to send from the publish a packet in the mqtt debug tools will allow me to see the other data?

MQTT settings I have are:

Client : dves_%06X <— what is this even used for?
Topic : laundryth
Full topic : %prefix%/%topic%

In “publish” I’ve tried all variants of:

stat/laundryth/
stat/laundryth/status10
cmnd/laundryth/status10

I’ve tried the status10 on the payload line to no avail.

2. how do I get that data into HA?

Bonus points:
3) how can I make sure laundryth has a unique entity_id? I mean, I’m not seeing a duplicate anywhere.

Posts: 1

Participants: 1

Read full topic