@dest I think you have more important things than this. 
Please let me know if you have any progress on the matter.
Thanks in advance.
K
K
krisztianszabo
@krisztianszabo
Hey @toggledbits I'm back to trying to optimize a couple of things based on dynamic group.
First of all, I think I found a typo in the doc:
primary_attribute: "binary_sensor.state"
primary_attribute_value: |
d = false;
each id in members: d = getEntity(id)?.attributes?.power_switch?.state or d,
d
I think the correct code snippet is d = false,
All that said, my use case for dynamic groups is to group 3 different climate devices, so I could easily command them at the same time. Commands are good, but sometimes I want to check if any of the devices are on, and that's easily done with a similar snippet as the one you have in the docs. But this is limited to the primary attribute, while I want to have any of the attributes in the group to be driven by a similar logic (while all are null in the group). ie, access hvac_control.mode and see if any of the unit is set to cool, or heat. Is that possible, without re-defining an expression in each of my rules? Thanks!
Edit: Solved in latest-26221.
Bare-metal latest-26193
I have this group:
"OKforLarm":
name: OK för Larm
select:
- include_controller: vera
- include_capability: door_sensor
filter_expression: entity.attributes.door_sensor.state
It contains the entities I expect but behaves a bit odd. When I open vera>device_10097 the entity attribute door_sensor.state changes to true but it won't show up as member in the group, when I also open vera>device_10095 they both shows as members and when I close vera>device_10095 it disappear from the group but when I close vera>device_10097 it lingers in the group until I restart Reactor.
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.
Love openLuup - it just keeps working perfectly.
I started looking at trying to add a gen4 Shelly device to the Shelly plugin via L_ShellyBridge.lua. The plugin is a little uncooked (no rudeness intended), so a bit of a rabbit hole for me.
All of a sudden no console pages available in either Firefox or Chrome. AltUI works perfectly and all the log files indicate no errors. openLuup still running everything works as it should - just no console pages.
I possibly screwed something up but any recently changes files show no problems. The original/ backup of L_ShellyBridge.lua was reinstated but still no console.
Bit stumped on this one. Not sure how to debug. Any ideas?
Hey @toggledbits
One thing that bothers me while doing work on new systems/new features, is that I cannot copy&paste actions, and I cannot drag&drop between set and resets.
#1 is for when I want to copy an action between different rules opened in two separate browser windows, while #2 is when I just need to flip a bunch of actions in the reset, or move some logic back and forth.
Both will be appreciated, but I understand the technical challenges. Thanks!
I'm currently on version 26011. I understand that the aarch64 image is no longer supported. So, I therefore need to update to the ARM64 image. Can anyone possibly suggest how I update my docker compose.yaml file (see below). Ideally I'd like to keep my existing reactions etc. rather than start from scratch.
# Multi-System Reactor template docker-compose.yml (version 22160)
#
# Change the lines indicated by "DO"...
#
services:
reactor:
container_name: reactor
environment:
# DO change the TZ: line to set your local time zone.
# See valid TZ list: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
TZ: GB
#
# DO NOT change this path. Your directory location is in "source" below.
REACTOR_DATA_PREFIX: /var/reactor
# DO change the image below to the one you are using (e.g. armv7l or aarch64 for RPi 4)
image: toggledbits/reactor:latest-aarch64
restart: "always"
expose:
- 8111
ports:
- 8111:8111
volumes:
# DO change the /home/username/reactor below to the directory you created for
# your local data; DO NOT change the /var/reactor part
- /home/pi/docker/reactor:/var/reactor
- /etc/localtime:/etc/localtime:ro
tmpfs: /tmp
It appears that Ezlo is going to new levels of paid subscription for cloud services supporting Vera hubs. I have to congratulate them. It will soon be 8 years since Ezlo acquired Vera, and despite their purported financial and "intellectual" capital, they have to date not produced a viable full replacement for Vera. Now they are going to charge extra for services for a platform that they stopped updating years ago.
If you know anyone who hasn't yet fully moved on from Captain Ahab's White Whale Chase, please remind them that my Decouple project is still up on Github to decouple a Vera Plus/Secure/Edge from Vera/Ezlo's cloud services. Veras have been said to misbehave when they can't reach the mother ship.
I have also written my first new Vera plugin in... six years? more?... the AlertPushover project will send Vera hub alerts to Pushover, so you can still get messages generated by your Vera hub without paying for Ezlo's cloud service. It's crude but functional (i.e. better than nothing/worth every penny paid).
These two projects won't replace the functionality of their cloud service and app for those who need those things. But any that don't, this may help bridge the gap. Hopefully these stragglers who have waited so long and been disappointed so often will get the idea that it's time to move on.
Posts
-
Vera or not vera? -
Vera or not vera?@dest said in Vera or not vera?:
@akbooer Last time, the thing I remember, the plugin was unable to "connect" to the socket on the DSC controller!
I would need to recreate my DSC device on openLuup and disable Vera for being able to test!
Hi @DesT!
Maybe you may have fixed the dsc plugin error?
-
Vera or not vera?@perh said in Vera or not vera?:
if not, you can use /dev/ttyUSBxx(whatever usb you device is connected to)
After many attempts, he finally succeeded.
Ser2net installed, restarted, ser2net.conf configured.
MySensors plugin is not red, startup lua does not write an error.However:
The children's tools were not made, but the shutters did not appear.
Do they need to be created manually? -
Vera or not vera?I think I also reached the limit ....
-
Vera or not vera?@perh said in Vera or not vera?:
if not, you can use /dev/ttyUSBxx(whatever usb you device is connected to)
There is no ttyUSB file in the / dev directory.
There are several tty files numbered here, but without USB ... -
Vera or not vera?@perh
How can I check if I am using debian 10.6?
I tried to type, but unfortunately there is no such directory ... -
Vera or not vera?@perh
Thanks for the reply and tip.
I installed ser2net, I think it worked fine, but I don't have a / serial directory under the / dev directory .....
What do you think I should do then? -
Vera or not vera?Hi @akbooer ,
Another task ahead of me:
I have a 15 channel shutter control module that I want to run under OpenLuup. (if you help I can transfer the plugin files)The shutter control interface is connected to the vera via usb.
The following setting is in Vera:
Where can I make such settings in openLuup?
Thanks -
Imperihome - missing devices@PerH, haven't you experienced this?
-
Imperihome - missing devices@perh said in Imperihome - missing devices:
That was it.
/cgi/Imperihome.lua: Changed "newTarget" to "newTargetValue" at line 385, 672 and 675. (i would upload the updated lua file, but im missing priveleges)
This was not an issue before, has there been changes on this in openluup?
@mrFarmer - FYI
I modified the right lines, it really works now!
At the same time, I can see the icons on the imperihome flashing as if they are constantly reloading ... -
Imperihome - questionYes, local tools are good for me too ...
It would be good if the error could be fixed.The biggest trouble is that I don’t see an alternative to replacing the imperihome.
-
Imperihome - questionI'm sorry @PerH!
I didn't see the same mistake.
I don't have a z-way yet, I thought it was your fault for it ....
Also I have the categories, sub categories ...Do I see that you don't have a solution to the problem yet?
-
Vera or not vera?Hi @DesT !
I don't want to urge you, I'm just interested,
do you have any good news about dsc?
Thanks.
K -
Imperihome - questionHi @mrFarmer,
I also have a question about ImperiHome:
I'm trying to configure imperihome with openluup.
Imperihome recognizes the new system, with all devices, status feedback is perfect.
If I turn on something on imperihome, it will seem to be temporarily turned on and then turn off. Device does not actually change.
Can you help me with what could be the problem?
Thanks.
Krisztian -
Vera or not vera?@akbooer
For some reason, after the AltUi "reload engine" I get a "controller did not respond" response with an orange background.
So far, I thought dsc and harmony are not due to connection.
I just deleted my two unconnected devices.
And still this message.
I looked at the logs for the duration of the error message and did not see anything to throw out.
How can I find out the cause of the error?K
-
Vera or not vera?@akbooer said in Vera or not vera?:
@krisztianszabo said in Vera or not vera?:
Could this be a localization problem?
You perhaps have not set your location correctly in openLuup. The latitude and longitude are initially set in the Lua Startup code, which has as default:
-- You can personalise the installation by changing these attributes, -- which are persistent and may be removed from the Startup after a reload. local attr = luup.attr_set -- Geographical location attr ("City_description", "Greenwich") attr ("Country_description", "UNITED KINGDOM") attr ("Region_description", "England") attr ("latitude", "51.48") attr ("longitude", "0.0")Thank you, I corrected the values. We will see the result when it gets dark ...
-
Vera or not vera?@akbooer
I find that sunrise and sunset happen late on openLuup compared to vera. OpenLuup is delayed for more than 1 hour.
Could this be a localization problem? -
Vera or not vera?@dest said in Vera or not vera?:
That's 'cause of what I said to @akbooer , I need to dig a little bit more as the plugin is having a hard time to "stay connected" to the DSC!
I understand.
I would be happy to offer my help, but I'm afraid you're not going to do much with me .... -
Vera or not vera?@dest said in Vera or not vera?:
@krisztianszabo The password is only used between openLuup and DSC, so there's no password going out!
Check the the file, you have a line like that:local password = luup.variable_get(DSC_PANEL_SID, "InterfacePassword", device) or "user"
so you can replace "user" there!
Yes thanks I found it in the meantime that.
I typed my own password in place of "user", but unfortunately the connection was not established.
Unfortunately, the Dsc Plugin is indicated by a red border. -
Vera or not vera?@dest said in Vera or not vera?:
@krisztianszabo yeah by default the plugin use the default password which is "user", if it's not your case, you can modify the code to change the "default" password to put yours!
I guess the interfacepassword needs to be rewritten in I_DSCAlarmPanel1.xml?
I found text to this effect in this file, but unfortunately I couldn't find where to insert the "interface password" instead of "user" ..."Any password in Vera's device config will be passed cleartext to the MiOS backup servers ..."
I also found the above text in the file. It doesn’t sound too good for the password to be passed to the mios in plain text. Isn't that a problem for me?