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.
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.
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.
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.
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:
lastEventType
lastEventCategory
lastEventTime
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?
you just need to declare a Java class with an ArrayList, put in the elements and then finally use gson.toJson() to build the JSON strong. Let me know if you need help, I could provide you some code.
I found out 2 important things with regards to alarms
usually you donât get a Push/SMS from them when an alarm was detected and could be resolved by calling the alarm contact(s). On demand this could be requested, call the hotline and set it up for you (AFAIK this is not possible in the App nor the Web UI)
The alarm is shown in the event log of the App, same as activate/deactivate. However, using the vsure command line utility retrieving the event log I donât see those events just open/close of the contacts. Therefor there must be a 2nd API call to retrieve the full list, which would then allow to extract those events and map them to a channel.
you just need to declare a Java class with an ArrayList, put in the elements and then finally use gson.toJson() to build the JSON strong. Let me know if you need help, I could provide you some code.
I was more thinking on how to represent it in the things modelling, but I will use a String representation for that channel. Then Iâll implement the following channels:
lastEventType - String
lastEventCategory -String
lastEventTime - DateTime
eventLog - String (JSON array of last x events where x is either hardcoded or a new config parameter)