Code: Select all
opkg list-installed > opkg_list.txt
Moderators: marcelr, TheHogNL, Toonz
Code: Select all
opkg list-installed > opkg_list.txt
Code: Select all
import QtQuick 1.1
import qb.components 1.0
import qb.base 1.0
import BxtClient 1.0
App {
id: boilerStatus
//Do we need a property declaration here
function retrieveBoilerData() {
var msg = bxtFactory.newBxtMessage(BxtMessage.ACTION_INVOKE, p.thermstatUuid, "specific1", "BoilerChPressure");
// Timeout is one second more than the timeout in happ_scsync
bxtClient.doAsyncBxtRequest(msg, retrieveBoilerData, 16);
console.log("BoilerStatus requested");
return BoilerChPressure; //Or for debug just whatever it returns, if it returns something
}
Timer {
id: datetimeTimer
interval: 60000 // update every minute
triggeredOnStart: true
running: true
repeat: true
onTriggered: retrieveBoilerData()
console.log("BoilerStatus Updated");
}
}
reverse engineering with notepad ++Ierlandfan wrote:How to know wich calls are suported in bxtfactory?
Code: Select all
ps | grep chron
Code: Select all
1091 root 2616 S /usr/sbin/chronyd -r
3210 root 2964 S grep chron
Code: Select all
1208 root 2616 S /usr/sbin/chronyd -r
25697 root 2960 S grep chron
Code: Select all
#server time.quby.nl minpoll 8
server www.nist.gov minpoll 8
#keyfile /etc/chrony/chrony.keys
#commandkey 1
driftfile /var/lib/chrony/chrony.drift
#log tracking measurements statistics
logdir /var/log/chrony
dumponexit
dumpdir /var/lib/chrony
local stratum 10
allow 10/8
allow 192.168/16
allow 172.16/12
# Generate syslog messages if large offsets occur (> x secs)
logchange 10
# Specify that the real time clock keeps UTC not local time
rtconutc
#rtcfile /var/lib/chrony/chrony.rtc
# Step system clock if large correction is needed (> x secs within y clkupdates)
makestep 1000 100
# Trim the system clock on boot-up. (> x secs from host)
#initstepslew 30 time.quby.nl
initstepslew 30 www.nist.gov
# Stop bad estimates upsetting machine clock
maxupdateskew 100.0