for a simple logging of the old data regarding front door, you can create a message task with front door as a trigger, then send an event to the user so they will receive a event notification regarding the front door, also every value change is saved under events for past logging.
you mentioned you started having this errors 2-3 months ago? Do you remember if they started after you updated bOS ?
We tested RPC/IFTTT using webhooks to control devices in the office using the latest bOS beta version and everything checks out and everything is working here.
Looking trough the update notes for our betas, there weren't any changes done on the RPC service so the communication should be working normally.
You tested directly roomba/IFTTT and you get the same results?
Apple HomeKit is planned to be released in bOS, the development is well underway, but there's no ETA on the release date yet.
can you send us a screenshot of the program you use that causes the KNX to restart? We haven't noticed this issue so far and noone else reported it and exit function is used in many of our program tasks, without any KNX disconnects.
since one node receives multiple values, we need to ask which values is received in the trigger. You can use the scene function from the button as a trigger for the scenes and other tasks (1 press, scene 1, 2 press, scene 2...) or you can make a program task like you created..
integration of zigbee is well under development and will be released with the next version of bOS. Currently there is no ETA, but the driver itself is more or less finished.
for long string values some text does get cut, usually these event messages are short only for notifying the user of current events. However, we will add into our developing plan so we can create this wrapping text that will display the whole message.
checking the device's overview, is the status "ready" or is status notconfigured, or configuration? When dealing with battery operated devices, sometimes when including the device, repeat the inclusion pattern or try selecting Functions tab, select Refresh configuration and include again so you get status as Ready, and association groups visible.
When setting parameters, try selecting the parameter number, adding name and use Get function, wake up the device so bOS gets the default value in.
After that, try using Set to set/change the new parameter.
hope this helps.
great to hear you're making some progress with the visualisation.
You can create a program task that will set all the mode values to OK, and the reception can click that button once every room is cleaned (example).
You can create message task that will send notification/email/alert to the reception if they don't have the client open all the time, notifying them of any room services.
we're currently working on fixing the grouping of multiple sonos speakers as well as adding features for doorbell option when using sonos. We should see these fixes soon.
Customer support service by UserEcho