I was setting up this bayesian sleep sensor based on what I had read in a couple forums and the sensor will trigger to on. But it is not turning off. Any ideas what I might be missing?

binary_sensor:
  - platform: bayesian
    prior: 0.5
    name: Sleeping
    probability_threshold: 0.85
    observations:
      - entity_id: 'device_tracker.pixel_5'
        prob_given_true: 0.99
        prob_given_false: 0.01
        platform: state
        to_state: 'Home'
      - entity_id: 'device_tracker.iphone'
        prob_given_true: 0.99
        prob_given_false: 0.01
        platform: state
        to_state: 'Home'
      - entity_id: 'sensor.sun'
        prob_given_true: 0.9
        prob_given_false: 0.2
        platform: state
        to_state: below_horizon
      - entity_id: light.master_bedroom_lights
        prob_given_true: 0.99
        prob_given_false: 0.01
        platform: state
        to_state: 'off'
      - entity_id: light.master_bathroom_lights
        prob_given_true: 0.99
        prob_given_false: 0.01
        platform: state
        to_state: 'off'
      - entity_id: media_player.master_bedroom_tv
        prob_given_true: 0.99
        prob_given_false: 0.4
        platform: state
        to_state: 'off'
      - entity_id: media_player.master_bedroom_speaker
        prob_given_true: 0.99
        prob_given_false: 0.4
        platform: state
        to_state: playing
      - entity_id: sensor.iphone_battery_state
        prob_given_true: 0.99
        prob_given_false: 0.4
        platform: state
        to_state: Charging
      - entity_id: binary_sensor.pixel_5_is_charging
        prob_given_true: 0.99
        prob_given_false: 0.4
        platform: state
        to_state: 'on'

1 post - 1 participant

Read full topic

I have this integration already installed and working for several outdoor and indoor outlets. The integration reports access is local (no cloud) but appears to be cloud based. Is that a false report or just misleading since the older devices can talk locally (before ports were reportedly blocked by later firmware updates)? At $6 per unit (indoor devices) these are hard to pass up even if they are dependent on cloud.

1 post - 1 participant

Read full topic

Hil folks,

when I try to integrate a new Shelly device, the integration module says, that it’s allready there.
I find the device in the device list, but all entities are deactivated an I can’t activate them.
I think, that I had this Shelly-device allready installed and replaced with another one.
Now there is a name-collision (I think)

Is it possible to delete integrations manually?
I’m confused

1 post - 1 participant

Read full topic

Hello all,

I have RFXCOM RFXtrx installed. Meanwhile, about 800 sensor.rm174rf_smoke_detector have been added while I have no smoke detectors at all. How can I remove them and make sure they don’t keep adding?

Thankx
Peter

1 post - 1 participant

Read full topic

Hey everybody,
I have a app that plays and casts Portuguese tv to any Chromecast device.
I want to use home assistant to cast the programs, without having to get my phone and open they app. I was thinking if is possible to get the Cast command sent from the app to the Cast device, and replicate that command from home assistant.
Is this possible?

1 post - 1 participant

Read full topic

Hi,

I have these two connected to my zigbee2mqtt controller:
https://www.zigbee2mqtt.io/devices/MS-105Z.html
https://www.zigbee2mqtt.io/devices/4512719.html

Since I’m a noob, what should my automation look like?

The dimmer switch’s payload on button hold is: brightness_move_up_1
The MOES dimmer documentation says you can use:

"brightness_move": 40

To dim the brightness 40 for every second. But I have no clue how to use this

1 post - 1 participant

Read full topic

In my web browser I’m forced to login every time to Homeassistant, however on my phone I am not. I did not used to have to login every time on my browser.

I removed a few of the tokens a few days back and I believe that is when it started, but I’ve since sen tokens remade, but still I have to loign

1 post - 1 participant

Read full topic

Hi all,
I think i need some help with this one.

So, i would like to turn on the tv when there i walk in the living room. I can achieve by this by using a motion sensor, but the problem is, next time someone walks in the living room, it switches off due to the IR signals being the same.

If the signals are not the same, i could use Viera (panasonic viera is the tv) turn on, but it would send a IR signal every second or so (sounds like a bad idea). If i would set it to every 10 minutes, then obviously the automation would only run every 10 minutes and it would take a long time for it to turn on. So that is not an option either.

I tried doing: Check for motion (1sec) but only if no motion in the previous 10 minutes was detection as a condition. It sounded like it should work, and the automation was accepted, but it never triggered. And in hindsight, it makes sense. Obviously the first time it senses motion, then the condition is invalidated.

Sigh. So now i’m thinking how else could i construct this. I want the tv to turn on but only if no one is currently in the room.

Many thanks for your help.

1 post - 1 participant

Read full topic

I’ve been able to successfully connect Tradfri and Osram Zigbee lights to Home Assistant with a deCONZ ConBee, but I’m struggling with some Linkind bulbs (model ZL100040014).

The lights appear to pair correctly:

[0x0000:zdo] ZDO request ZDOCmd.Mgmt_Permit_Joining_req: [60, <Bool.false: 0>]
[0x0000](ConBee): started initialization
[0x0000:ZDO](ConBee): 'async_initialize' stage succeeded
[0x0000](ConBee): power source: Mains
[0x0000](ConBee): completed initialization
Device 0x3257 (80:4b:50:ff:fe:3f:3b:2e) joined the network
Device 80:4b:50:ff:fe:3f:3b:2e changed id (0x3257 => 0x3257)
[0x3257] Skipping initialization, device is fully initialized
Device is initialized <Device model='ZBT-CCTLight-C4700107' manuf='lk' nwk=0x3257 ieee=80:4b:50:ff:fe:3f:3b:2e is_initialized=True>
Checking quirks for lk ZBT-CCTLight-C4700107 (80:4b:50:ff:fe:3f:3b:2e)
Considering <class 'zhaquirks.xbee.xbee_io.XBeeSensor'>
Fail because endpoint list mismatch: {232, 230} {1, 242}
Considering <class 'zhaquirks.xbee.xbee3_io.XBee3Sensor'>
Fail because endpoint list mismatch: {232, 230} {1, 242}
Considering <class 'zhaquirks.smartthings.tag_v4.SmartThingsTagV4'>
Fail because endpoint list mismatch: {1} {1, 242}
Considering <class 'zhaquirks.smartthings.multi.SmartthingsMultiPurposeSensor'>
Fail because endpoint list mismatch: {1} {1, 242}
Considering <class 'zhaquirks.netvox.z308e3ed.Z308E3ED'>
Fail because endpoint list mismatch: {1} {1, 242}
Considering <class 'zhaquirks.gledopto.soposhgu10.SoposhGU10'>
Fail because endpoint list mismatch: {11, 13} {1, 242}
Considering <class 'bellows.zigbee.application.EZSPCoordinator'>
Fail because endpoint list mismatch: {1} {1, 242}
[0x3257:zdo] ZDO request ZDOCmd.Device_annce: [0x3257, 80:4b:50:ff:fe:3f:3b:2e, 142]
device - 12887:80:4b:50:ff:fe:3f:3b:2e entering async_device_initialized - is_new_join: False
device - 12887:80:4b:50:ff:fe:3f:3b:2e has been reset and re-added or its nwk address changed
skipping discovery for previously discovered device - 12887:80:4b:50:ff:fe:3f:3b:2e
[12887](ZBT-CCTLight-C4700107): started configuration
[12887:ZDO](ZBT-CCTLight-C4700107): 'async_configure' stage succeeded
[12887](ZBT-CCTLight-C4700107): started initialization
[12887:ZDO](ZBT-CCTLight-C4700107): 'async_initialize' stage succeeded
Device 80:4b:50:ff:fe:3f:3b:2e already exists. Updating it.
[12887:1:0x0006]: bound 'on_off' cluster: Status.SUCCESS
[12887:1:0x0300]: bound 'light_color' cluster: Status.SUCCESS
[12887:1:0x0008]: bound 'level' cluster: Status.SUCCESS
[0x3257:1:0x0006] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=False> manufacturer=None tsn=38 command_id=Command.Configure_Reporting_rsp>
[12887:1:0x0006]: Successfully configured reporting for '{'on_off': (0, 900, 1)}' on 'on_off' cluster: [ConfigureReportingResponseRecord(status=0)]
[12887:1:0x0006]: finished channel configuration
[12887:1:0x0000]: finished channel configuration
[0x3257:1:0x0300] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=False> manufacturer=None tsn=40 command_id=Command.Configure_Reporting_rsp>
[12887:1:0x0300]: Successfully configured reporting for '{'current_x': (30, 900, 1), 'current_y': (30, 900, 1), 'color_temperature': (30, 900, 1)}' on 'light_color' cluster: [ConfigureReportingResponseRecord(status=0)]
[12887:1:0x0300]: finished channel configuration
[12887:1:0x0019]: finished channel configuration
[12887:1:0x0006]: initializing channel: from_cache: False
[0x3257:1:0x0008] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=False> manufacturer=None tsn=42 command_id=Command.Configure_Reporting_rsp>
[12887:1:0x0008]: Successfully configured reporting for '{'current_level': (1, 900, 1)}' on 'level' cluster: [ConfigureReportingResponseRecord(status=0)]
[12887:1:0x0008]: finished channel configuration
[12887:1:0x0300]: initializing channel: from_cache: False
[0x3257:1:0x1000] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=CLUSTER_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=44 command_id=65>
[12887:1:0x0008]: initializing channel: from_cache: False
[12887:1:0x0006]: 'async_configure' stage succeeded
[12887:1:0x0300]: 'async_configure' stage succeeded
[12887:1:0x0008]: 'async_configure' stage succeeded
[12887:1:0x0000]: 'async_configure' stage succeeded
[12887:1:0x1000]: 'async_configure' stage succeeded
[12887:1:0x0019]: 'async_configure' stage succeeded
[12887](ZBT-CCTLight-C4700107): completed configuration
[12887](ZBT-CCTLight-C4700107): stored in registry: ZhaDeviceEntry(name='lk ZBT-CCTLight-C4700107', ieee='80:4b:50:ff:fe:3f:3b:2e', last_seen=1638207060.7810538)
[0x3257:1:0x0006] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=46 command_id=Command.Read_Attributes_rsp>
[12887:1:0x0006]: finished channel initialization
[12887:1:0x0000]: initializing channel: from_cache: False
[12887:1:0x0000]: finished channel initialization
[12887:1:0x1000]: initializing channel: from_cache: False
[12887:1:0x1000]: finished channel initialization
[12887:1:0x0019]: initializing channel: from_cache: False
[12887:1:0x0019]: finished channel initialization
[0x3257:1:0x0300] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=48 command_id=Command.Read_Attributes_rsp>
[12887:1:0x0300]: finished channel initialization
[0x3257:1:0x0008] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=50 command_id=Command.Read_Attributes_rsp>
[12887:1:0x0008]: received attribute: 0 update with value: 254
[12887:1:0x0008]: finished channel initialization
[12887:1:0x0006]: 'async_initialize' stage succeeded
[12887:1:0x0300]: 'async_initialize' stage succeeded
[12887:1:0x0008]: 'async_initialize' stage succeeded
[12887:1:0x0000]: 'async_initialize' stage succeeded
[12887:1:0x1000]: 'async_initialize' stage succeeded
[12887:1:0x0019]: 'async_initialize' stage succeeded
[12887](ZBT-CCTLight-C4700107): power source: Mains
[12887](ZBT-CCTLight-C4700107): completed initialization
[0x3257:1:0x0003] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=False> manufacturer=None tsn=52 command_id=Command.Default_Response>
[12887:1:0x0003]: executed 'trigger_effect' command with args: '(2, 0)' kwargs: '{}' result: [64, <Status.SUCCESS: 0>]
[12887](ZBT-CCTLight-C4700107): started initialization
[12887:ZDO](ZBT-CCTLight-C4700107): 'async_initialize' stage succeeded
[12887:1:0x0006]: initializing channel: from_cache: False
[12887:1:0x0300]: initializing channel: from_cache: False
[12887:1:0x0008]: initializing channel: from_cache: False
[0x3257:1:0x0006] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=54 command_id=Command.Read_Attributes_rsp>
[12887:1:0x0006]: finished channel initialization
[12887:1:0x0000]: initializing channel: from_cache: False
[12887:1:0x0000]: finished channel initialization
[12887:1:0x1000]: initializing channel: from_cache: False
[12887:1:0x1000]: finished channel initialization
[12887:1:0x0019]: initializing channel: from_cache: False
[12887:1:0x0019]: finished channel initialization
[0x3257:1:0x0300] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=56 command_id=Command.Read_Attributes_rsp>
[12887:1:0x0300]: finished channel initialization
[0x3257:1:0x0008] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=58 command_id=Command.Read_Attributes_rsp>
[12887:1:0x0008]: received attribute: 0 update with value: 254
[12887:1:0x0008]: finished channel initialization
[12887:1:0x0006]: 'async_initialize' stage succeeded
[12887:1:0x0300]: 'async_initialize' stage succeeded
[12887:1:0x0008]: 'async_initialize' stage succeeded
[12887:1:0x0000]: 'async_initialize' stage succeeded
[12887:1:0x1000]: 'async_initialize' stage succeeded
[12887:1:0x0019]: 'async_initialize' stage succeeded
[12887](ZBT-CCTLight-C4700107): power source: Mains
[12887](ZBT-CCTLight-C4700107): completed initialization

…but they stop working after that. Attempting to reconfigure gives this:

The device profile looks like this:

{
  "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.Router: 1>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress|RxOnWhenIdle|MainsPowered|FullFunctionDevice: 142>, manufacturer_code=4456, maximum_buffer_size=82, maximum_incoming_transfer_size=82, server_mask=11264, maximum_outgoing_transfer_size=82, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=False, *is_full_function_device=True, *is_mains_powered=True, *is_receiver_on_when_idle=True, *is_router=True, *is_security_capable=False)",
  "endpoints": {
    "1": {
      "profile_id": 260,
      "device_type": "0x010c",
      "in_clusters": [
        "0x0000",
        "0x0003",
        "0x0004",
        "0x0005",
        "0x0006",
        "0x0008",
        "0x0300",
        "0x0b05",
        "0x1000",
        "0xfc82"
      ],
      "out_clusters": [
        "0x000a",
        "0x0019"
      ]
    },
    "242": {
      "profile_id": 41440,
      "device_type": "0x0061",
      "in_clusters": [],
      "out_clusters": [
        "0x0021"
      ]
    }
  },
  "manufacturer": "lk",
  "model": "ZBT-CCTLight-C4700107",
  "class": "zigpy.device.Device"
}

Any pointers for troubleshooting?

1 post - 1 participant

Read full topic

I have an entity-filter card and do not want to show pepole that are either “offline” or “unknown”. If I only put one in it works … if I extend for a second it does not work. I assume a language issue?

this works:

type: entity-filter
entities:
  - entity: sensor.ric_******
state_filter:
  - operator: '!='
    value: offline
card:
  title: Discord Online

this does not:

type: entity-filter
entities:
  - entity: sensor.ric_******
state_filter:
  - operator: '!='
    value: offline
  - operator: '!='
    value: unknown
card:
  title: Discord Online

1 post - 1 participant

Read full topic

I recently got some Philps Hue Color bulbs that don’t seem to work with ZHA out of the box.
I can pair them, they will be detected as “Signify Netherlands B.V. LCA006”. They flash green after pairing and show all the right data but after like 10 seconds they will start pairing again and again, this goes on the whole 60 seconds while zha-pairing is active.

Afterwards the devices are shown in HA but controls don’t work (turn off/on, brightness).

Could that be a device-support issue or is something wrong with my zha database? Has anyone seen this behaviour? I’m not sure what to look for in the zha-debug-log. From the behaviour I would guess zha can read the bulb fine but the bulb does not store the pairing-info.

This is what the device signature looks like:

{
  "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.Router: 1>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress|RxOnWhenIdle|MainsPowered|FullFunctionDevice: 142>, manufacturer_code=4107, maximum_buffer_size=82, maximum_incoming_transfer_size=128, server_mask=11264, maximum_outgoing_transfer_size=128, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=False, *is_full_function_device=True, *is_mains_powered=True, *is_receiver_on_when_idle=True, *is_router=True, *is_security_capable=False)",
  "endpoints": {
    "11": {
      "profile_id": 260,
      "device_type": "0x010d",
      "in_clusters": [
        "0x0000",
        "0x0003",
        "0x0004",
        "0x0005",
        "0x0006",
        "0x0008",
        "0x0300",
        "0x1000",
        "0xfc01",
        "0xfc02"
      ],
      "out_clusters": [
        "0x0019"
      ]
    },
    "242": {
      "profile_id": 41440,
      "device_type": "0x0061",
      "in_clusters": [],
      "out_clusters": [
        "0x0021"
      ]
    }
  },
  "manufacturer": "Signify Netherlands B.V.",
  "model": "LCA006",
  "class": "zigpy.device.Device"
}

Thx,
Kai

1 post - 1 participant

Read full topic

Does anyone else find that automation traces sometimes don’t work, giving a “Chosen trace is no longer available” error message?

Also, how do you enable Script debugging in YAML mode?

I have an automation that is configured with an “id” to enable traces to be recorded. More often than not, when I click on “Show trace” in the Logbook, it tells me that the trace is no longer available. Yet that same automation has previously shown me a trace without issues, and will again sometimes work afterwards.

It’s not just one automation either, it happens with others with no particular pattern as to which one will fail to collect a trace.

Is there any debugging I can enable to find out why the traces sometimes don’t work?

Just in case it helps, one of the automations looks like this:

  - alias: Bed3 Bedside Night Light Button
    id: bed3_bedside_nightlight_button
    initial_state: 'on'
    trigger:
      platform: state
      entity_id: sensor.xiaomi_switch_sw10_action
    action:
      - choose:
          - conditions: "{{ trigger.to_state.attributes.action == 'single' }}"
            sequence:
              - service: script.opple_bed3_2_hold
          - conditions: "{{ trigger.to_state.attributes.action == 'double' }}"
            sequence:
              - service: script.opple_bed3_1_double
          - conditions: "{{ trigger.to_state.attributes.action == 'hold' }}"
            sequence:
              - service: script.opple_bed3_1_hold

1 post - 1 participant

Read full topic

Hello,

I installed home assistant on my nuc and the ram usage was pretty good like 1.6 gig with 43 zigbee devices and many automations. Out of nowhere the server started to use a lot of ram like 3.5gb. I tought it was because I updated the server. But I did restore a backup and the problem was still there. I disabled everything at the supervisor like nodered and zigbee2mqtt but i dont see big diffrences.

Does someone have a idea to where to look for? I don’t see weird things in the logs.

1 post - 1 participant

Read full topic

Hello, everyone,

i have created several presets in the wled surface. I also get this displayed in home assistant. however, an error occurs when executing:

But if i do it via service in developer-tools or node-red, it works for me. I’m actually also sure that it worked recently, and I haven’t made any updates since then.

Home Assistant Core:
core-2021.10.6
Operating System:
6.5

Thank you for your help, greetings

1 post - 1 participant

Read full topic

Hello everyone,

I´m completely new with Smart Home, my question is: How do I create an automation for dimming my light.
I bought this product from Ikea and connected it to my Home Assistant wirh Zigbee2Mqtt.
(TRÅDFRI Set mit Fernbedienung, Weißspektrum, E27 - IKEA Deutschland)

At the moment I can dim the bulb my holding the button, but it change the brightness only one time.
I want to dim the bulb by pressing the button till I stoped.
Can anyone helped me?

1 post - 1 participant

Read full topic

Hi,

I want to turn off my AC display off whatever the AC is turned on. I created an automation on hvac_mode_changed, wait 5 seconds and turn off the display. I would like this automation to fire whatever the hvac mode is selected, right now it only works with heat. Basically I want to: 'Off' inverted.

Thank you

alias: Turn Off AC Display
description: ''
mode: single
trigger:
  - platform: device
    device_id: 85008ff2f96e03a0a7b192156d0e509f
    domain: climate
    entity_id: climate.room_air_conditioner
    type: hvac_mode_changed
    to: 'heat'
action:
  - delay:
      hours: 0
      minutes: 0
      seconds: 5
      milliseconds: 0
  - type: turn_off
    device_id: 85008ff2f96e03a0a7b192156d0e509f
    entity_id: switch.room_air_conditioner_light
    domain: switch

2 posts - 2 participants

Read full topic

Hi!

I’ve been trying to make my first custom automation with temperature based switch control.
I.e. if temperature drops below a certain value, i would like to turn a switch on - and if it goes above the same number it should turn the switch off.

There are a lot of examples here, and it seems fairly simple - but most of them seem to be slightly deprecated syntax wise, and I can’t seem to get them to run.

All i get when i reload my automations is this error:
“Invalid config for [automation]: [service] is an invalid option for [automation]. Check: automation->service. (See /config/configuration.yaml, line 9).”

Can you help me out? This is what i got so far:
(Like to skip the trigger above/below value, but that seems to be mandatory now as well)

- id: '1638214495338'
  alias: Pump Heater
  description: ''
  trigger:
    - platform: numeric_state
      entity_id: sensor.temperature_2
      below: 100
  condition: []
  action:
    - service: >
        {% set temp = states('sensor.temperature_2') | int %}
        {% if temp <= 12 %}
          switch.turn_on
        {% else %}
          switch.turn_off
        {% endif %}
      device_id: 36dcb46fe4a1e4c823a379bdc26a51ae
      entity_id: switch.heater_outlet
      domain: switch

Thanks!

1 post - 1 participant

Read full topic

Hi folks

Running 2011.1 here with the new Energy features fed by an Enphase Envoy.

My issue is that when I add the Energy Distribution card to my Lovelace dashboards, the card does not automatically refresh/update every hour as the underlying data updates. This only happens to the card itself when added to my dashboard, the Energy section of HA updates correctly.

The update to the ED card seems to happen when I switch tabs or dashboards in HA. Is this a bug or is there some underlying config I’m missing?

Thanks

1 post - 1 participant

Read full topic

Hi All!

Well, after searching for some days I am a little lost…

Long story short: I am trying to integrate my domestic water heat pump boiler (Hewalex PCWU 3.0) to my home-assistant instance.

There is an RS485 (modbus) terminal available and have been able to find some documentation on this (here, its in polish)

Based on this a domoticz-plugin is available and a python script which allows control via mqtt (and a pre-made docker). (click for links)

Now, my question:
I’d like to run this python script within home-assistant os (running HA OS as a generic install on an older HP I5).

What is the best/easiest way to do this? can I do this using the python integration, do I need an addon like pyscript/appdeamon? or am I missing something? (is it maybe easier/better to run the docker image instead?)

Thank you in advance!

1 post - 1 participant

Read full topic

Hi,
Suddenly today I started getting notifications:

Login attempt failed
Login attempt or request with invalid authentication from IP (IP). See the log for details.

then few seconds later

Banning IP address
Too many login attempts from IP

The IP address in question belongs to my standalone web server running nginx and it is also acting as a revers proxy for my HA installation.

I am trying to figure out where are the logs that I am supposed to check for details.
Thanks
A

1 post - 1 participant

Read full topic