Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[lviper]

How are you handling HA's inability to see x10 commands sent from other devices?
Mochad is capable of seeing PL & RF commands not just sending, something HA on the surface appears not to utilize.

I'm using a cm11a for plc. WGL Design's W800usb (supports both regular and security rf) for RF. And lastly HeyU.

Heyu has a state engine built in and the HA X10 component uses this for state information. When I use my palmpad to turn on a light, HA reflects this within a second or 2. HeyU also has a nice scripting function that allows me to map some palmpad rf signals to either be forwarded to plc or to the aux_engine to be processed by HA. So for example, my palmpad is house code F. F1 and F2 or forwarded to the aux_engine and never go to the powerline. This way I can use a script in heyu to send a command directly to HA to turn on a light on a different protocol. Meanwhile the rest of the unit codes on the palmpad transceive directly to plc.

That's why I say you could possibly use the rf of a cm15a to have mochad send everything to the powerline where the cm11 will pick it up and heyu act on it. Just wouldn't directly work for security rf though.

[Tuicemen]

I can't believe HA uses Mochad but doesn't utilize all its possibilities! Makes me wonder how many other things in HA are half baked
The mochad_dispatch >> MQTT user workaround is klunky to say the least.
However they're not the only Linux Home Automation software using mochad and not to its full potential

[lviper]

I know there is way more potential for mochad, and if I knew how to program or script I would run with it. I bet someone who knew how could somehow merge heyu and mochad together so heyu would support the cm15a.

I just felt since I had invested so much in getting my X10 working so reliably with the W800usb for RF and the XTB-RII with CM11a for plc, I had to find a way to continue using the devices. I was never able to get reliable RF from the CM15a even with several different antenna mods. My house is a story and a half and if I include the unfinished full basement, I have over 4000 sq ft. I have my W800usb antenna on the main floor in the middle of the house and it just works. I have 6 MS16's around the house outside all triggering different lights and all of them report in all the time. I have 9 DS10a's on doors and windows and everyone reports in.

[petera]

You've well and truly nailed X10 in Home Assistant along with the other aspects of home automation it has to offer. So much more to explore too by the looks of it. You've taken to Home Assistant on the Raspberry Pi like a duck to water 

So glad your experience was a positive one and a lot more to report in the coming months by the sounds of it.

[Tuicemen]

I don't think heyu needs to be in the mix. (just more things running )
I wonder HA has TCP and HTTP modules and since Mochad is a TCP based application one may be able to tap into that.
I'll see what I can learn on that front.
 

[lviper]

Give this page a look. It's for the Restful API. I used this to have my old program, Home Control Assistant, make calls to turn on lights in HA before I setup X10 in HA.

https://developers.home-assistant.io/docs/en/external_api_rest.html

I also use MQTT Sensors to get my DS10a's and MS16's setup in HA.

https://www.home-assistant.io/components/sensor.mqtt/

[Tuicemen]

I believe Rest , MTTQ and TCP would work but no better then how HA does it now with the Mochad module 
There is a Broadlink switch module which will allow sending any x10 RF even security codes, However no way to tell if the switch was turned on/off by another device as the broadlink RM is oneway (send only).
Saddly I see this isn't the software for me. Love your setup lviper!
 

[petera]

Just curious to know did you script and skin your own Dash files or did you mod examples that you found on the net. I finished off installing AppDaemon and HADashboard, did the Hello World thing so before I reinvent the wheel, did you find working examples you could mod yourself.

[lviper]

Just curious to know did you script and skin your own Dash files or did you mod examples that you found on the net. I finished off installing AppDaemon and HADashboard, did the Hello World thing so before I reinvent the wheel, did you find working examples you could mod yourself.

I did script my own dash file but used the default skin. I basically created my dash file from scratch using what I learned from examples on the net. Here is my main dash file for an example.

Code: [Select]

##
## Main arguments, all optional
##
title: Main Panel
widget_dimensions: [140, 140]
widget_size: [1, 1]
widget_margins: [5, 5]
columns: 7
global_parameters:
    use_comma: 0
    precision: 1
    use_hass_icon: 1
    namespace: default
    devices:
      media_player:
        step: 5

layout:
    - clock(2x1), sensor.smartthings_motionv4_0107d8a1_1_1026, alarm, spacer, spacer, cameradash
    - weather(2x2), porchcamera(3x2), porchlight, weatherdash
    - sidedoor
    - barlight, polelight, craftlight, spotlights, patiolights, backdoor, familysecurity

clock:
    widget_type: clock
    show_seconds: 1

weather:
    widget_type: weather
    prefer_icons: 1
    show_forecast: 1
    forecast_title: Tomorrow
    sensors:
      icon: sensor.dark_sky_icon
      temperature: sensor.dark_sky_temperature
      apparent_temperature: sensor.dark_sky_apparent_temperature
      humidity: sensor.dark_sky_humidity
      precip_probability: sensor.dark_sky_precip_probability
      precip_intensity: sensor.dark_sky_precip_intensity
      precip_type: sensor.dark_sky_precip
      pressure: "" #sensor.dark_sky_pressure
      wind_speed: sensor.dark_sky_wind_speed
      wind_bearing: sensor.dark_sky_wind_bearing
      forecast_icon: sensor.dark_sky_icon_1
      forecast_temperature_min: sensor.dark_sky_overnight_low_temperature_1
      forecast_temperature_max: sensor.dark_sky_daytime_high_temperature_1
      forecast_precip_probability: sensor.dark_sky_precip_probability_1
      forecast_precip_type: sensor.dark_sky_precip_1

spotlights:
    widget_type: light
    icon_on: mdi-spotlight-beam
    icon_off: mdi-spotlight-beam
    entity: group.spotlights
    title: Spot Lights

patiolights:
    widget_type: light
    icon_on: mdi-lightbulb
    icon_off: mdi-lightbulb
    entity: group.patiolights
    title: Patio Lights

craftlight:
    widget_type: light
    icon_on: mdi-spotlight-beam
    icon_off: mdi-spotlight-beam
    entity: light.sengled_e11g13_0311c010_1
    title: Craft Light

backdoor:
    widget_type: light
    icon_on: mdi-lightbulb
    icon_off: mdi-lightbulb
    entity:  light.sengled_e11g13_03117c11_1
    title: Back Door

alarm:
    widget_type: alarm
    entity: alarm_control_panel.alarm_system
    title: Alarm Status

barlight:
    widget_type: light
    icon_on: mdi-lightbulb
    icon_off: mdi-lightbulb
    entity: light.bar
    title: Bar Light

polelight:
    widget_type: light
    icon_on: mdi-lightbulb
    icon_off: mdi-lightbulb
    entity: light.pole
    title: Pole Light

familysecurity:
    widget_type: light
    icon_on: mdi-lamp
    icon_off: mdi-lamp
    entity: light.family_room_security
    title: Family Security Light

sidedoor:
    widget_type: light
    icon_on: mdi-lightbulb
    icon_off: mdi-lightbulb
    entity: light.side_door
    title: Side Door

allfamilyroomlights:
    widget_type: light
    entity: group.familyroomlights
    title: All Family Room Lights

cameradash:
    widget_type: navigate
    title: Cameras
    dashboard: camera
    icon_inactive: mdi-cctv
    args:
      timeout: 15
      return: main

weatherdash:
    widget_type: navigate
    title: Weather
    dashboard: weather
    icon_inactive: mdi-weather-sunny

porchcamera:
    widget_type: camera
    entity_picture: https://REDACTED.duckdns.org:8123/api/camera_proxy_stream/camera.camera_proxy__camerafront_porch?&api_password=REDACTED
    refresh: 300

porchlight:
    widget_type: light
    title: Porch Light
    icon_on: mdi-lightbulb
    icon_off: mdi-lightbulb
    entity: light.porch



[petera]

Probably the best route to go so.

The AppDaemon and HADashboard install instructions were overkill. The process was actually very straightforward in the end. Looking forward to designing my own HADashboard scripts and skins.

Plenty to keep busy over the winter months.

[petera]

Well HADashboard is all up and running. iPad hung on the wall and visibility of widgets is 100%. Some very interesting HADashboard projects on GitHub that can be installed. All that's needed now is a little spare time to install them and configure them around my Home Assistant project.

[lviper]

Congrats. You're one step ahead of me. I still have to get my tablet mounted.

[petera]

Congrats. You're one step ahead of me. I still have to get my tablet mounted.

It was one of the old Gen 1 iPads too. It was heading for the recyclers so I changed the battery and now it has a new home.

The options available to Home Assistant are endless. From basic configuration to high end automation. I'm glad I chose the Python install as the Docker and the Hass.io are very limiting expansion wise.

I'm still laughing at the four spaces and a dash problem one of the users came across in his dashboard configuration. He spent hours trying to figure out the problem. That's the problem when using a plain text editor. If you get down and deep with Python later on try PyCharm IDE. Open source and very able.

Anyway Home Assistant is the distraction of choice for the coming season. Should be fun to see what comes of it.

[petera]

Could you post the config of your hadashboard3.dash file. I think I've discovered a bug in the way the configuration.yaml is passing names to the Dashboard but I just want to confirm this before I report it to Home Assistant.

[lviper]

Could you post the config of your hadashboard3.dash file. I think I've discovered a bug in the way the configuration.yaml is passing names to the Dashboard but I just want to confirm this before I report it to Home Assistant.

What I posted a few posts back is still my current main dash file.