Looking at using Home Assistant for the first time, either on a Home Assistant Green, their own hardware or buying a cheap second hand mini PC.
Sounds like Home Assistant OS is linux based using Docker for HA etc.
Would I also be able to install things like MSR as well on their OS ? On the same box?
Thanks.
Having been messing around with some stuff I worked a way to self trigger some tests that I wanted to do on the HA <> MSR integration
This got me wondering if there's an entity that changes state / is exposed when a configured controller goes off line? I can't see one but thought it might be hidden or something?
Cheers
C
Using build 25328 and having the following users.yaml configuration:
users:
# This section defines your valid users.
admin: *******
groups:
# This section defines your user groups. Optionally, it defines application
# and API access restrictions (ACLs) for the group. Users may belong to
# more than one group. Again, no required or special groups here.
admin_group:
users:
- admin
applications: true # special form allows access to ALL applications
guests:
users: "*"
applications:
- dashboard
api_acls:
# This ACL allows users in the "admin" group to access the API
- url: "/api"
group: admin_group
allow: true
log: true
# This ACL allows anyone/thing to access the /api/v1/alive API endpoint
- url: "/api/v1/alive"
allow: true
session:
timeout: 7200 # (seconds)
rolling: true # activity extends timeout when true
# If log_acls is true, the selected ACL for every API access is logged.
log_acls: true
# If debug_acls is true, even more information about ACL selection is logged.
debug_acls: true
My goal is to allow anonymous user to dashboard, but MSR is still asking for a password when trying to access that. Nothing in the logs related to dashboard access. Probably an error in the configuration, but help needed to find that. Tried to put url: "/dashboard" under api_acls, but that was a long shot and didn't work.
I use Virtual Entity Controller virtual switches which I turn on via webhooks from other applications. Once a switch triggers and turns on, I can then activate associated rules.
I would like each virtual switch to automatically turn off after a configurable time (e.g., 5 seconds, 10 seconds).
Is there a better way to achieve this auto-off behavior instead of creating a separate rule for each switch that uses the 'Condition must be sustained for' option to turn it off?
With a large number of these switches (and the associated turn-off rules), I'm checking to see if there is a simpler approach.If not, could this be a feature request to add an auto-off timer directly to the virtual switches.
Thanks
Reactor (Multi-hub) latest-26011-c621bbc7
VirtualEntityController v25356
Synology Docker
TL;DR: Format of data in storage directory will soon change. Make sure you are backing up the contents of that directory in its entirety, and you preserve your backups for an extended period, particularly the backup you take right before upgrading to the build containing this change (date of that is still to be determined, but soon). The old data format will remain readable (so you'll be able to read your pre-change backups) for the foreseeable future.
In support of a number of other changes in the works, I have found it necessary to change the storage format for Reactor objects in storage at the physical level.
Until now, plain, standard JSON has been used to store the data (everything under the storage directory). This has served well, but has a few limitations, including no real support for native JavaScript objects like Date, Map, Set, and others. It also is unable to store data that contains "loops" — objects that reference themselves in some way.
I'm not sure exactly when, but in the not-too-distant future I will publish a build using the new data format. It will automatically convert existing JSON data to the new format. For the moment, it will save data in both the new format and the old JSON format, preferring the former when loading data from storage. I have been running my own home with this new format for several months, and have no issues with data loss or corruption.
A few other things to know:
If you are not already backing up your storage directory, you should be. At a minimum, back this directory up every time you make big changes to your Rules, Reactions, etc.
Your existing JSON-format backups will continue to be readable for the long-term (years). The code that loads data from these files looks for the new file format first (which will have a .dval suffix), and if not found, will happily read (and convert) a same-basenamed .json file (i.e. it looks for ruleid.dval first, and if it doesn't find it, it tries to load ruleid.json). I'll publish detailed instructions for restoring from old backups when the build is posted (it's easy).
The new .dval files are not directly human-readable or editable as easily as the old .json files. A new utility will be provided in the tools directory to convert .dval data to .json format, which you can then read or edit if you find that necessary. However, that may not work for all future data, as my intent is to make more native JavaScript objects directly storable, and many of those objects cannot be stored in JSON.
You may need to modify your backup tools/scripts to pick up the new files: if you explicitly name .json files (rather than just specifying the entire storage directory) in your backup configuration, you will need to add .dval files to get a complete, accurate backup. I don't think this will be an issue for any of you; I imagine that you're all just backing up the entire contents of storage regardless of format/name, that is the safest (and IMO most correct) way to go (if that's not what you're doing, consider changing your approach).
The current code stores the data in both the .dval form and the .json form to hedge against any real-world problems I don't encounter in my own use. Some future build will drop this redundancy (i.e. save only to .dval form). However, the read code for the .json form will remain in any case.
This applies only to persistent storage that Reactor creates and controls under the storage tree. All other JSON data files (e.g. device data for Controllers) are unaffected by this change and will remain in that form. YAML files are also unaffected by this change.
This thread is open for any questions or concerns.
Just another thought. Adding devices from my Home Assistant / Zigbee2MQTT integration. Works perfectly but they always add as their IEEE address. Some of these devices have up to 10 entities associated, and the moment they are renamed to something sensible, each of those entities 'ceases to exist' in MSR. I like things tidy, and deleting each defunct entity needs 3 clicks.
Any chance of a 'bulk delete' option?
No biggy as I've pretty much finished my Z-wave migration and I don't expect to be adding more than 2 new Zigbee devices
Cheers
C
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here.
Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions;
Fix an error in OWMWeatherController that could cause it to stop updating;
Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later;
Improve error detail in messages for EzloController during auth phase;
Add isRuleSet() and isRuleEnabled() functions to expressions extensions;
Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases);
Fix a place in the UI where 24-hour time was not being displayed.
I have tried numerous ways to define a recurring annual period, for example from December 15 to January 15. No matter which method I try - after and before, between, after and/not after, Reactor reports "waiting for invalid date, invalid date. Some constructs also seem to cause Reactor to hang, timeout and restart. For example "before January 15 is evaluated as true, but reports "waiting for invalid date, invalid date". Does anyone have a tried and true method to define a recurring annual period? I think the "between" that I used successfully in the past may have broken with one of the updates.
Good evening all,
For about the past week or so, I've been having problems with a specific rule in my home automation that controls when my home goes from an Away mode to Home mode. One of the conditions it checked for was my alarm panel, when it changed from Armed Away to Disarmed. There seems to have been a firmware update on the panel that added an intermittent step of "pending", and I can't say for certain it happens 100% of the time.
Is there a way to write a condition that so it changes from one condition, to the next, and then another condition? As in, Home alarm changes from armed_away to pending to disarmed.
Thanks.
No idea how easy this would be. During my migration away from Z-wave I've been replacing the Z-wave devices with Sonoff which has broken some of my automations.
Any chance of a 'Test Reaction' function to call out which ones are broken because an entity no longer exists? Without actually running the reaction?
Or does this exist already and I'm just not aware of how to do it? Obviously I can see entities that are no longer available, but not quite what I'm looking for.
I guess it's something of an edge case so no huge issue.
TIA!
C
Home Assistant, ReferenceError: auth is not defined
-
I doesn't succeed with connection to my home assistant.
Anyone that can see what's wrong?
I have also tried with token between " instead of 'From reactor.yaml
- id: hass enabled: true implementation: HassController name: Hassio config: source: 'ws://12.12.12.9:8123' access_token: 'Rm97bt83DGwqyfv4c6wiQRPByhbkJmnYwviP8MLQZXw'From command window:
PS C:\reactor> node app.js Configuration path: config resolved C:\reactor\config 2021-02-28T17:45:25.872Z <app:null> Reactor "0.1.21058" starting on v14.16.0 2021-02-28T17:45:25.874Z <app:INFO> Process ID 1408; platform win32/x64 Windows 10 Education 2021-02-28T17:45:25.875Z <app:INFO> Home C:\reactor; data in . 2021-02-28T17:45:25.894Z <default:INFO> Module Entity v21057 2021-02-28T17:45:25.898Z <Controller:null> Module Controller v21058 2021-02-28T17:45:25.908Z <default:null> Module Structure v21050 2021-02-28T17:45:25.917Z <default:null> Module Ruleset v21041 2021-02-28T17:45:25.919Z <default:null> Module Rulesets v21041 2021-02-28T17:45:25.938Z <default:null> Module Rule v21058 2021-02-28T17:45:25.942Z <default:null> Module Engine v21055 2021-02-28T17:45:25.944Z <default:null> Module httpapi v21041 2021-02-28T17:45:25.954Z <default:null> Module httpproxy v21054 2021-02-28T17:45:25.985Z <default:null> Module wsapi v21053 2021-02-28T17:45:25.987Z <app:NOTICE> Starting HTTP server and API... 2021-02-28T17:45:25.996Z <httpapi:NOTICE> HTTP API v1 21041 base URL http://12.12.12.12:8111; listening 2021-02-28T17:45:26.007Z <app:NOTICE> HTTP server running; registering proxy endpoints. 2021-02-28T17:45:26.008Z <app:NOTICE> Starting WSAPI... 2021-02-28T17:45:26.009Z <wsapi:NOTICE> wsapi: starting version 21053 2021-02-28T17:45:26.011Z <app:NOTICE> Endpoints up; starting Structure... 2021-02-28T17:45:26.012Z <Structure:INFO> Structure#1 starting controller interface vera (VeraController) 2021-02-28T17:45:26.018Z <Structure:INFO> Structure#1 starting controller interface hass (HassController) 2021-02-28T17:45:26.021Z <Structure:INFO> Structure#1 starting controller interface weather (OWMWeatherController) 2021-02-28T17:45:26.022Z <Structure:INFO> Structure#1 starting controller interface reactor_system (SystemController) 2021-02-28T17:45:26.047Z <default:null> Module VeraController v21058 2021-02-28T17:45:26.052Z <default:null> Module HassController v21053 2021-02-28T17:45:26.054Z <default:null> Module OWMWeatherController v21027 2021-02-28T17:45:26.065Z <default:null> Module SystemController v21054 2021-02-28T17:45:26.076Z <VeraController:NOTICE> VeraController#vera starting 2021-02-28T17:45:26.079Z <VeraController:INFO> VeraController#vera loaded mapping ver 21057 rev 2 format 1 notice 2021-02-28T17:45:26.109Z <Controller:INFO> HassController#hass device data loaded; checking structure 2021-02-28T17:45:26.111Z <Controller:ERR> ./server/lib/hass_devices.yaml implementation of capability hvac_blower_swing uses unknown attribute mode 2021-02-28T17:45:26.112Z <Controller:WARN> ./server/lib/hass_devices.yaml implementation of capability hvac_blower_swing does not provide attribute swing; using fixed value=(null) 2021-02-28T17:45:26.129Z <Controller:NOTICE> HassController#hass attempting reconnection to ws://12.12.12.9:8123/api/websocket 2021-02-28T17:45:26.130Z <Controller:NOTICE> HassController#hass connecting to ws://12.12.12.9:8123/api/websocket 2021-02-28T17:45:26.155Z <Controller:NOTICE> Controller SystemController#reactor_system is now online. 2021-02-28T17:45:26.170Z <app:INFO> Structure is now running 2021-02-28T17:45:26.171Z <app:INFO> Pausing for controllers' initial ready 2021-02-28T17:45:26.190Z <Controller:NOTICE> HassController#hass connected, starting protocol 2021-02-28T17:45:26.200Z <Controller:ERR> HassController#hass message handler for auth_invalid failed: ReferenceError: auth is not defined 2021-02-28T17:45:26.210Z <Controller:NOTICE> HassController#hass websocket closed, 1000 2021-02-28T17:45:26.286Z <OWMWeatherController:NOTICE> Controller OWMWeatherController#weather is now online. 2021-02-28T17:45:26.466Z <VeraController:NOTICE> Controller VeraController#vera is now online. 2021-02-28T17:45:26.505Z <OWMWeatherController:ERR> [Entity:setPrimaryAttribute] Attempt to set primary to power_switch.state invalid, not in { "x_vera_rgbcontroller_plugin": { "device_type": "ZWaveColorDevice", "configured": true, "color": "#e900ff0000", "message": "" } } 2021-02-28T17:45:26.506Z <VeraController:ERR> VeraController#vera exception/error while updating VeraController#vera 2021-02-28T17:45:26.507Z <VeraController:CRIT> Error: Entity#vera>device_235:setPrimaryAttribute() can't set power_switch.state, not defined for entity Error: Entity#vera>device_235:setPrimaryAttribute() can't set power_switch.state, not defined for entity at Entity.setPrimaryAttribute (C:\reactor\server\lib\Entity.js:364:19) at C:\reactor\server\lib\VeraController.js:692:118 at processTicksAndRejections (internal/process/task_queues.js:93:5) Error: Entity#vera>device_235:setPrimaryAttribute() can't set power_switch.state, not defined for entity at Entity.setPrimaryAttribute (C:\reactor\server\lib\Entity.js:364:19) at C:\reactor\server\lib\VeraController.js:692:118 at processTicksAndRejections (internal/process/task_queues.js:93:5) 2021-02-28T17:45:31.213Z <Controller:NOTICE> HassController#hass attempting reconnection to ws://12.12.12.9:8123/api/websocket 2021-02-28T17:45:31.215Z <Controller:NOTICE> HassController#hass connecting to ws://12.12.12.9:8123/api/websocket 2021-02-28T17:45:31.226Z <Controller:NOTICE> HassController#hass connected, starting protocol 2021-02-28T17:45:31.237Z <Controller:ERR> HassController#hass message handler for auth_invalid failed: ReferenceError: auth is not defined 2021-02-28T17:45:31.256Z <Controller:NOTICE> HassController#hass websocket closed, 1000 2021-02-28T17:45:36.258Z <Controller:NOTICE> HassController#hass attempting reconnection to ws://12.12.12.9:8123/api/websocket 2021-02-28T17:45:36.260Z <Controller:NOTICE> HassController#hass connecting to ws://12.12.12.9:8123/api/websocket 2021-02-28T17:45:36.272Z <Controller:NOTICE> HassController#hass connected, starting protocol 2021-02-28T17:45:36.283Z <Controller:ERR> HassController#hass message handler for auth_invalid failed: ReferenceError: auth is not defined 2021-02-28T17:45:36.298Z <Controller:NOTICE> HassController#hass websocket closed, 1000 2021-02-28T17:45:41.302Z <Controller:NOTICE> HassController#hass attempting reconnection to ws://12.12.12.9:8123/api/websocket 2021-02-28T17:45:41.303Z <Controller:NOTICE> HassController#hass connecting to ws://12.12.12.9:8123/api/websocket 2021-02-28T17:45:41.314Z <Controller:NOTICE> HassController#hass connected, starting protocol 2021-02-28T17:45:41.336Z <Controller:ERR> HassController#hass message handler for auth_invalid failed: ReferenceError: auth is not defined 2021-02-28T17:45:41.353Z <Controller:NOTICE> HassController#hass websocket closed, 1000 2021-02-28T17:45:46.355Z <Controller:NOTICE> HassController#hass attempting reconnection to ws://12.12.12.9:8123/api/websocket 2021-02-28T17:45:46.357Z <Controller:NOTICE> HassController#hass connecting to ws://12.12.12.9:8123/api/websocket 2021-02-28T17:45:46.368Z <Controller:NOTICE> HassController#hass connected, starting protocol 2021-02-28T17:45:46.377Z <Controller:ERR> HassController#hass message handler for auth_invalid failed: ReferenceError: auth is not defined 2021-02-28T17:45:46.394Z <Controller:NOTICE> HassController#hass websocket closed, 1000 2021-02-28T17:45:47.169Z <app:NOTICE> Shutdown signal (SIGINT) received. Stopping Reaction Engine... 2021-02-28T17:45:47.172Z <Engine:NOTICE> Engine#1 has shut down. 2021-02-28T17:45:47.172Z <app:NOTICE> Closing APIs... 2021-02-28T17:45:47.173Z <wsapi:NOTICE> wsapi closing... 2021-02-28T17:45:47.179Z <httpapi:NOTICE> HTTP API closing... 2021-02-28T17:45:47.180Z <app:NOTICE> Closing Structure... 2021-02-28T17:45:47.181Z <Structure:INFO> Structure#1 Stopping controllers... 2021-02-28T17:45:47.183Z <VeraController:NOTICE> VeraController#vera stopping 2021-02-28T17:45:47.184Z <Controller:NOTICE> HassController#hass stopping 2021-02-28T17:45:47.189Z <Controller:NOTICE> HassController#hass stopping 2021-02-28T17:45:47.190Z <OWMWeatherController:NOTICE> OWMWeatherController#weather stopping 2021-02-28T17:45:47.190Z <OWMWeatherController:NOTICE> OWMWeatherController#weather stopping 2021-02-28T17:45:47.191Z <Controller:NOTICE> SystemController#reactor_system stopping 2021-02-28T17:45:47.193Z <Controller:NOTICE> SystemController#reactor_system stopping 2021-02-28T17:45:47.194Z <Structure:INFO> Structure#1 Final data sync... 2021-02-28T17:45:47.199Z <Structure:NOTICE> Structure Structure#1 stopped 2021-02-28T17:45:47.199Z <app:NOTICE> Stopping timers... 2021-02-28T17:45:47.200Z <app:NOTICE> Shutdown complete, process ID 1408 2021-02-28T17:45:47.201Z <wsapi:NOTICE> wsapi: server closed FORCED EXIT -
Looks like you are using the wrong kind of access token. The instructions specify that you have to use a long-lived access token, and these are usually very long on Hass. Yours is very short (at least, much shorter than the LLATs I've seen on my own system). Did you use a Long-Lived Access Token?
-
Looks like you are using the wrong kind of access token. The instructions specify that you have to use a long-lived access token, and these are usually very long on Hass. Yours is very short (at least, much shorter than the LLATs I've seen on my own system). Did you use a Long-Lived Access Token?
@toggledbits said in Home Assistant, ReferenceError: auth is not defined:
Looks like you are using the wrong kind of access token. The instructions specify that you have to use a long-lived access token, and these are usually very long on Hass. Yours is very short (at least, much shorter than the LLATs I've seen on my own system). Did you use a Long-Lived Access Token?
The lengts seems random I think.
I did 3 tokens, first one super long.
When it didn't work i created another one, in first post.
Now I created the third one, and this became super long, and it works.No idea why, long-lived tokens is the only I can create...
-
Hi! My HA does not connect either. I get a "websocket error" over and over again. This is my reactor.yaml:
- id: hass enabled: true implementation: HassController name: Home Assistant config: source: 'ws://192.168.50.167:8123' access_token: "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiI0ZDg4MzVjZmJkMjQ0ODYwODZhYzc1ZTExZDk2MGU1OSIsImlhdCI6MTYxNTczMzMyMSwiZXhwIjoxOTMxMDkzMzIxfQ.eMGyHpM" -
In CMD it looks like this:
2021-03-14T15:20:27.492Z HassController:NOTICE HassController#hass attempting reconnection to ws://192.168.50.167:8123/api/websocket
2021-03-14T15:20:27.492Z HassController:NOTICE HassController#hass connecting to ws://192.168.50.167:8123/api/websocket
2021-03-14T15:20:27.501Z HassController:WARN HassController#hass socket error during open: Error: socket hang up
2021-03-14T15:20:27.502Z HassController:NOTICE HassController#hass socket to ws://192.168.50.167:8123/api/websocket closed during open
2021-03-14T15:20:27.505Z HassController:ERR HassController#hass connect error with ws://192.168.50.167:8123/api/websocket: websocket error
2021-03-14T15:20:27.505Z HassController:WARN HassController#hass failed to connect/initialize communication: websocket error -
Make sure you have the websocket API enabled in your Hass configuration.
-
That's all that's necessary. I also add the documented
sensorlines so I can see how many connections are active, but it's not strictly necessary to functionality. -
I'm afraid it doesn't work @toggledbits. Shouldn't there be anything after the ":", an IP-adress or something?
@fanan said in Home Assistant, ReferenceError: auth is not defined:
Shouldn't there be anything after the ":", an IP-adress or something?
If you are referring to the "websocket-api:" line in your Home Assistant configuration, no, that line stands by itself. It needs to be properly formatted and placed in your HomeAssistant configuration file. Check your HomeAssistant log for any errors related to its configuration file.
Oh, and just to make sure I've asked, are you keeping up with the builds? Are you testing on the latest build?
Ref: https://www.home-assistant.io/integrations/websocket_api/
-
@toggledbits ; Just a stupid question, since I´m kind of new to this.... Do I have to install the websocket api? I have HACS installed and have tried to add it to the custom resporitories. I tried to add the URL:
and a few more URL as well... But I only get: "Repostitory structure for 2021.3.4 is not compliant", or something else if I try other URL:s.
core/homeassistant/components/websocket_api at dev · home-assistant/core
:house_with_garden: Open source home automation that puts local control and privacy first. - home-assistant/core
I don't want to waste your time with these newbie questions, but after hours and days of failure, I´m becoming desperate... 🥴 -
I just installed Hass via docker, and all I needed to do was add that line to my Hass config and generate the Long-Lived Access Token and everything connected right up. I've never had a problem connecting to Hass, and I didn't have to install anything additional. This is what my configuration file looks like:
# Configure a default setup of Home Assistant (frontend, api, etc) default_config: http: server_host: 0.0.0.0 websocket_api: sensor: platform: websocket_api group: !include groups.yaml automation: !include automations.yaml script: !include scripts.yaml scene: !include scenes.yaml -
T toggledbits locked this topic on
Home Assistant WebSocket API
