After update of Jigsaw into 4.8.5 I have troubles with blinds managed throw KNX. Aditionally is not possible to upgrade linux and knx interface. Both show need to upgrade and looks they are updating when run the process but still requesting to be updated.

Hey,

Yesterday we had reports that some of the buttons in the ventilation panel were not working. Turns out that some of them have changed the control type to lable after the server update. The template is my old vallox template that i made few years back, all the servers that are running on older version have it still set to toggle button. So it must have been the server update that changed it.

Good news is that i havent had any crashes with the latest betas,

Bad news is that i have to change the buttons control type for about 200+ apartments now. And adding a column or copying and pasting a node to it still takes up to a minute, so the server CPU load goes up to 30-50%. Making panels with a lot of nodes takes more time.

Just a FYI whoever is messing with the beta updates, that some changes may have happened to your configuration.

Best regards.

Dear,

I try many times but the 1 byte DPT 20.102 HVAC mode is not imported. 

The datapoint is visible and correctely identified in the first step, but in the final step the DPT not present

In finaly the value is not imported to the bOS.

Dear bOS Team,

Will the animation support will be in the next release or any time soon ?

Was anyone able to configure a bos program to play a radio station?

Also to play Spotify playlist?

Thanks, Ziv

Hello everyone,

Ever wondered that the e-mails in plain text sucks?

Well I've got tired, so I got news for you: it's possible to beautify the e-mails sent from bOS.

This was tested with my Gmail SMTP. If you add HTML/CSS tags, the e-mail sent will understand those tags.

On my e-mail body I've added something like:

And the result on my inbox was:

Tada!!!

Use it! It's cooler than plain text.

Best regards

Hi people,

May I ask a little help about counter log?

I have a power sensor on an electric board. On ETS, I get an Instantaneous Power object (2 bytes), which comes in kW format. Like, if the house is consuming 1200W, I get 1,2 value on ETS, if it's consuming 250W, I get 0,25 value, and so on. I have the correct instant values showing on visualization.

I've tried to create counter logs, to get an approximate daily consumption, etc. The problem is that the values on the counter log don't make any sense.

For example, if the house is consuming constant 250W during 24hour, I should get 6 kWh by the end of the day, but the values don't make sense. On one day, it showed something like 138kWh on one day, which is impossible. I deleted all data now.

Either I'm configuring all wrong the counter log, or there's something I'm missing.

Thanks for any help

Hi,

I have several z-wave devices from different manufacturers and I don't understand why in some I don't see any parameters to configure them.
I have tried to send them manually and it says "index outside the limits of the matrix"
I am doing something wrong?
Two of the devices that happen to them are Fibaro RGBW Controller and Qubino Flush RGBW Dimmer.
I would greatly appreciate a solution, at least I can send the parameters manually.
regards

Hello!

Here we have a short tutorial on how to integrate bOS and TASKER using new bOS’ RPC service.

bOS offers a JSON RPC Service for integration with Tasker, IFTTT and other services.

This tutorial will show bOS RPC service interacting with TASKER on Android in a simple task, but the important thing here is to understand how to set-up the RPC service so you can do more complex integrations.

RPC service on the new bOS offers HTTP basic authentication with username and password.

In this example, we'll be using Tasker to turn a Z-Wave Socket off.

Of course, this can be done easily within bOS Client app, but this is just for demo purposes. You can change and adapt the task to your needs, for example, "If my phone battery is lower than 80%, turn the socket on", or "If I’ve reached my house, turn front door light on". The possibilities are endless.

Step 1: Configure your RPC service

• In bOS Configurator, under API, enable RPC and define your Username and Password:

Step 2: Find your Device Path

• In this example, the Info tab from the Z-Wave socket device will show us the path: Devices\Z-Wave\Socket\Basic

Now we need to form the JSON body to POST on TASKER.

The Path we have is: Devices\Z-Wave\Socket\Basic

We need to double the backslashes on the Path to form the JSON body to POST on TASKER service, so now we have: Devices\\Z-Wave\\Socket\\Basic

The simple SetValue body post looks something like this:

{"objectName":"INSERT PATH HERE","valueName":"Value","value":"true"} where "value":"true" is to turn the value to true or 1. You can change to false or 0 or look for other RPC examples.

For our valueName, we have “State”:

To turn the Socket off, our body post is:

{"objectName":"Devices\\Z-Wave\\Socket\\Basic","valueName":"State","value":"false"}

Step 3: Tasker

• Create a new task and include the “HTTP Post” action:
  

• In your HTTP Post:
  Server:Port
  https://RPCUserName:RPCPassword@your_ip_address_or_dynamic_dns_address/API/RPC/SetValue
  
  in our example: https://RPC:RPCCOLIBRI@ip_address_or_dynamic_dns_address/API/RPC/SetValue
  
  Data / File (here we include our body post)
  {"objectName":"Devices\\Z-Wave\\Socket\\Basic","valueName":"State","value":"false"}
  
  Content Type
  application/json; charset=utf-8
  
  Trust Any Certificate:
  Yes

Done! Now every time we run this task our Socket will turn off.

This is a simple example for demo purposes, but with more complex commands you can do whatever you want... call scenes, set other values, etc.

To call a RPC Service a HTTP POST call must be preformed with data content-type = "application/json";

Service offers the following commands

http://localhost:81/SetValue

POST data example (Turn ON a light): {"objectName":"Devices\\EIB\\Light 1","valueName":"Value","value":"true"}

http://localhost:81/GetValue

POST data example (Get light status): {"objectName":"Devices\\EIB\\Light 1","valueName":"Value"}

http://localhost:81/CallFunction

POST data example (Send alert to user):

{"objectName":"Building\\General\\Users\\User","functionName":"SendAlert","value":["'Hello'"]}

I hope you’ve enjoyed the tutorial and please post here the examples and ideas you have using the new bOS’ RPC API.

I have a menu that is secured with the theme unlock pin. However, I would like to be able to change it without having to get into the BOS Configurator. Is it possible? 

If not, is there any other way to protect some info with a PIN/Paswword that I can change from the App? 

Regards,