Home Assistant Home Assistant WGL Designs W800RF32 Integration

Got the HA WGLw800 integration sort of working even though it doesn't show up in integrations.

Here is what I did.

1 - validate ttyUSB port connectivity to W800.
2 - configuration.yaml file adds:
Code: 
logger:
  default: info
  logs:
    custom_components.w800rf32: debug

w800rf32:
  device: /dev/ttyUSB1

binary_sensor:
  - platform: w800rf32
    devices:
      a1:
        name: chime
3 - copied all of the components
github.com

core/homeassistant/components/w800rf32 at dev · home-assistant/core

:house_with_garden: Open source home automation that puts local control and privacy first. - home-assistant/core
github.com github.com
to config/custom_components/w800rf32

4 - edited the manifest.json file to read:

Code: 
{
  "domain": "w800rf32",
  "name": "WGL Designs W800RF32",
  "codeowners": [],
  "documentation": "https://www.home-assistant.io/integrations/w800rf32",
  "integration_type": "hub",
  "iot_class": "local_push",
  "loggers": ["W800rf32"],
  "requirements": ["voluptuous==0.13.1","pyserial==3.5","pyW800rf32==0.3,"],
  "version": "4.6.5"
}

5 - restarted HA and looked at logs and see:

Code: 
2023-09-27 13:37:05.498 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration w800rf32 which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-09-27 13:37:18.500 INFO (MainThread) [homeassistant.setup] Setup of domain w800rf32 took 0.1 seconds
2023-09-27 13:37:18.695 DEBUG (MainThread) [custom_components.w800rf32.binary_sensor] Add chime w800rf32.binary_sensor (class None)
pressing on and off on Palmpad
2023-09-27 13:38:23.695 DEBUG (Thread-2 (_connect)) [custom_components.w800rf32] Receive W800rf32 event in handle_receive
2023-09-27 13:38:23.696 DEBUG (MainThread) [custom_components.w800rf32.binary_sensor] BinarySensor update (Device ID: A1 Command On ...)
2023-09-27 13:38:23.816 DEBUG (Thread-2 (_connect)) [custom_components.w800rf32] Receive W800rf32 event in handle_receive
2023-09-27 13:38:23.816 DEBUG (MainThread) [custom_components.w800rf32.binary_sensor] BinarySensor update (Device ID: A1 Command On ...)
2023-09-27 13:38:23.936 DEBUG (Thread-2 (_connect)) [custom_components.w800rf32] Receive W800rf32 event in handle_receive
2023-09-27 13:38:23.936 DEBUG (MainThread) [custom_components.w800rf32.binary_sensor] BinarySensor update (Device ID: A1 Command On ...)
2023-09-27 13:38:24.055 DEBUG (Thread-2 (_connect)) [custom_components.w800rf32] Receive W800rf32 event in handle_receive
2023-09-27 13:38:24.056 DEBUG (MainThread) [custom_components.w800rf32.binary_sensor] BinarySensor update (Device ID: A1 Command On ...)
2023-09-27 13:38:24.176 DEBUG (Thread-2 (_connect)) [custom_components.w800rf32] Receive W800rf32 event in handle_receive
2023-09-27 13:38:24.176 DEBUG (MainThread) [custom_components.w800rf32.binary_sensor] BinarySensor update (Device ID: A1 Command On ...)
2023-09-27 13:38:24.294 DEBUG (Thread-2 (_connect)) [custom_components.w800rf32] Receive W800rf32 event in handle_receive
2023-09-27 13:38:24.295 DEBUG (MainThread) [custom_components.w800rf32.binary_sensor] BinarySensor update (Device ID: A1 Command On ...)
2023-09-27 13:38:24.416 DEBUG (Thread-2 (_connect)) [custom_components.w800rf32] Receive W800rf32 event in handle_receive
2023-09-27 13:38:24.417 DEBUG (MainThread) [custom_components.w800rf32.binary_sensor] BinarySensor update (Device ID: A1 Command On ...)
2023-09-27 13:39:29.379 DEBUG (Thread-2 (_connect)) [custom_components.w800rf32] Receive W800rf32 event in handle_receive
2023-09-27 13:39:29.380 DEBUG (MainThread) [custom_components.w800rf32.binary_sensor] BinarySensor update (Device ID: A1 Command Off ...)
2023-09-27 13:39:29.499 DEBUG (Thread-2 (_connect)) [custom_components.w800rf32] Receive W800rf32 event in handle_receive
2023-09-27 13:39:29.500 DEBUG (MainThread) [custom_components.w800rf32.binary_sensor] BinarySensor update (Device ID: A1 Command Off ...)
2023-09-27 13:39:29.618 DEBUG (Thread-2 (_connect)) [custom_components.w800rf32] Receive W800rf32 event in handle_receive
2023-09-27 13:39:29.618 DEBUG (MainThread) [custom_components.w800rf32.binary_sensor] BinarySensor update (Device ID: A1 Command Off ...)
2023-09-27 13:39:29.738 DEBUG (Thread-2 (_connect)) [custom_components.w800rf32] Receive W800rf32 event in handle_receive
2023-09-27 13:39:29.739 DEBUG (MainThread) [custom_components.w800rf32.binary_sensor] BinarySensor update (Device ID: A1 Command Off ...)
2023-09-27 13:39:29.858 DEBUG (Thread-2 (_connect)) [custom_components.w800rf32] Receive W800rf32 event in handle_receive
2023-09-27 13:39:29.858 DEBUG (MainThread) [custom_components.w800rf32.binary_sensor] BinarySensor update (Device ID: A1 Command Off ...)
2023-09-27 13:39:29.978 DEBUG (Thread-2 (_connect)) [custom_components.w800rf32] Receive W800rf32 event in handle_receive
2023-09-27 13:39:29.979 DEBUG (MainThread) [custom_components.w800rf32.binary_sensor] BinarySensor update (Device ID: A1 Command Off ...)
2023-09-27 13:39:30.099 DEBUG (Thread-2 (_connect)) [custom_components.w800rf32] Receive W800rf32 event in handle_receive
2023-09-27 13:39:30.099 DEBUG (MainThread) [custom_components.w800rf32.binary_sensor] BinarySensor update (Device ID: A1 Command Off ...)
2023-09-27 13:39:30.218 DEBUG (Thread-2 (_connect)) [custom_components.w800rf32] Receive W800rf32 event in handle_receive
2023-09-27 13:39:30.219 DEBUG (MainThread) [custom_components.w800rf32.binary_sensor] BinarySensor update (Device ID: A1 Command Off ...)
2023-09-27 13:39:30.339 DEBUG (Thread-2 (_connect)) [custom_components.w800rf32] Receive W800rf32 event in handle_receive
2023-09-27 13:39:30.339 DEBUG (MainThread) [custom_components.w800rf32.binary_sensor] BinarySensor update (Device ID: A1 Command Off ...)

6 - created two automations event to trigger an Alexa TTS.

For A1 On...
Code: 
alias: WGL-W800 A1 Chime ON
description: ""
trigger:
  - platform: state
    entity_id:
      - binary_sensor.chime
    to: "on"
condition: []
action:
  - service: notify.alexa_media_pete_s_echo_show_8_2nd_gen
    data:
      message: A1 is on.
      data:
        type: tts
mode: single

For A1 off

Code: 
alias: WGL-W800 A1 Chime Off
description: ""
trigger:
  - platform: state
    entity_id:
      - binary_sensor.chime
    to: "off"
condition: []
action:
  - service: notify.alexa_media_pete_s_echo_show_8_2nd_gen
    data:
      message: A1 is off.
      data:
        type: tts
mode: single


The above sticks on a restart and reboot.
 
Last edited:
pete_c said:
What do you utilize the W800 for these days?

Been testing a Tasmota 433Mhz hub (Sonoff Bridge) which speaks MQTT. You can purchase a battery operated 8 channel 433Mhz remote for it similiar to the X10 Palmpad.

View attachment 11284

and 433Mhz Sonoff PIRs (which I am using today) and probably contact switches.
Click to expand...

I use the keypads to trigger automation sequences - goodnite macro, start movie scene, shutdown theater system, etc. Also I have a couple of interior door sensors to turn on and off the lights.
 
Tried to follow all you guides here. When I check the configuration I get this error:
Integration error: w800rf32 - Requirements for w800rf32 not found: ['pyW800rf32==0.3,'].
Platform error binary_sensor.w800rf32 - Requirements for w800rf32 not found: ['pyW800rf32==0.3,'].
 
When I try to install pyserial and pyW800rf32 it says they are already installed in /user/lib/python3.11/site.packages

but in file browser I do not have a python3.11 folder under /user/lib
 
What version of Home Assistant are you running?

Here running:
Home Assistant 2023.9.3
Supervisor 2023.09.2
Operating System 10.5
Frontend 20230911.0 - latest

Yes here have a python3.11 folder under /user/lib.

Python 3.11 is included in newest release of Home Assistant.

SSH to your build an add voluptuous

pip install voluptuous

I also installed X10 MQTT Gateway to work with a CM11A
 
Last edited:
Have a look here:

Sonoff RF Bridge with Tasmota


Sonoff RF Bridge Easy Setup with Tasmota Rules and the trigBoard

 
Home Assistant 2023.9.3
Supervisor 2023.09.2
Operating System 10.5
Frontend 20230911.0 - latest

Doing the pip install voluptuous didnt change anything
 
When I use Filebrowser I do not see a python3.11 folder.
However when I ls from the terminal I can see it in purple. Dont know what the purple color means, but I can list the files inside of it.
 
Yes here do not utilize the desktop and only SFTP via root to the HA box.

The box's W800 set up is surviving warm and cold boots. Not sure yet if an update to the HA core will wipe out changes.

Used to use the X10 palm pad for my irrigation way back. Today only use X10 for my Christmas lighting and outdoor landscaping lighting.

Here and related to HA have been adding a bunch of Tasmota firmware updated devices. Wall switches and dimmers, temperature sensors, garage door opener combo, et all.
 
Any idea why I am getting this error:

Integration error: w800rf32 - Requirements for w800rf32 not found: ['pyW800rf32==0.3,'].
Platform error binary_sensor.w800rf32 - Requirements for w800rf32 not found: ['pyW800rf32==0.3,'].
 
Install these three via root ssh access (terminal).

1 - pip install voluptuous
2 - pip install pyserial
3 - pip install pyW800rf32

turn on debug (edit configuration.yaml)

edit the manifest.json file so it reads same as mentioned above.

restart and see if the error goes away.
 
Each install states: "Requirement already satisfies"

Dont know what to put in the configuration.yaml to start debug

This is my manifest:
{
"domain": "w800rf32",
"name": "WGL Designs W800RF32",
"codeowners": [],
"documentation": "https://www.home-assistant.io/integrations/w800rf32",
"integration_type": "hub",
"iot_class": "local_push",
"loggers": ["W800rf32"],
"requirements": ["voluptuous==0.13.1","pyserial==3.5","pyW800rf32==0.3,"],
"version": "4.6.5"
}
 
I deleted the parts of "requirements" that call for specific version. i.e.
"requirements": ["voluptuous","pyserial","pyW800rf32,"],
That let me pass the configuration test. But on reboot I see this in the logs

2023-09-28 12:07:39.851 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration sonoff which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-09-28 12:07:39.851 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration w800rf32 which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-09-28 12:07:39.852 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration blueiris which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-09-28 12:07:39.852 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

but doesn't say the domain was set up like in your example.
 
For debug put this in in your configuration.yaml file.

Code: 
logger:
  default: info
  logs:
    custom_components.w800rf32: debug

running debug and looking at logs you will see if there are any more errors. I disabled my logging today as it was using too much space on the virtual drive.

I am guessing you have confirmed the serial port connection.
Should pick up domain name from top of manifest file. Make sure the RW are the same as other component directories and make sure that the python files are executable. (chmod +x <file>)

This is OK and doesn't prevent integration from running ===>

Code: 
2023-09-28 12:07:39.851 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration w800rf32 which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
 
You must log in or register to reply here.

Similar threads

pete_c
Home Assistant Home Assistant-Homeseer-CumuluxMX Server out of space
Replies
0
Views
66
pete_c
pete_c
pete_c
Pete's Blog Migration of Home Assistant and Homeseer 4 to new hardware-OS
Replies
0
Views
820
pete_c
pete_c
A
Home Assistant OmniLinkBridge
Replies
5
Views
909
pete_c
pete_c
electron
Chat transcript 05/06/2005
Replies
0
Views
4K
electron
electron
Back
Top