This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm that you accept these cookies being set.

[OLD] LogicMachine firmware 2017.06
#1
RC3 is ready for testing, this is a bug-fix releases with minor changes:

1. Apps installation issue fixed
2. Object log now works properly when log policy is set to "all" and bus sniffer is disabled

LM2 IMX: https://dl.openrb.com/lm-17/lm2i-20170601.img
LM3 V1 (4 x RS-485): https://dl.openrb.com/lm-17/lm3v1-20170601.img
LM3 V2 (3 x RS-485 and 1 x RS-232): https://dl.openrb.com/lm-17/lm3v2-20170601.img
LM4: https://dl.openrb.com/lm-17/lm4-20170601.img
LM5 lite: https://dl.openrb.com/lm-17/lm5m3-20170601.img
LM5 lite with extensions: https://dl.openrb.com/lm-17/lm5m3ex-20170601.img
LM5 4 DIN units: https://dl.openrb.com/lm-17/lm5m4-20170601.img
LM Ambient: https://dl.openrb.com/lm-17/lmwall-20170601.img
LM Reactor Lite: https://dl.openrb.com/lm-17/rctl-20170601.img
LM Reactor V1: https://dl.openrb.com/lm-17/reactor-20170601.img
LM Reactor V2: https://dl.openrb.com/lm-17/reactorv2-20170601.img
LM Reactor V3: https://dl.openrb.com/lm-17/reactorv3-20170601.img

Extra packages: https://dl.openrb.com/lm-17/pkg


LM5 Power devices
Note: if upgrade does not work, run this script once:
https://gist.github.com/jsopenrb/4ba040d...dbc6b74447

LM5 lite: https://dl.openrb.com/lm-17-imx6/lm5m3-20170601.img
LM5 lite with extensions: https://dl.openrb.com/lm-17-imx6/lm5m3ex-20170601.img
LM5 4 DIN units: https://dl.openrb.com/lm-17-imx6/lm5m4-20170601.img

Extra packages: https://dl.openrb.com/lm-17-imx6/pkg


Load balancer:
https://dl.openrb.com/lm-17/lb-20170601.img

Old LM2:
https://dl.openrb.com/lm-17/lm2-at91-20170601.img
#2
Unfortunately, almost whole was good after upgrade but unfortunately now I can't reach my LM Load BalancerSad
#3
Can you check if it's reachable via SSH? If yes, then send me remote access to port 22 via PM.
#4
(01.06.2017, 13:47)admin Wrote: Can you check if it's reachable via SSH? If yes, then send me remote access to port 22 via PM.

How can I check this? Via Total Commander?
#5
Use putty or kitty app, can you even ping the device?
#6
No, unfortunately I can't ping and also I can't reach it via Putty(I have tried also with working LM4 and on it is ok). I've tried also reboot a device and still the same.
#7
You can try running Ubuntu live USB, then I can connect through TeamViewer there. If I remember correctly you need to press F12 or Esc during start-up to select boot device.
#8
(01.06.2017, 15:02)admin Wrote: You can try running Ubuntu live USB, then I can connect through TeamViewer there. If I remember correctly you need to press F12 or Esc during start-up to select boot device.

which kind of ubuntu? Can be from here, for desktop?
https://www.ubuntu.com/download
#9
Try 17.04 i386 version, here's a guide on how to run it without installation: https://www.ubuntu.com/download/desktop/...ou-install
#10
Ok so today I will download this file and prepare ubuntu usb and if this would be not a problem tomorrow morning when I will on the installation I will contact with you. Thanks for upgrade and thanks for helpWink
#11
When I connected the monitor to Load Balancer I have such info:
"Booting 'OS'
#12
This means that it's trying to boot, but if the main filesystem got damaged you won't see any messages. Have you tried running live USB?
#13
I've upgraded to the version 20170601. Sonos app works normally, the same Mosaic and the other plugins/apps.
Many thanks to Edgars and Erwin which they have fixed remotely the Sonos app on my LM4! :-)
#14
Hi, here are my findings so far (one day) after restoring my backup to a fresh LM4 running RC3:
  1. Scheduler events are doubled in most (not all) my schedulers
  2. In visualisation, the icon that gets status from a byte object that I use to display my AC status (which is driven by multiple icons per status value i.e. off_icon when value=0, on_icon when value=1 etc) is displayed correctly within the editor, but it is vanished when I view the visualisation page directly from browser or from iPhone, iPads etc.
  3. I get too the "Mosaic 2.0 error: cannot open /data/apps/store/data/mosaic20/lua/mqtt_library.lua: No such file or directory" any 5 minutes or so
  4. There are logs created by an "unknown" script (probably running hidden for the Alexa integration) each time you saying a command to Alexa (probably due to RC3 debuging?)
  5. Alexa integration is working ok, but I cannot find how to expose also my shutter objects (there are options only for lights, locks and thermostats)

Also, is there a way now in RC3 to enable or disable a schedule from within a script?
Thanks
#15
1. Schedulers conversion procedure for new HW:
If an old event is set to run on both weekdays and holidays two events will be created: one that runs on weekdays, another that runs on all days and is set to run only on holidays.

2. Can you provide a backup to reproduce this issue?

3., 4., 5. This should be reported in Application Store section Smile

Scheduler API is not yet included.
#16
Hi,

Whether I use scripting or object tab interface. Create an object, that is 2 byte float or 2 byte temperature. Now try to set the value to 100 either in script or set parameter, you see 100.00.
Now set the value to 101. Its new value 100.96. Any value above 100 will always round down to 0.96

Thanks,

Roger
#17
This data type has limited precision and it gets worse for large values. For values around 100 precision is 0.08. So you can either get 100.96 or 101.04, but not 101.
#18
(12.06.2017, 06:16)admin Wrote: This data type has limited precision and it gets worse for large values. For values around 100 precision is 0.08. So you can either get 100.96 or 101.04, but not 101.

That kind of sucks.  I have created a driver talking over IP which receives a temperature.  when I have to update the ip device, I would have to round the value up the object value before sending.

Hi,

Since updating to RC3, the system log is repeating itself with the following, is this really necessary?

Jun 14 05:11:08 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 14 04:41:06 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 14 04:11:06 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 14 03:41:04 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 14 03:11:03 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 14 02:41:02 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 14 02:11:00 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 14 01:41:00 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 14 01:10:58 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 14 00:40:57 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 14 00:10:57 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 13 23:40:55 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 13 23:10:55 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 13 22:40:53 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 13 22:10:52 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 13 21:40:52 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 13 21:10:50 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 13 20:40:50 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 13 20:10:48 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 13 19:40:47 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 13 19:10:47 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 13 18:40:45 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 13 18:10:44 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 13 17:40:43 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 13 17:10:41 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 13 16:40:41 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 13 16:10:39 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 13 15:40:38 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 13 15:10:37 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 13 14:40:35 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 13 14:10:35 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 13 13:40:33 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 13 13:10:32 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 13 12:40:32 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 13 12:10:29 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 13 11:40:28 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 13 11:10:27 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 13 10:40:26 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 13 10:10:26 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 13 09:40:24 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 13 09:10:23 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 13 08:40:22 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 13 08:10:20 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 13 07:40:20 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 13 07:10:18 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 13 06:40:17 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 13 06:10:16 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 13 05:40:14 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 13 05:10:14 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4
Jun 13 04:40:12 LogicMachine user.notice dhcp: setting dns servers: 8.8.8.8 8.8.4.4


Thanks,

Roger
#19
Not needed, but there's no harm in it. These logs are stored in RAM and are not written to flash.
#20
(14.06.2017, 06:27)admin Wrote: Not needed, but there's no harm in it. These logs are stored in RAM and are not written to flash.

ok thanks


Forum Jump: