-
....but not what you think, probably.
I doubt there's an answer here to this, and it's about Iphone locator (sorry!)
Hopefully the question is, at least, slightly interesting.
Polling on the phone is currently set to 5 minutes and IPhone locator appears to update every 5 minutes as I also get an update in the OpenLuup log every 5 minutes.
The 'problem' is that the Iphone locator (and therefore any conditions based upon a change in value) are happening 4 minutes and some seconds after the phone polls and updates its position. So effectively the phone is moving for nearly 10 minutes before any notification takes place. Which is a bit slow for my desired application.
As an example:
2022-05-05 17:27:08.244 luup.variable_set:: 55.urn:upnp-org:serviceId:IPhoneLocator1.MsgText2 was: 28.35 Km @ 0.00 Km/h on 2022-05-05 17:17 now: 28.35 Km @ 0.00 Km/h on 2022-05-05 17:22 #hooks:0 2022-05-05 17:32:12.340 luup.variable_set:: 55.urn:upnp-org:serviceId:IPhoneLocator1.MsgText2 was: 28.35 Km @ 0.00 Km/h on 2022-05-05 17:22 now: 27.77 Km @ 6.92 Km/h on 2022-05-05 17:27 #hooks:0Where you can see that the phone must have updated its location between 17:27:08.244 and 17:28:00.000
Anyone got an bright ideas how I can reduce the discrepency?
Cheers!
C
-
I am running HA, MSR and ZWavejs2MQTT on a Synology NAS (Docker). When the NAS reboots (after a power outage for example), I see errors (under Status), yellow triangles in front of Rule Sets and yellow bars in front of Global Expressions. See images below.
To give you some context, in some cases MSR writes statuses to HA Helpers. In order cases, MSR just can't seem to find the referenced entities.
Also, note the bevahior under Global Expressions (images below). The one with the yellow bar says, "Invalid reference to member attributes of null". If I click the Try this expression button, the Last value will refresh accordingly and the yellow bar disappears.
Interestingly, everything seems to be working like it should even if I don't do anything. Which is weird.
This behaviour does not happen when the MSR container is stopped and restarted manually.
Anybody experienced this? Thanks
Errors showing under Status
16581e96-9f7d-4107-a591-6c0755349a73-image.pngYellow triangles showing under Rule Sets
84b7c20d-a325-4101-b456-5aa4814a798f-image.pngYellow bar showing under Global Expressions
67f150eb-4c18-43ff-bd3b-b5bd181bc933-image.png 1a648901-450a-4b15-b558-c73a5b737b56-image.png -
-
Hi @toggledbits,
i tried the ezmqtt today, i have some issues most likely that i'm doing something wrong.
i have on my ezlo hub 3 switches, 1 dimmer and 1 motion sensor
i can control the dimmer via ezmqtt/set/device/<device-id>/item/<item-name>
but i can't control the switches.i receive on ezmqtt/tele/device/61e8937e124c35129921171d/item/switch payload true or false depending on the state of the switch, but when i send on ezmqtt/set/device/61e8937e124c35129921171d/item/switch payload true or false nothing happens, its the same for all switches.
what i'm doing wrong?
Cheers
-
Hi
Hope I am allowed to post this here?
I can't figure out how to correctly show device battery levels from the Vera Plus via MSR in Granfana.
These devices don't have the battery levels that its displaying in Granfana. I've tried messing about with various settings like units and decimals but its still not right.
-
Everyone,
As a side project, building on some deep innards borrowed from Reactor, I have released two new projects (unrelated to Reactor). Both are published on npmjs (for installation via npm), and on GitHub.
ezmqtt — a standalone app that acts as a conduit between Ezlo hubs and MQTT. It's published on npmjs.com and on Github. node-red-contrib-ezlo — Node-RED nodes (installable package) for Ezlo hubs. It's published in the Node-RED Nodes Library, at npmjs.com, and on GithubWhy? Because choices are a good thing.
There are docker containers available for ezmqtt, but I haven't finished the work there, so they may not be quite ready for prime time; but feel free to test/play if you want.
-
I know we talked about this a while back, but wondered if anyone has any ideas at all? It's still a 5-10 second pause between initiating a TTS event and getting the output.
This is using either a direct Luup call or the most excellent VeraTTS plug in.
I noticed that executing from reactor using the little 'run' icon, I'm getting an occasional '0 timeout undefined' error (even though the event eventually happens
Any thoughts, anyone?
C
-
Full disclosure.
I am from [HundredGraphs.com](link url). We are the data aggregation service for smart homes. So far we have plugins for Vera and SmartThings and we are looking to move in onto new hubs.
What would you be interested in?
Vera Energy graph
hg energy.jpg -
Years after having installed and implemented the homekit integration to the vera through the verahomekitbridge which later became the homebridge:
rafale77/VeraHomeKitBridge rafale77/VeraHomeKitBridgeContribute to rafale77/VeraHomeKitBridge development by creating an account on GitHub.
(I just implemented a few updates I discovered were outdated for the garage door which were meant for older vera firmwares)
I just recently came to the realization that I can do a lot more with Hey Siri with devices I already own. I have therefore a renewed interest and have been configuring my homekit installation to match my alexa capability. Unfortunately a lot of things are still pretty far behind in terms of integration but... I found homebridge and all its plugins. I just wanted to share the alternative I pursued: Home Assistant. I implemented the Homekit component for it and have been able to bridge Sonos and Harmony while my openLuup devices are still bridged into homekit through the VeraHomekitBridge. If you already have home assistant, homebridge is potentially redundant...
The probability of taking down alexa and its cloud dependency completely is increasing... -
For those who are familiar with node-red, I found interesting news from the Home Assistant site that the openzwave project has gone stale and that they have shifted their focus on integrating zwave-js! It spiked my interest in spite of currently not seeing any need since z-way has been rock solid in combination with openluup but it might be of interest for others that there is yet another open source z-wave platform, this time written in javascript and running on a nodejs server... yes the same platform @toggledbits has chosen for "super reactor". I am already running a number of smaller nodejs application in my setup so it isn't quite new and yes there is also mqtt and node red bindings coming with it.
-
Vera Alexa TTS slowwwww (still)
-
I know we talked about this a while back, but wondered if anyone has any ideas at all? It's still a 5-10 second pause between initiating a TTS event and getting the output.
This is using either a direct Luup call or the most excellent VeraTTS plug in.
I noticed that executing from reactor using the little 'run' icon, I'm getting an occasional '0 timeout undefined' error (even though the event eventually happens
Any thoughts, anyone?
C
-
I'd just love to know how you got the Vera>Alexa TTS to work. My AMZ account has 2FA enabled (because why wouldn't you use 2FA everywhere...?) and my VeraSecure is on 7.31 (the 7.32 beta just still seems flakey from what I keep reading) and these two things together seem to be the death knoll for
therealdb
Vera plugin. -
Pass. I don't have 2FA because (without getting into a huge argument about relative risks) why would I
And I don't use Vera because, again, why would I
And both TTS and voice control work absolutely marvellously apart from this slightly irritating 5-10 sec delay
C
-
I believe I'm confused. I thought the topic was Vera>Alexa TTS and I was inquiring how you got it to work, that's all. If you're not using Vera... guess that's where my confusion about Vera>Alexa TTS stems from.
Re 2FA, to each his own. That's not the topic.
-
Ahh, well that's a fair call. The plugin is called Vera Alexa, even though I run it on OpenLuup......
Clearer?
C
-
Yep, clear.
-
@gwp1
I have tts working in vera and openluup with 2FA enabled and I auto update the cookie. Occasionally i have to update by hand but that's rare. If you want help just ask. -
@catmanv2 I have no speed issues, maybe your system is overloaded?
-
@elcid said in Vera Alexa TTS slowwwww (still):
@catmanv2 I have no speed issues, maybe your system is overloaded?
It seems unlikely
I'm running OpenLuup on an Intel NUC
top - 18:09:57 up 126 days, 11:16, 1 user, load average: 0.10, 0.11, 0.09
Everything else is nice and snappy (with the exception of the door sensors which are utter rubbish, but it's an old issue with these devices)
Even if I tell Alexa to turn on a device via HA Bridge, the command is typically executed before I get the 'OK' from Alexa.
The only exception is when I have (typically Reactor, but the delay is apparent in direct Luup calls) dealing with a response. If I have a voice command that triggers Speech > device activation, the activation waits for (up to) 10 seconds for the speech to complete, then the device activation is immediate. If I change the order to Device activation > Speech the devices activate immediately, then there's a (up to) 10 second pause for the spoken response (Not the "OK" that's immediate)
Where are you based @Elcid ?
C
-
Sounds weird, but look at logs. I’ve not touched it since ages, but I could dedicate some time during the weekends.
I have 2fa enabled and I’m using oath tool to automatically renew the cookie. I’ve not touched it since years. I’ve moved away from the Plugin because I’m using a custom udp server to offload the Vera, but it’s running the same sh script anyway.
-
-
@elcid so it's not country specific then!
C
-
@therealdb does the Vera Alexa plugin do anything self-reflexive, like make (or cause to be made by something else) an HTTP request to the Vera/openLuup, or ask that it play a file on the Vera/openLuup system?
I had an issue with getting the Sonos plugin running on openLuup.... there was a strange delay, not unlike the situation described here. It turned out that the Sonos plugin was, in its HTTP request handler, asking the Sonos to play a file and waiting for the Sonos to ack that it had started it, but the Sonos couldn't play the file because (!) openLuup's web server is single-threaded and can only process one request at a time, and it was in a request already. So until the originating request timed out, the Sonos player couldn't get the media file it needed from openLuup, but the original request was waiting for the Sonos to signal it was playing it (fortunately it had a timeout).
MSR performs actions by making HTTP requests to openLuup...
-
@toggledbits it’s not doing http calls, but it’s waiting for a bash command to complete. I’m not sure it this is correlated, but I’ll take a look.