@toggledbits, it's going to take soem time to wrap my head around everything you posted, but it's great to know it's possible!
Feedback / solutions with openLuup's built-in Shelly bridge.
Hi,
For the standard capabilities MSR sends both a value record and a units record to InfluxDB. The latter I would like not to send as they are not really any use for me and it will reduce the number of records send to my InfluxDB.
Is there a quick way to do this with a filter_entities line like: *>units?
Or do I have to update all capabilities to read like this:
power_sensor:
attributes:
value: true
Cheers Rene
I'm trying to replicate this
wallbox_set_number.PNG
into a MQTT entity where I could set a number with a min and max value.
I can't find a standard capability that fits or any documentation on local MQTT capabilities and the only post on the forum mentioning local MQTT capabilities is this post, is it even possible in current release?
My trial and error work in local_mqtt_capabilities.yaml isn't much to show as it's just a copy of mqtt_capabilities.yaml with changed names and then I got stuck.
Any guidance, examples, documentation, future feature request or denial would be much appreciated, thanks!
Reactor 24057-e9add9f5 bare metal
MQTTController 24050
With their awesome new X10 switch!
dbe7408f-dc86-4932-bf71-f0528f5384c1-image.png
I'm hopping in my 1980s time machine to go see whether this is exactly what I think it is. 🙂
(Srsly, tho, I love(d) X10 and did everything humanly possible to keep that old equipment perking along with Vera, and almost succeeded.)
LibraP.S. Just got banned for the 9th time from Hubitat Forum, so had a little extra time to throw shade.
P.P.S. The boilerplate 5-star reviews for this brand-new product come from bots with names like Avery, Phoenix and Owen (two from Mateo!). Sheesh.
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.Hoping you could tell us a bit about your experiences with ZWaveJS and MQTT.
A list of openLuup releases including the latest developments…
master – stable, and infrequently updated, development – latest updates and bug fixes, testing – use only when advised!A long while ago (May, 2015) I wrote my 2000-th post on another forum: openLuup - running unmodified plugins on any machine.
Now rehosted at https://community.ezlo.com/t/openluup-running-unmodified-plugins-on-any-machine/187412
Here’s the gist of it:
...I want to work in a more open and stable [Vera] environment...
...All would be solved if Luup was open source and could be run on the plethora of cheap and reliable hardware available today. But it’s not. But we could get something like that effect if we engineered a sufficient subset of Luup to run on such a platform. Could it be done? What would we need?
1. UI
2. scheduler
3. web server
4. Luup compatible API
5. Device and Implementation xml file reader
6. Zwave bridge to Vera
7. runs most plugins without modification
What we wouldn’t need is UPnP.
What have we (nearly) got already?
We have, courtesy of @amg0, the most excellent AltUI: Alternate UI to UI7, and that, I think, is probably the hardest one to do in the above list. Items 2 - 5, and 7, I’ve prototyped, in pure Lua, and posted elsewhere: DataYours on Raspberry Pi, running selected plugins unmodified, including: DataYours, EventWatcher, Netatmo, RBLuaTest, altUI. See screenshot attached.Is it worth the effort? Probably not. Will I pursue this quest? Yes.
openLuup was the result.
Hi guys,
I've recently bought a new Govee outdoor permanent lights set, and I love it. WAF is pretty high, and the product is good quality. I hope to never run lights in the front of the house.
This new addition has found me searching for something to control these lights, locally. Govee has officials remote and LAN APIs and Home Assistant has it supported, but some undocumented stuff that's integrated into an Homebridge plugin that seems very promising. Without this plugin, my playlist is orchestrated via the cloud and that makes zero sense.
In the past I got some inspiration from plugins running on other platforms and Homebridge seems one of the most active. I could map its devices via HomeKit-local on HA, but I've decommissioned Homebridge years ago when we settled to Alexa (and I want to stay simple), so I had an idea: why get inspiration and rewrite things, when you could write an Homebridge adapter that could load any Homebridge plugin and run them natively under Reactor (MSR)?
I'm not sure if that's viable or made any sense, so I'm posting here to get feedback, encouragement and your thoughts. Anyone could be potentially interested in such a thing?
This system has been running flawlessly year after year for the time changes twice a year literally since MSR came out so I was caught off-guard when this happened this morning.
Time in MSR browser is EST, time on RPi is local time (DST).
76ed5313-b9b9-46d4-b0f9-462c40e99750-image.png
195e61c5-58a7-4453-b96a-18cebae75550-image.png
I've rebooted the RPi I've restarted MSR after double-checking the time on the RPi. Used a completely different browser to eliminate any caching concerns. Double-checked MSR reactor.yamla5f23151-d691-4343-8499-8e77a55528e5-image.png
What am I missing here @toggledbits ?
Hi- looking for a hint in where to start. My goal is to set a PIN code in a zwave kwikset lock triggered in a rule.
The device isn’t exposing methods to help. The x-hass.call-service looks promising, but what would the service name be?
Plan b would be send the zwave controller a config command- I don’t see any way to explicitly send a command through JS Zwave in my environment.
Running reactor bare metal. JS Zwave is running as an add on inside HASS OS.
Any tips are appreciated.
Originally I was using Futzle's UPnP event proxy plugin on Vera with the Sonos plugin. Worked very well.
On making the move to openLuup, one finds that the proxy can't be used because the proxy daemon start and stop, etc uses a script installed by the plugin that only works on openWRT, as used by Vera.
The Sonos plugin still works without the proxy but it reverts to polling. It becomes a bit on the sluggish side and sometimes doesn't function quite as intended.
I've modified the proxy plugin to install a script that runs as a systemd service. systemd can be found on a lot of contemporary Linux installs, including Raspberry Pis. To make use of; just install the plugin from the AltUI app store and restart the Luup engine a couple of times. The dashboard should indicate "Status: Proxy running".
Note that the service file expects "L_UPnPProxyDaemon.lua" to be located at the typical plugin files location:
/etc/cmh-ludl/After the plugin is installed, the service file should be found in:
/etc/systemd/system/as UPnPProxy.service.
If you use the Sonos plugin, you need to change the variable "UseProxy" to "1" and restart the LuupEngine. In the Sonos parent device, you should see: "Running x zones; proxy detected".
Updated doco here.
Hope it works - YMMV.
Hey crew, I'm trying to use MSR to control the RGB values of a Z-Wave bulb in Home Assistant.
Problem I'm running into - I would like to use 'rgb_color.set' to control this, but it doesn't work, instead it always passes the values '255,255,255' to HA no matter what values I enter within MSR.
More notes and examples below - I'm wondering if this is a formatting issue that I'm missing? Thanks for any help!
NOTES FROM TROUBLESHOOTING:
'rgb_color.set_rgb' works successfully, which seems strange. You'd think they would both be affected I've tried a couple different formats, like adding quotes, adding/removing spaces between the RGB values, nothing has fixed it.EXAMPLES:
When I use 'rgb_color.set_rgb', the values successfully carry over to Home Assistant:
f0f4befc-a642-428e-8923-e5f856ca7e2b-image.png
0af0a4f8-50b9-4100-b1e8-52a0de4cbcbb-image.png
But when I use 'rgb_color.set', the values DO NOT successfully carry over to Home Assistant:
9e2d7004-8085-4b70-bb3e-45614b7260a0-image.png 0d630228-c74b-4db8-89bd-2572a08608a3-image.png
DETAILS:
Bulb is LZW42 by Inovelli MSR version: stable-23242-5ee8e1d4HA DETAILS
Core 2024.2.5 Supervisor 2024.02.1 Operating System 12.0Some of you may know that I took at shot at building an alternate geofencing solution for Vera. The core of it was system agnostic, using the OwnTracks application and AWS lambdas to track devices and keep a central data, then disseminate that to the Vera via a websocket-based plugin. It worked with other apps as well, including Tasker and GPSLogger, but of the dozen people that were testing it, most used OwnTracks.
A lot was learned in the process, not the least of which is that the success of any such solution is highly dependent on the phone and its settings. Phone manufacturers love to set things up for the longest battery life, of course, but that's usually very anti-geofencing behavior. In the case of at least one brand, it was unusable and the settings could not be modified. It was also cost-prohibitive to maintain on Amazon, as AWS grabs a dime here and a dollar there and before you know it, it added $100/month to my AWS bill, which my wife deducted from my Scotch budget. Unacceptable.
But it's quite reasonable to use OwnTracks to a local endpoint, and I could pretty easily replicate the functionality as a local application, or maybe even as an additional endpoint built into MSR's API (still separate port and process, but in the package).
So the question really is... would you do it, or would you be too concerned about the security risks associated (e.g., dynamic DNS and NAT mapping in the firewall necessary for the phone to contact the service when not on LAN)?
Since a couple of weeks/months, we are in the process to redo 5 rooms @ home (kids are moving from room to another room) and of course, I would need to redo a bunch of device name and room name in Zway..
Is there an easy way to tell openLuup to completely start over fresh without having to delete/rename them one by one in openLuup ?
Hi,
I’m running MSR in a docker container on my Synology Nas. The container is automatically updated using watchtower weekly.
It was working. Now, after the update, Reactor webpage is able to load, and all indications on the webpage suggests that it is working fine. However, the updated statuses from Home Assistant and Vera are not being detected.
The container logs show the following error
Reactor stable-23344-5aad7754 app 23344 configuration from /var/reactor/config NODE_PATH /opt/reactor:/opt/reactor/node_modules [stable-23344]2024-02-28T21:57:49.516Z <app:null> Reactor build stable-23344-5aad7754 starting on v16.15.1 [stable-23344]2024-02-28T21:57:49.517Z <app:null> Process ID 1 user/group 0/0; docker; platform linux/x64 #69057 SMP Fri Jan 12 17:02:28 CST 2024; locale (undefined) [stable-23344]2024-02-28T21:57:49.517Z <app:null> Basedir /opt/reactor; data in /var/reactor/storage [stable-23344]2024-02-28T21:57:49.517Z <app:null> NODE_PATH=/opt/reactor:/opt/reactor/node_modules [stable-23344]2024-02-28T21:57:49.696Z <Structure:null> Module Structure v23172 [stable-23344]2024-02-28T21:57:49.698Z <Capabilities:null> Module Capabilities v23331 [stable-23344]2024-02-28T21:57:49.780Z <Plugin:null> Module Plugin v22300 [stable-23344]2024-02-28T21:57:49.790Z <TimerBroker:null> Module TimerBroker v22283 [stable-23344]2024-02-28T21:57:49.794Z <Entity:null> Module Entity v22353 [stable-23344]2024-02-28T21:57:49.866Z <Controller:null> Module Controller v23069 [stable-23344]2024-02-28T21:57:50.030Z <default:null> Module Ruleset v22293 [stable-23344]2024-02-28T21:57:50.031Z <default:null> Module Rulesets v22146 [stable-23344]2024-02-28T21:57:50.066Z <GlobalExpression:null> Module GlobalExpression v23211 [stable-23344]2024-02-28T21:57:50.581Z <Predicate:null> Module Predicate v23093 [stable-23344]2024-02-28T21:57:50.595Z <AlertManager:null> Module AlertManager v22283 [stable-23344]2024-02-28T21:57:50.600Z <Rule:null> Module Rule v23107 [stable-23344]2024-02-28T21:57:50.614Z <GlobalReaction:null> Module GlobalReaction v22324 [stable-23344]2024-02-28T21:57:50.617Z <Engine:null> Module Engine v23339 [stable-23344]2024-02-28T21:57:50.635Z <httpapi:null> Module httpapi v23058 [stable-23344]2024-02-28T21:57:50.680Z <wsapi:null> Module wsapi v23172 [stable-23344]2024-02-28T21:57:50.789Z <TaskQueue:null> Module TaskQueue 21351 [stable-23344]2024-02-28T21:57:50.790Z <VeraController:null> Module VeraController v23109 [stable-23344]2024-02-28T21:57:50.971Z <HassController:null> Module HassController v23344 [stable-23344]2024-02-28T21:57:51.716Z <DynamicGroupController:null> Module DynamicGroupController v22313 [stable-23344]2024-02-28T21:57:52.253Z <SystemController:null> Module SystemController v23331 i18n: missing en-US language string: The version of nodejs you are using ({0}) is now end-of-life, and so is deprecated for use with Reactor. Please upgrade nodejs to {2}.{3} or higher as soon as possible; the current LTS version is recommended. Releases of Reactor produced after {1} will not run under this version of nodejs at all. [stable-23344]2024-02-28T21:57:52.256Z <Controller:CRIT> SyntaxError: Unexpected end of JSON input [-] SyntaxError: Unexpected end of JSON input at JSON.parse (<anonymous>) at /opt/reactor/server/lib/Controller.js:464:51 at Array.forEach (<anonymous>) at SystemController._restoreEntities (/opt/reactor/server/lib/Controller.js:458:36) at new Controller (/opt/reactor/server/lib/Controller.js:45:42) at new SystemController (/opt/reactor/server/lib/SystemController.js:29:9) at /opt/reactor/server/lib/Controller.js:101:37 Trace: The version of nodejs you are using ({0}) is now end-of-life, and so is deprecated for use with Reactor. Please upgrade nodejs to {2}.{3} or higher as soon as possible; the current LTS version is recommended. Releases of Reactor produced after {1} will not run under this version of nodejs at all. at _T (/opt/reactor/server/lib/i18n.js:468:37) at AlertManager.addAlert (/opt/reactor/server/lib/AlertManager.js:126:25) at /opt/reactor/app.js:381:140 [stable-23344]2024-02-28T21:57:59.313Z <app:CRIT> SyntaxError: Unexpected end of JSON input [-] SyntaxError: Unexpected end of JSON input at JSON.parse (<anonymous>) at IndividualFileStrategy.getDataObject (/opt/reactor/server/lib/IndividualFileStrategy.js:114:54) at DelayWriteCacheStrategy.getDataObject (/opt/reactor/server/lib/DelayWriteCacheStrategy.js:87:50) at Container.getDataObject (/opt/reactor/server/lib/Container.js:69:67) at Function.getInstance (/opt/reactor/server/lib/Data.js:37:179) at Rule.getRuleStates (/opt/reactor/server/lib/Rule.js:507:100) at Rule.getConditionState (/opt/reactor/server/lib/Rule.js:538:47) at new Rule (/opt/reactor/server/lib/Rule.js:378:47) at Function.getInstance (/opt/reactor/server/lib/Rule.js:387:36) at /opt/reactor/server/lib/Engine.js:263:53 i18n: missing en-US language string: HomeAssistant on {0:q} may be an unsupported version. The reported version ({1}) has not been certified/tested with this version of Reactor and may cause errors. You must either modify your HomeAssistant install, or see if an update to Reactor has been made available. Trace: HomeAssistant on {0:q} may be an unsupported version. The reported version ({1}) has not been certified/tested with this version of Reactor and may cause errors. You must either modify your HomeAssistant install, or see if an update to Reactor has been made available. at _T (/opt/reactor/server/lib/i18n.js:468:37) at AlertManager.addAlert (/opt/reactor/server/lib/AlertManager.js:126:25) at HassController.sendWarning (/opt/reactor/server/lib/Controller.js:197:36) at /opt/reactor/server/lib/HassController.js:1117:370 at processTicksAndRejections (node:internal/process/task_queues:96:5)I’ve tried using “latest-amd64” and it does not work either. The logs show similar json input error.
Reactor latest-24057-e9add9f5 app 24052 configuration from /var/reactor/config NODE_PATH /opt/reactor:/opt/reactor/node_modules [latest-24057]2024-02-28T22:27:30.466Z <app:null> Reactor build latest-24057-e9add9f5 starting on v20.10.0 [latest-24057]2024-02-28T22:27:30.522Z <app:null> Process ID 1 user/group 0/0; docker; platform linux/x64 #69057 SMP Fri Jan 12 17:02:28 CST 2024; locale (undefined) [latest-24057]2024-02-28T22:27:30.522Z <app:null> Basedir /opt/reactor; data in /var/reactor/storage [latest-24057]2024-02-28T22:27:30.522Z <app:null> NODE_PATH=/opt/reactor:/opt/reactor/node_modules [latest-24057]2024-02-28T22:27:30.667Z <Structure:null> Module Structure v23172 [latest-24057]2024-02-28T22:27:30.673Z <Capabilities:null> Module Capabilities v23331 [latest-24057]2024-02-28T22:27:30.780Z <Plugin:null> Module Plugin v22300 [latest-24057]2024-02-28T22:27:30.787Z <TimerBroker:null> Module TimerBroker v22283 [latest-24057]2024-02-28T22:27:30.791Z <Entity:null> Module Entity v22353 [latest-24057]2024-02-28T22:27:30.796Z <Controller:null> Module Controller v23069 [latest-24057]2024-02-28T22:27:30.811Z <default:null> Module Ruleset v22293 [latest-24057]2024-02-28T22:27:30.811Z <default:null> Module Rulesets v22146 [latest-24057]2024-02-28T22:27:30.821Z <GlobalExpression:null> Module GlobalExpression v23211 [latest-24057]2024-02-28T22:27:30.890Z <Predicate:null> Module Predicate v23093 [latest-24057]2024-02-28T22:27:30.958Z <AlertManager:null> Module AlertManager v22283 [latest-24057]2024-02-28T22:27:31.027Z <Rule:null> Module Rule v24057 [latest-24057]2024-02-28T22:27:31.033Z <GlobalReaction:null> Module GlobalReaction v22324 [latest-24057]2024-02-28T22:27:31.036Z <Engine:null> Module Engine v24023 [latest-24057]2024-02-28T22:27:31.042Z <httpapi:null> Module httpapi v24057 [latest-24057]2024-02-28T22:27:31.216Z <wsapi:null> Module wsapi v24057 [latest-24057]2024-02-28T22:27:31.296Z <TaskQueue:null> Module TaskQueue 21351 [latest-24057]2024-02-28T22:27:31.297Z <VeraController:null> Module VeraController v24050 [latest-24057]2024-02-28T22:27:31.365Z <HassController:null> Module HassController v24048 [latest-24057]2024-02-28T22:27:31.659Z <DynamicGroupController:null> Module DynamicGroupController v22313 [latest-24057]2024-02-28T22:27:31.668Z <SystemController:null> Module SystemController v23331 [latest-24057]2024-02-28T22:27:31.673Z <Controller:CRIT> SyntaxError: Unexpected end of JSON input [-] SyntaxError: Unexpected end of JSON input at JSON.parse (<anonymous>) at /opt/reactor/server/lib/Controller.js:464:51 at Array.forEach (<anonymous>) at SystemController._restoreEntities (/opt/reactor/server/lib/Controller.js:458:36) at new Controller (/opt/reactor/server/lib/Controller.js:45:43) at new SystemController (/opt/reactor/server/lib/SystemController.js:237:9) at /opt/reactor/server/lib/Controller.js:101:37 [latest-24057]2024-02-28T22:27:38.845Z <app:CRIT> SyntaxError: Unexpected end of JSON input [-] SyntaxError: Unexpected end of JSON input at JSON.parse (<anonymous>) at IndividualFileStrategy.getDataObject (/opt/reactor/server/lib/IndividualFileStrategy.js:51:45) at DelayWriteCacheStrategy.getDataObject (/opt/reactor/server/lib/DelayWriteCacheStrategy.js:89:49) at Container.getDataObject (/opt/reactor/server/lib/Container.js:69:65) at Data.getInstance (/opt/reactor/server/lib/Data.js:45:179) at Rule.getRuleStates (/opt/reactor/server/lib/Rule.js:515:101) at Rule.getConditionState (/opt/reactor/server/lib/Rule.js:546:47) at new Rule (/opt/reactor/server/lib/Rule.js:371:47) at Rule.getInstance (/opt/reactor/server/lib/Rule.js:380:36) at /opt/reactor/server/lib/Engine.js:828:53 i18n: missing en-US language string: HomeAssistant on {0:q} may be an unsupported version. The reported version ({1}) has not been certified/tested with this version of Reactor and may cause errors. You must either modify your HomeAssistant install, or see if an update to Reactor has been made available. Trace: HomeAssistant on {0:q} may be an unsupported version. The reported version ({1}) has not been certified/tested with this version of Reactor and may cause errors. You must either modify your HomeAssistant install, or see if an update to Reactor has been made available. at _T (/opt/reactor/server/lib/i18n.js:614:37) at AlertManager.addAlert (/opt/reactor/server/lib/AlertManager.js:128:25) at HassController.sendWarning (/opt/reactor/server/lib/Controller.js:197:36) at /opt/reactor/server/lib/HassController.js:1133:374 at process.processTicksAndRejections (node:internal/process/task_queues:95:5)How do I fix this?
Akbooer: it would be good if openLuup was added to the awesome mqtt resources list.
How to contribute is described here.
Hello forum instigators.
Not sure who host/runs the forum software but a couple of challenges:
The chat is not currently usable, as the scrolling is all not right and it's not possible to read chats or send chats reliably.
There are a lot of female members that should perhaps be on another forum; where they can advertise their skills more appropriately. Note: I agree it's a job, like any other.
Whoever you are - thank you for your invaluable work.
I’m moving a lot of my home automation Raspberry Pi’s to Proxmox virtualisation and really enjoying it.
I would like to install Reactor that way too. Having researched this forum I’m surprised more people haven’t ventured into this. Although I use HomeAssistant in Proxmox I don’t want to use the HAOS path addin one user has tried as it seems to be unsupported now.
What would be the best way to install Reactor under Proxmox? As a Linux VM (flavour?) with manual install or as a Docker install or even following the Portainer write up with Docker install underneath? Proxmox tend to recommend you away from Docker where possible.
Keeping Reactor upto date easily would be a big consideration too.
Thanks for any recommendations and anyone running Reactor within Proxmox already ?
There’s a growing number of helper scripts for Proxmox that one click install home automation favourites as a prebuilt Linux container (LXC) . It would be nice to get Reactor listed and installed this way too…under the automation category
Noticed right away last night at closing time that the open/close had become inverted with the update to v23326.
It wasn't an awful bit of lift to change all Reactions to reflect the change but it was jarring initially when everything flipped.
Are there release notes on that version, @toggledbits ?
tamorgen
Posts
-
-
Good morning,
I'm running Home Assistant with MSR, and I do my automation strictly within MSR. I have some basic notifications set up, for instance, when my dishwasher has completed it's cycle, it'll send my iPhone a push notification via the x_haas.system.call_service --> notify.mobile_iphone action.I saw in the Home Assistant documentation that you can push Actionable Notifications. The example they use if there is motion detection, but no one is home, you can sound an alarm or silence an alarm.
Can this be done from MSR and not directly in Home Assistant? I'd like to do something more of an acknowledgement, like if a door or window is left open, to have a way to get notified, but acknowledge that it is open, and not send any more notifications. If not acknowledged, the notification will continue every 5 or 10 minutes until the door or window is closed, or the notification is acknowledged. This would be useful in situations where I may have a slider door open for some fresh air, so it was deliberate, versus an entry door that didn't latch when entering or leaving the house.
-
@gwp1 ,
I really don't have any sort of weekly config on mine. I haven't noticed mine drifting at all, but a weekly recalibrate wouldn't be a bad idea.
I have rules for hourly refreshing the the cover, position, and switch positions that are now pretty much legacy of the old device class. I only have two of the IB2 devices left, and they're in non critical rooms ( guest bedroom and mudroom). I'll replace those later this year. Once those are gone, I'll be able to remove those three hourly rules.
I have reactions set up for each set of windows in a room. Most rooms only have two windows, so I group those. The lone exception is my family room, where I have four windows, but on different walls. I have those set up on two separate reactions, which allows me to separately set the blinds to a partial open position when the sun is shining directly in. The largest events with the blinds are at sunrise, sunset, and when the house is vacant or someone arrives, when I'll set the reactions from the rule, and I have "Wait for completion" enabled after each call for a reaction. It takes a couple of minutes for all my blinds to open/close when it's called. I initially didn't do this, but iBlinds recommended not calling them all at once (thus the pause in between each call for a blind to open/close). For the most part, this has helped tremendously with the IB2 motors, although they still had their fair share of problems, which is why I've been replacing them all this year.
I call the reactions from rulesets, so I don't have to reinvent the wheel each time I want to perform an action on a window. It also allows me to make an adjustment once and not 10 different times in different rules.
-
@gwp1 said in [SOLVED-ish] New iblind and zwaveJScontroller/MSR not communicating:
It's more helpful if, instead of generalized statements, you provide settings/configurations you're using whilst having this success for comparison sake.
All of mine are like this, cover.close, cover.open.
Perform cover.close on Office Blind Left (zwavejs>30-0) Delay for 5 seconds Perform cover.close on Office Blind Right (zwavejs>31-0) Delay for 5 seconds Perform zwave_device.refresh on Office Blind Left (zwavejs>30-0) Perform zwave_device.refresh on Office Blind Right (zwavejs>31-0)
I'm not even sure the zwave.device.refresh is needed anymore. This was more of an issue when trying to force the old device class to refresh on both the binary switch and the multi-level switch, as they weren't directly connected and didn't update each other. It was one of the reasons that the folks at iBlinds were pushing to get the window device class implemented.
-
@gwp1, I just replaced 6 of my ib2 motors with ib3.1, and they are working just fine (12 of 14 are v3.1). I can control them from MSR with ZWJSController without issue.
My only issue is actually Home Assistant itself. I've had to go to great lengths to get a somewhat working card for each of the blinds in my home, and I'm still not completely there yet. I'm hoping either the ZWaveJS devlopers or the HA developers figure out whats going on with the 'state' value for each of these, as they all return 'unknown', so none of the cards work out of the box.
-
@gwp1,
I'm working on trying to make something useful in the dashboards using this new device class, and it's not going well. I've reached out to iBlinds/Eric B for help. What we are both seeing as unknown/null states could be a problem.There are three values that are null or unknown: cover.state, position.value, and then a repeat using the x_hass.state.
When I go into Developer Tools in HA, the state is unknown as well. That makes sense since MSR has to grab it from somewhere.
I'm trying to work on my dashboard and display some useful information, and I'm unable to get the value of the attributes. I'm guessing that's because the State is unknown.
Hopefully iBlinds can work with HA and ZWaveJS and get these values to show properly.
-
@gwp1,
Thanks, I figured it couldn't hurt to ask someone else running HA to see if they were experiencing the same problems. I think it just might be old batteries. -
@gwp1 ,
Not to steal your thread, but out of curiosity, have you noticed any issues with battery life lately? I've noticed that a few of my iBlinds are draining very rapidly, ending in a unresponsive state. I've charged them, then less than a week later, they are dead and unresponsive.They all appear to be the older v2 iBlinds, so it could just be that the batteries are ending their useful life, however, it's also possible that the new configuration and command class is affecting them in some way. I'm gradually replacing them, as I've found the v3.1 iBlinds to be much more reliable. I haven't noticed this behavior in the v3.1 iBlinds.
I'm just curious if you've seen this as well. If you are seeing it, it could be an issue with how ZWaveJS is communicating with the iBlinds due to this new roleout.
-
Okay, gotcha. I did verify that the cover.open using the zwavejscontroller entries does work on my system with the updated release. Curious that the cover.open command does not work using the equivalent haas entity.
-
@gwp1
It seems to me that something may be missing from this command class integration. I know iBlinds was working with the ZWaveJS developers. I'm curious is this is what they expected.When I look at the entities in MSR, there are a lot of entries that have null or unknown. I'm not sure if this is coming from MSR expecting entries in a specific command class or if ZWaveJs is providing it to MSR that way.
Of all the actions in that window, the cover.xxx don't seem to work for me. The only ones that seem to work are:
x_hass_cover.close_cover_tilt
x_hass_cover.open_cover_tilt
x_hass_cover.set_cover_tilt_positionOthers may work, but these are the one's I know specifically work and from an automation perspective meet my needs.
-
@gwp1 said in [SOLVED] New iblind and zwaveJScontroller/MSR not communicating:
With these new changes from HA, these commands have become hit/miss.
To be precise, it's not so much a change from HA, but from ZWaveJS. They're recognizing a new command class that the developers at iBlinds actually recommend.
I don't believe the old power switch commands work with the new command class. When I go into a specific device in ZwaveJS, the switch type devices are greyed out.
if you go into the switch, it shows it as unavailable.
I would guess the power on/off cover.close / cover.open are remnants and probably need to be removed.
-
I've been using the ID hass>cover_blind_horizontal_slats_angle and x_hass_cover.open_cover_tilt or x_haas_cover.close_cover_tilt and it works flawlessly for open and close. If I want to set the position for partial close when the sun is glarring into the room, I use x_hass_cover.set_cover_tilt_position with the same ID, and set the tilt_position to whatever I want to reduce the glare.
My only problem now is that I use mushroom for my dashboard in Home Assistant, and the templates for covers hasn't caught up with the new Window Covering class. It makes adjusting the blinds more problematic from HA.
-
@gwp1 said in [SOLVED] New iblind and zwaveJScontroller/MSR not communicating:
Further, I just discovered if I do a
reinterview
on an existing blind via ZWaveJS in HA it switches to this new Window Covering mode.For what it's worth, I have both v2 and v3.1 iBlinds in my home. Reinterviewing only changes the type from multilevel switches to window covering on v3.1 blinds. Version 2 blinds remain multilevel switches after reinterviewing.
The Window Covering class is supposedly better. The MLS class is designed for rolling blinds, so on/off will have the bllinds all the way open, or all the way off. With horizonal blinds, the 0/100 values are just 180 degree opposites of a closed blind. With Window Covering class, I believe there are values to tell the Z-Wave system what type of blind it is, and specify what is open versus closed. I dealt with iBlinds support maybe 4 or 5 months ago, and at the time, no Z-Wave system supported Window Covering. Zwave JS implemented the change shortly thereafter.
-
Good afternoon,
I'm running my MSR instance on an old NAS server running Fedora 37 Server. This is an older Core i5-4690K server that has served me well overall, but it's showing it's age, and will often reboot into maint mode if it applies updates overnight. I've been trying to troubleshoot, but it's also in my office (makes my office hot), and I'm looking at getting either a QNAP or Syslogy rack mount NAS to replace it.What I'm wondering is what the process would be to migrate my current MSR config and move it to a different platform. I have quite a large ruleset that I don't want to have to recreate. I know I can run it in a container on either platform, but I'm not sure how I would migrate all my rules over. Is there one config file that has all of the rules, or could I simply copy my /reactor directory over to a enw platform?
I am also considering moving the MSR instance to a stand alone RPI 4 with a SSD. This way, while I'm migrating all of my files off of my NAS, I'm not loosing Reactor's functionality until I have whichever rack mount NAS I go with up and running, with all of the data migrated.
Thoughts?
-
@toggledbits said in MSR - Bug report:
This is all great. Your "New Information" message would have gotten me there; I can see it now. Thanks for the extra information, that helps confirm the first and cover other cases.
Stay tuned for fix...
I'm glad you were able to see and replicate my issue. I'm also glad that I was able to come up with a work around until you're able to present a fix.
-
@toggledbits,
Final piece of the puzzle. If I change the sustained seconds value itself, I can change the sustained operator. I'm now able to correct the rules operator, but I have to change the seconds value along with the operator for it save properly. This is a work around, but no matter what I to do, the restriction operator cannot be changed by only changing the drop down.I hope this makes sense and you can reproduce it on your end, to determine the cause. If you need anything else from me, please let me know.
-
@toggledbits,
I just tried another method for verification. I tried making a copy of the rule, and editing that copy. I'm unable to change that restriction operator on the newly copied rule. I'm assuming it saves it when the rule is copied, so when I go to edit that restriction, it acts like an existing rule, and will not allow the change to be saved.Please let me know if I can provide any more information.
-
@toggledbits
New information: I created a new rule, and the "less than" operator does save properly. The issue seems to only be the case when changing the restriction operator on existing rules.I also tried to change that newly created rule restriction operator from "less than" to "at least", and just like my other existing rules, it failed to save after the change.
I hope this helps.
-
I changed the drop down. This was an existing set of rules that stopped working at some point in the past, because it was set to less than, and now is showing up as greater than. I keep trying to just change the drop down to less than and it doesn’t change upon saving.
Change in this case simply means changing the operator in the restriction, as is shown in the screenshots.
Edit: I've had these rules set up since the Vera days (Vera Reactor). These rules don't do anything themselves (as in they are triggers only, no reactions.) They are used in multiple other rules, which rely on their state. I have two of these types for each user in my Home Assistant user base; one for arriving conditions, and one for departing state. I've attempted to change the restriction sustained operator on several of these independent rules, and the result is the same on each; that being, even though the restriction states "Condition must be sustained for less than 300" seconds.", after I click Save, then Exit, I look at the rule I just edited, the rule states "at least", not "less than".
I'm observing this behavior on all 8 of the trigger conditions I have this in use.
I'm sorry if this doesn't seem clear from a developer perspective, but changing the drop down operator and saving, and it not actually saving seems fairly clear to me from a user perspective. I understand there are more variables to consider on your end, and I'm trying to provide as much information as possible.
-
@toggledbits,
I'm running this on Chrome on my Mac Studio M2 Max when I discovered the issue, however, I tried it again at work on Windows 10 running Chrome, and experienced the same result. I haven not tired it on a different browser, only Chrome. I didn't do a hard refresh, but I did try incognito mode.I just tried in Safari and experienced the same result.
The exact steps were listed (Changed and saved, exited, viewed rule).
I'm currently unable upload screenshots (I had this issue the other day).
Actionable notification question
Actionable notification question
[SOLVED] New iblind and zwaveJScontroller/MSR not communicating
[SOLVED] New iblind and zwaveJScontroller/MSR not communicating
[SOLVED] New iblind and zwaveJScontroller/MSR not communicating
[SOLVED] New iblind and zwaveJScontroller/MSR not communicating
[SOLVED] New iblind and zwaveJScontroller/MSR not communicating
[SOLVED] New iblind and zwaveJScontroller/MSR not communicating
[SOLVED] New iblind and zwaveJScontroller/MSR not communicating
[SOLVED] New iblind and zwaveJScontroller/MSR not communicating
[SOLVED] New iblind and zwaveJScontroller/MSR not communicating
[SOLVED] New iblind and zwaveJScontroller/MSR not communicating
[SOLVED] New iblind and zwaveJScontroller/MSR not communicating
Migration question
MSR - Bug report
MSR - Bug report
MSR - Bug report
MSR - Bug report
MSR - Bug report
MSR - Bug report