-
Posted this in Vera forum with no response:
Seeing this in reactor UI:
A newer version of the device information database is available. Please use the update function on the Tools tab to get it. This process is quick and does not require a Luup reload or browser refresh–you can immediately come back here and go right back to work! The new version is 865.877, and you are currently using 557.352…Hit update in Tools and get an error: “The update could not be retrieved. If this problem persists, consult the documentation.”
Looked through logs and not seeing anything specific. You have a keyword I should search for?
-
Hi Rene @mrFarmer just thought i would let you know that the new broadlink app from Ezlo causes an error in log, It does not stop the bridge.
luup.variable_set:: 24.urn:rboer-com:serviceId:EzloBridge1.Ezlo_deviceMap was: {"603a8896122335165e686cb3":29,"5fe26c71122335120f05323e":23,"603a8896122335165e686cb7":30,"5fd354fc12233516e1e0c3b... now: {"603a8896122335165e686cb3":29,"5fe26c71122335120f05323e":23,"603a8896122335165e686cb7":30,"603a869b122335165e686cb... #hooks:0 2021-04-14 20:15:47.641 luup_log:24: EzloBridge_error: No device found for device id 32. 2021-04-14 20:15:47.642 luup_log:24: EzloBridge_error: No device found for device id 32. 2021-04-14 20:15:47.643 luup_log:24: var.SetString: wrong data type (number) for variable TamperAlarm 2021-04-14 20:15:47.644 luup_log:24: creating device numbers: [20016,20029,20023,20009,20021,20030,20031] 2021-04-14 20:15:47.645 luup_log:24: linking to remote scenes... 2021-04-14 20:15:47.645 luup.variable_set:: 24.urn:upnp-org:serviceId:altui1.DisplayLine1 was: Getting devices and scenes... now: 7 devices, 4 scenes #hooks:0 2021-04-14 20:15:47.646 luup.variable_set:: 24.urn:upnp-org:serviceId:altu
here is the logTried excluding the device but not sure what number to put tried 32 and the longer ezlo device id, but caused ezlo bridge to fail.
-
Hey @toggledbits updated to Reactor 3.9develop-21009.1600 on my VP running 7.32 and I keep getting this pop up and can't change anything in my reactor sensors because of it. I am running Alt UI 2.52 and there are no updates for it. Screen Shot 2021-03-31 at 8.33.47 PM.png
-
@toggledbits On my veraplus I try to use the plugin switchboard. On my veraplus I use a virtual window covering which can also be used in google home with tts. Now I also use openluup. The virtual window covering is not visible in openluup. Is this correct? I also use reactor in openluup. If this virtual window covering is not visible in openluup, I cannot use it in reactor either
-
Is there any chance of @amg0 becoming an active member, do you think?
He appears to be not responding on GitHub (I opened my licensing query a month back)
There are also some challenges around how things like thermostats behave in their display which would be great if we could get them fixed. Well beyond my capability 😞C
-
While i wait for MSR to arrive, i'm trying to get better control over my zigbee devices. Looked over the fence to Domoticz, and they have a really good plugin for Zigate, and as there was a domoticz bridge here, i thought i'd use that instead..
This plugin have bben abandoned for some years though, and when I installed it, it won't start properly.. looking at the startup log, it looks like OpenLuup might have had some changes that needs to be handled in the plugin? (@akbooer ?)
2021-01-26 22:31:37.457 luup.create_device:: [833] D_DomoticzBridge.xml / I_DomoticzBridge.xml / D_DomoticzBridge.json (DomoticzBridge) 2021-01-26 22:31:37.457 openLuup.chdev:: [string "L_DomoticzBridge.lua"]:59: module 'openLuup.rooms' not found: no field package.preload['openLuup.rooms'] no file './openLuup/rooms.lua' no file '/usr/local/share/lua/5.1/openLuup/rooms.lua' no file '/usr/local/share/lua/5.1/openLuup/rooms/init.lua' no file '/usr/local/lib/lua/5.1/openLuup/rooms.lua' no file '/usr/local/lib/lua/5.1/openLuup/rooms/init.lua' no file '/usr/share/lua/5.1/openLuup/rooms.lua' no file '/usr/share/lua/5.1/openLuup/rooms/init.lua' no file '../cmh-lu/openLuup/rooms.lua' no file 'files/openLuup/rooms.lua' no file 'openLuup/openLuup/rooms.lua' no file './openLuup/rooms.so' no file '/usr/local/lib/lua/5.1/openLuup/rooms.so' no file '/usr/lib/x86_64-linux-gnu/lua/5.1/openLuup/rooms.so' no file '/usr/lib/lua/5.1/openLuup/rooms.so' no file '/usr/local/lib/lua/5.1/loadall.so' no file './openLuup.so' no file '/usr/local/lib/lua/5.1/openLuup.so' no file '/usr/lib/x86_64-linux-gnu/lua/5.1/openLuup.so' no file '/usr/lib/lua/5.1/openLuup.so' no file '/usr/local/lib/lua/5.1/loadall.so' -
Morning, all
Couple of AltUI issues.
On this machine AltUI correctly reports its licensed status. On another machine, it claims to be unlicensed, and not of my favourites etc are reflected. Is this correct behaviour? Surely it doesn't need a licence per browser? Neither machine will upgrade to the latest version, if I select it from the pop up. Should I be doing it another way?TIA
C
-
rafale77/Amcrest-Dahua-Openluup rafale77/Amcrest-Dahua-OpenluupPlugin for Amcrest/Dahua Cameras on openLuup. Contribute to rafale77/Amcrest-Dahua-Openluup development by creating an account on GitHub.
-
So, I was bored to see all those "device not responding" banners in the Alexa app and I created a new plug-in:
dbochicchio/Vera-HABridge dbochicchio/Vera-HABridgeLuup plugin to syncronize Vera/openLuup status to HA-Bridge and Alexa. - dbochicchio/Vera-HABridge
This will update your devices' status to HA-Bridge and Alexa will finally reflect the correct status!
Just install, insert the HA-Bridge IP and port and you're done. It will work with lights and scenes (scene just to update the status and remove the "device not responding" banner). Colors are not supported, because
It will work with Vera bridged on openLuup, but HA-Bridge accessing the Vera's device directly (there's a special variable, look at the logs).
Very beta, feedback appreciated as always 🙂
I hope they'll add a way to query the status via voice soon 😉
-
The latest/working version of OpenSprinkler for openLuup, is it the one from @therealdb ?
-
Anyone using the Yamaha plugin currently? I installed it from the AltAppStore and put in the IP in the Attribute field but it never connects to it. This was working fine on the Vera side.
altUI
-
Is there any chance of @amg0 becoming an active member, do you think?
He appears to be not responding on GitHub (I opened my licensing query a month back)
There are also some challenges around how things like thermostats behave in their display which would be great if we could get them fixed. Well beyond my capability
C
-
He has reached out to me a couple of months ago about his credential here. He seems to have tuned down his activity to a minimum and I have just submitted a pull request for ALTUI on github. Generally speaking he seems to be willing to take in PRs but is not going to invest himself in larger projects. He was not very active in the old place either.
If there are things you need to get done, I can give it a shot but I am very much a newb in javascript.
-
@rafale77 thanks chap. Seems a little unfair (to you!)
I guess there are two issues (so far)
Thermostats don't work properly under Altui. Or at least mine doesn't There's no way of adjusting the set point in the web interface. Works fine in Homewave but....
The other is the licencing issue previously mentioned. A minor peeve.
But this raises some concern that if the UI is not maintained, in a couple of years, how functional will it be?
C
-
I would not call it "unmaintained", @amg0 has just recently taken my localcdn updates and has upgraded bootstrap. I can't help with the licensing unfortunately. Maybe @akbooer can. About the setpoint problem with the thermostat, can you provide more details? I don't think this would be an ALTUI issue and more of a vera device file issue since that's what is controlling it. I have personally wrote a plugin to control my thermostat which integrates door/motion sensors/vents (The US mostly use forced air HVAC) and calculates a virtual home temperature. (Kind of like ecobee but much better as it shuts off vents for rooms with open windows, ignores and shuts off unoccupied rooms etc...)... and my thermostat works. What model and what errors/issues are you seeing?
-
Maybe 'unmaintained' is unfair, not my intention. But if support has stopped (no response to a follow up on my licensing query) and the other issue raiser in 2018 was directed to Vera forum, not sure what's going to happen.
Ref the Thermostat, I guess it may be the device file since it doesn't 'work' in the console either. This is all I get in AltUI
So there's no way to adjust the set point.
C
-
Can you show me the device attributes? And action screen? What are you expecting to be able to do? Only change setpoints (heat/cool?) do you need to change also mode?
-
Here you are
I guess all I expect to change (and display) is the current set point. Heat on and off would be cool as well.
As far as I am aware there is only one (functional) setpoint. Although I suspect it has rather more than that. And only one mode (heat) although again I suspect it has more of them as well. Which is probably a failure in the file attributed to the device?
I can see it has in its variables two CurrentSetpoints. One is probably my fault trying to control it. But it also has Energymodes and Fanspeed.
It's really a very simple on / off stat
Tangentially this feels like the kind of issue that we should be able to provide a quick and easy solution to the average user. You know I'm going to be happy to ask and fire commands, but for basic users, it's a simple device and it's effectively un-usable.
I use it with Homewave (not exactly simple) and Alexa / HA Bridge (not quite user hostile, but verging on it)
So I don't need this functionality, it just feels like quite a big miss.C
-
ouch... this is through the z-way bridge. Need @akbooer here. It looks like this device was not recognized by the z-way bridge as a thermostat. I am curious as to what command class it is showing on z-way. Can you please take a look at the expertUI on z-way and show what command classes it is presenting on the interview screen?
-
-
I just looked at the z-way bridge code... and it shows that the bridge should create a thermostat device instead of a combo device.
You may have installed this on an older version of the z-way bridge.
Solution:
Update the z-way-bridge if it isn't already the latest version, delete the child device and reload luup.
See what device file you get. -
So this is the Z-way plugin on AltUI?
Showing 20.7.14
C
-
-
OK. If I delete the child device, am I going to lose all my automations and actions around it?
Sorry to be a PITA....
C
-
Not on openLuup. That was a vera "feature" luckily openLuup didn't reproduce. Upon luup reload, the device will be recreated and no automation should be broken. Make sure you only delete the thermostat device.
The device created should show you the thermostat temperature and at least one setpoint.
-
OK
So used the App store to select Github.development
Plugins now shows 21.1.19
Deleted the device that I thought was the Thermostat (i.e. the one I showed you earlier)
Reloaded Luup and I have a device that was recreated in my Z-Way-nnnnnn room
But...Nothing appears to have changed:
I assume I've done something dumb
C
-
Nope... there is something missing: the bridge has linked the variables but did not use the right device files.
Go into attributes and change the device json from ComboDevice1.json to D_HeaterStelpro.json and the device file to D_Heater1.xmlI think that you have a heater rather than a thermostat...
-
Heheh. Not sure why it would be considered a heater but....
Not much of an improvement... (I reloaded Luup)
C
-
hmm - hmmm you have the device files reversed the json file needs to be in the json field... also make sure that these files do exist in your openluup installation. They should come from the vera.
I read the manual for your thermostat and it is indeed a heat only thermostat which for vera is a heater control device... The difference is that it only has one setpoint instead of 2 and terminologies are all around heating.
-
See it was only a matter of time before I did something stupid
Thanks for all this. Sure when I originally mentioned this it was a feature of AltUI.
Looks much better now. thanks!
C
-
As a supplementary question, now I have a Heat / Off switch.
Can I make this actually switch my boiler control on? This would neatly solve an issue I've been considering with TRVs.
Currently altering it from 'Off' to 'Heat' does nothing and does not appear to alter the value of the ModeTarget variable which is reflected in the logs.
I also need to chase something down I suspect in HA Bridge as I've managed to re-create another CurrentSetpoint
C
