Thanks for the work being put into this binding - it really works well!
One question. When using the Verisure app there is a timestamp associated with door/window sensors. Is that something that has been discussed to be included in the binding?
Thanks for the work being put into this binding - it really works well!
One question. When using the Verisure app there is a timestamp associated with door/window sensors. Is that something that has been discussed to be included in the binding?
Thanks for the work being put into this binding - it really works well!
Thanks Christian! Really appreciated!
That is something that I can add for sure, stay tuned!
New jar-file.
NOTE: If you’re already running the binding and the DoorWindow thing is auto-discovered then you have to delete and re-discover the thing in Paper UI to get the new channel.
[00:15:20] openhabian@openhab:/usr/share/openhab2/addons$ md5sum org.openhab.binding.verisure-3.0.0-SNAPSHOT.jar
ebdb583400d1ec57565a693c7c88469a org.openhab.binding.verisure-3.0.0-SNAPSHOT.jar
Wow, that was quick! I will give it a try ASAP!
Not sure if I’, doing something wrong but I couldn’t get the alarm state change timestamp to work. Do you know if that channel has been tested? FYI, I have only tested it using the 2.5 snapshot from dec 5th. Maybe it works on the 2.5.0 final or the new 3.0.0 snapshot!?
The new timestamp work just fine including the alarm timestamp when using the latest jar. Great work, thanks!
One thing that I don’t understand is that when testing, the timestamp from the alarm is presented in one format (2019-12-25T13:47:53+01:00) and the new timestamp from the door/window-sensors in a different format (2019-12-25 13:51). It looks like this in the basic UI and I haven’t done any formatting of the items/strings.
The README was erronously showing all timestamps as being of String type but they are defined as DateTime type in the things definition file.
If you change your timestamp items types to DateTime and use the following formatting:
DateTime SmartLockLastUpdated "SmartLock Last Updated [%1$tY-%1$tm-%1$td %1$tR]"
you will hopefully get consistent formatting.
This page is a good source for different DateTime formatting options.
Hi Jan,
While we are on the topic of the README…
The broadbandConnection
describes the connected
channel to get the connection status (as does the thing-types.xml), but the example later on defines a status
channel.
And I would like to suggest one tiny addition to the README: you could mention the exact Karaf command to set the DEBUG log level and add a reference to the Karaf documentation.
Hi Jan,
On the topic of the README…
The broadbandConnection
describes the connected
channel to get the connection status (as does the thing-types.xml), but the example later on defines a status
channel.
And I would like to suggest one small addition to the README: you could mention the exact Karaf command to set the DEBUG log level.
Thanks for the comments, I’ll do another revision of the README!
I’ve seen similar error since I upgraded to 2.5. Works fine approximately 24h. Anyone seeing the same? Solution?
New jar-file based on 2.5.x branch.
NOTE: Changes made to Broadband Connection status requires you to delete/re-discover thing again.
[22:00:15] openhabian@openhab:/usr/share/openhab2/addons$ md5sum org.openhab.binding.verisure-2.5.2-SNAPSHOT.jar
7cc0cc18430aef54dd2df7094bc58d23 org.openhab.binding.verisure-2.5.2-SNAPSHOT.jar
Would really appreciate If you could try this version, hopefully it is not so far away of getting this binding official!
New jar-file with better handling of failed logins and also use background threads for bridge/things initialization, previous post updated!
Updated again with some code enhancements.
Small error I noticed in the readme
temperature Number:Temperature This channel reports the current humidity->temperature in percentage.
New jar-file based on upcoming 2.5.4 release.
NOTE: Changes made to SmartPlug and channel hazardous that is now a Switch (On/Off) instead of a String.
[22:30:58] openhabian@openhab:/usr/share/openhab2/addons$ md5sum org.openhab.binding.verisure-2.5.4-SNAPSHOT.jar
a25d2697820771b743265219b87d316d org.openhab.binding.verisure-2.5.4-SNAPSHOT.jar
Take care out there!
Updated once more, previous post updated.
Hi @jannegpriv, I tried your binding and it works like charme
Wouldn’t it make sense to change the channels Location, Installation Site Name and Installation Site Id into thing properties rather than channels (for all things except the Account). Those values are static, relate to the Account and do create redundant information for all attached Things.
Is there no alarm status for the smoke detectors? temp and humidity are good, but the alarm status is essential. How to obtain the alarm source when the system reports an alarm?
Is there a way to query the history? (“Verlauf” in mypages)
I could contribute German translations if you are interested.
Works like a charm, absolutely love it
@jannegpriv I found a Python library, which also reads the event log:
Does that help to integrate that feature?
Is there a way to find out, which sensor raised the alarm?
Wouldn’t it make sense to change the channels Location, Installation Site Name and Installation Site Id into thing properties rather than channels (for all things except the Account). Those values are static, relate to the Account and do create redundant information for all attached Things.
We’ve had that discussion here, ao I will not comment it here too.
Is there no alarm status for the smoke detectors? temp and humidity are good, but the alarm status is essential. How to obtain the alarm source when the system reports an alarm?
Is there a way to find out, which sensor raised the alarm?
Actually I don’t know, there is no obvious query that I’ve found for getting alarm status for a device. I think that it is implemented as a push notice to the Verisure App and not a part of the Web API.
Is there a way to query the history? (“Verlauf” in mypages)
Yes, there is an API query for the event log. I’m not really sure how to model it? It would be a new Thing called EventLog with channels like:
Then you would always get the latest event. But how do you model a list of events? You could have channels for last, secondLast, thirdLast but that it kind of ugly?