Activity for dmitry-kazakov
-
dmitry-kazakov posted a comment on a wiki page
Changes (16 February 2026) to the version 4.78: The package Generic_Undirected_Graph was added; The package Discrete_Integer_Set an instance of Generic_Discrete_Set with Integer was added; The Natural_Number_Range pattern was added to Parsers.Generic_Source.Patterns to match a number from a range of natural numbers; The Natural_Number_Range pattern was added to Parsers.Generic_Source.Patterns to match a number from a set of natural numbers; The maximum number of matches was added to the pattern Proceed...
-
Changes to the previous version: The Size functions were added to Strings_Edit.UTF8 to calculate the length of UTF-8 encoding of a code point or an array of; The package Strings_Edit.RFC_3897 was added to handle IP addresses v4 and v6 as well as IRI (Internationalized Resource Identifier). IRI is an extension of URI (Uniform Resource Identifier) and URL (Uniform Resource Locator) that supports Unicode.
-
Changes to the previous version: Recurring rational representations (1/3 = 0.(3)) were added to the package Strings_Edit.Unbounded_Rational_Edit; Bug fix in Strings_Edit.Unbounded_Unsigned_Edit caused by overflow for 16 base; Next_Prime was added to the package Unbounded_Unsigneds.Primes; The pattern Proceed was added to SNOBOL-like patterns; Some heuristics were added to improve performance of SNOBOL-like patterns.
-
Changes the previous version: The pattern NL_or_EOF was added to SNOBOL-like patterns; The package Parsers.Generic_Source.Patterns.Generic_Fields was added to match and accumulate a string array of delimited fields; The package Parsers.Generic_Source.Patterns.Generic_Floats was added to match and accumulate a float array; The package Parsers.Generic_Source.Patterns.Generic_Integers was added to match and accumulate an integer array; The package Parsers.String_Patterns was added as an instance of...
-
Changes the previous version: The Python high-level class support fixed to accommodate controlled types; The Python high-level class supports extension of Python types with Ada type extension; Binding to Get_Basic_Size were added to the package Py; Throw_NotImplementedError procedure was added to the package Py; Weak references support was added to the Py package.
-
Changes to the previous version: Function Compare to compare arrays of code points was added to the package Strings_Edit.UTF8; Function Image to convert a code points array to UTF-8 string was added to the package Strings_Edit.UTF8; Function Compare to compare arrays of code points using a code points mapping was added to the package Strings_Edit.UTF8.Maps; The package Strings_Edit.UTF8.Normalization was added to provide Unicode decompositions (NFD and NFKD), composition, normalization (NFC, NFKC)...
-
Changes to the previous version: The parsing example was upgraded from Ada 95 to Ada 2022. The changes include: Unicode identifiers; new (<subpool>) syntax;</subpool> Container aggregate; for expressions in container aggregate; declare expressions; delta aggregates; if expressions; case expressions; raise expressions; The package Parsers.Generic_Ada_Parser.Generic_Dot was added for writing Ada syntax trees in the DOT format of Graphviz; The package Parsers.Generic_Ada_Parser.Generic_Text_IO was added...
-
The new version provides an implementation of SNOBOL-like patterns. The patterns are integrated into the parsing framework. They can be constructed using expressions and then matched against the generic source. SNOBOL patterns are more powerful than regular expressions. A BNF grammar can be directly translated into pattern. Therefore they can be recursive. Features like immediate assignment and printout are fully supported. Patterns can extended by user-defined matching functions. Unicode is fully...
-
Changes to the version 3.8: Bug fix in Strings_Edit.UTF8.Maps.Is_Prefix; Unread was added to Strings_Edit.Streams to return the contents available to read; Get function was added to.Strings_Edit.UTF8.Maps.
-
The focus of this release is an implementation of arbitrary precision rational numbers. The difference to standard library Ada.Numerics.Big_Numbers.Big_Reals: No limits, except for the pool size; String edit packages representing a number in a usual form (with the specified accuracy) rather than as a numerator/denominator ratio; An equivalent of Ada.Numerics.Elementary_Functions with rational approximations; Simple continued fractions support. Changes to the previous version: The package Unbounded_Rationals...
-
Changes the version 4.73: Bug fix in Generic_Set.Insert which failed to set Inserted output correctly when the element is already in the set; Bug fix in Generic_Indefinite_Set.Insert, same as above; The package Generic_Lock_Free_FIFO was added. The package implements lock-free N-to-M FIFOs.
-
Changes the version 4.72: Topic list bug fix in the package GNAT.Sockets.MQTT (thanks to Xavier Grave); Minor performance improvements in Unbounded_Unsigneds: calculating log2, testing for power of two; OpenSSL MQTT test (components-connections_server.mqtt-test_mqtt) added; GNAT.Sockets.Server.Secure (GNUTLS) bug fixed. Activated is called at the end of handshaking; GNAT.Sockets.Server.OpenSSL bug fixed. Activated is called at the end of handshaking.
-
Changes to the previous version 4.70: The package Generic_FFT provides an implementation fast Fourier transform. The implementation supports pre-computed bit-reverse permutation and exponents to be used in multiple transformations of same vector length.
-
Changes to the previous version: The package Unbounded_Unsigneds implementing arbitrary precision unsigned arithmetic was added; The package Unbounded_Integers implementing arbitrary precision integer arithmetic was added; The package Unbounded_Unsigneds Primes implementing operations with prime numbers was added; The package Unbounded_Unsigneds.Montgomery implementing Montgomery domain operations was added; The package Unbounded_Unsigneds.Barrett implementing Barrett reduction was added; The package...
-
Changes the previous version 4.68: The procedure Compile was added to Python bindings in order to get a handle to the compiled module; The function Object_Super of the bindings is an equivalent of x.super().y. It returns the implementation of y from the x's parent class.
-
Changes to the version 3.31: Get_CSS_Name and Set_CSS_Name were added to Gtk.Missed; Gtk.Widget.Styles.CSS_Store changed to enumerate labels of Gtk_Notebook or its descendants; Since Gtk broke its CSS rules and the widget class cannot be used in the CSS style anymore and because unset widget names are defaulted to the class name but have no effect on the style name, Gtk.Widget.Styles.CSS_Store was changed to report only the widget name if different from the class names.
-
Changes to the version 4.8: Exporting styles fixed for the notebook titles.
-
Usually the issue is fixed by rebooting the cube. Turn the power off. Wait 15 seconds. Plug the cube back. When you start MAX! home automation application again it will find the cube. P.S. Note that cube discovery works only in the same LAN segment.
-
Updates. The supported version is "bookworm" and there is no need to specify a version. In the position 6, installation goes like this: sudo get install max-home-automation The sources.list line is this: deb [trusted=yes] http://www.dmitry-kazakov.de/distributions bookworm main To run the application from the console type max_home_automation It may happen that the cube is not discovered. First, reboot it. Power off, wait 5 seconds, the power it on.
-
Changes to the version 4.7: The device status polling continues even if some the cube lost configuration of some devices; Resilience in presence of malconfigured devices improved.
-
Changes to the version 4.67: Boolean types handling was added to the Python bindings; Python library search path for OSX fixed.
-
Changes to the version 4.6: MQTT .../status/.../json topics added; MQTT broker supports forceful publishing option on the settings page.
-
Changes to the version 4.66: Python bindings for OSX fixed.
-
Changes to the version 4.5: MQTT topics added for Initialize and Panel_Locked; MQTT topics added for Eco button.
-
Changes to the version 4.65: The ambiguities in the ODBC.API package implementation fixed.
-
Changes to the version 3.12: The package Generic_Complex_Measures was added to provide dimensioned complex values; The package Complex_Measures added as an instance of Generic_Complex_Measures with the type Float.
-
Changes to the version 4.64: Bug fix in HTTP server causing memory leaks in accumulated bodies when browser keeps connection on; Python bindings, backward compatibility to lower versions of Python 3, e.g. 3.8; Julia and Python bindings for OSX corrected.
-
Changes to the version 3.11: Added four new SI prefixes adopted by General Conference on Weights and Measures (CGPM) in November 2022.
-
Changes to the version 4.63: Persistent.Memory_Pools.Streams.Generic_Float_Waveform was added to provide waveform implementation; The implementations of B-trees was modified to support tagging buckets of the three. For this the packages Generic_B_Tree, Generic_Indefinite_B_Tree, Persistent.Memory_Pools.Streams.Generic_External_B_Tree, Persistent.Memory_Pools.Streams.Generic_External_Ptr_B_Tree provide subprograms Get_Tag and Set_Tag; The package Generic_B_Tree now has additional generic formal parameters...
-
Changes to the version 4.4: Python scripting based to the bindings provided by the Simple Components library.
-
Changes to the version 4.62: Code cleanup; SQL_Show and Close added to the package SQLite; Python dynamic bindings added.
-
Changes to the version 3.7: Minor bug fixes in Strings_Edit-ISO_8601.
-
Changes to the version 4.61: Pipe stream implementation added; GNAT 12.1 bugs worked around in several package, in particular, in GNAT.Sockets.Server; Bug fix in Generic_Set procedure Replace, parameter Updated unset; Bug fix in Tables.UTF8_Names procedure Replace, parameter Offset unset under circumstances.
-
Changes to the version 4.3: Adapted to GNAT 12.1 and Fedora 36.
-
Changes to the version 4.60: GNAT Studio Community 2021 bugs worked around; GTK 3.24.x support.
-
Changes (to the version 3.9: GNAT Studio Community 2021 bugs worked around; GTK 3.24.x support.
-
Changes to the version 4.1: GNAT Studio Community 2021 bugs worked around; GTK 3.24.x support.
-
Changes to the version 3.29: Compatibility functions Get_Iter_At_Location and Get_Iter_At_Position were added to the package Gtk.Missed. The functions provide backward compatibility to GTK 3.14 to 3.19 when the GTK interface was changed. The implementation works with both earlier and later versions.
-
Changes to the version 1.10: GNAT Studio Community 2021 bugs worked around; GTK 3.24.x support.
-
No, but you can use REST API or MQTT to communicate MAX! home automation from a mobile device. AFAIK there are dashboard apps for Android capable of doing so.
-
Eco switch signal is sent over the RF to all devices. The result can be seen only indirectly, when the state of a device change. E.g. MQTT topic cube-address/radiator thermostat/device-address/set temperature would report the ECO temperature as set for this thermostat. The state of the contact is reflected by the topic cube-address/shutter contact/device-address/status (open/close). So you get it directly. That depends on the message. Regarding the states of the devices, normally a device, e.g. a...
-
Let me know if you find any problems.
-
Changes to the version 4.59: Test IEEE 754 (test_ieee_754) adapted to the latest GNAT Ada compilers natively supporting Integer_128.
-
Wildcards fixed in 4.1
-
MQTT not working
-
Problem when moving/editing devices
-
Fixed in 4.1
-
Changes to the version 4.0: The bug "Unsuccessful attempt to rename device" fix while the device renaming. The fix also affected other operations involving storing the topology into the cube; MQTT wildcard subscription bug fixed.
-
When nothing changes then nothing gets published. You can change, for example, the thermostat's mode from automatic to manual. And see the change. As a rule a radiator thermostats never sends the actual temperature unless the valve position is changed. So there is little to publish. BTW, MQTT Explorer is much more comfortable to use than mosquitto. You can browse the available topics interactively etc. If you enable MQTT tracing you will see full exchange with the client in the trace. Trace into...
-
If you want to publish on the server you must enable MQTT publishing on the settings tab. You can furthermore specify the list of topics allowed for external publishing. Regarding wildcard topic subscriptions, that is a bug fixed in the incoming version 4.1.
-
On 2022-01-24 15:06, Meirion Williams wrote: [tickets:#1] Problem when moving/editing devices Status: open Milestone: 1.0 Created: Mon Jan 24, 2022 02:06 PM UTC by Meirion Williams Last Updated: Mon Jan 24, 2022 02:06 PM UTC Owner: nobody Hi there, I've got MHA v4.0 Having trouble getting my system tidied up. Moving and rename stats wasn't work, so I used the application to reset my cube. I added just one TRV and one room stat back using the add function. The room stat did not add correctly, and...
-
Changes to the version 3.29: Julia scripting support was added; Summer time zone setting corrected; Workarounds added for the time zone interval functions bugs in the Windows GLib port.
-
Changes to the version 4.58: The primitive operation Clear was added to GNAT.Sockets.Server.Connect; Julia bindings moved to the version 1.6.3; The functions Eval_char_array, Get_Safe_Restore, Load_File_String, Set_Safe_Restore were added to Julia bindings; Functions To_Julia and Value added to Julia bindings for Ada types Time and Day_Duration; To_Julia defined on tuples fixed when types of elements are not directly visible.
-
Changes to the version 3.28: Not saving temperature-timeout was fixed.
-
Changes to the version 4.57: Bug fix in the HTTP client. The bug affected systems with above average performance causing sporadic distortion of HTTP request headers.
-
Changes to the version 3.27: Switched to the latest version of Simple Components 4.58.
-
Changes to the version 3.26: Bug fix for large device configurations.
-
Changes to the version 4.55: The packages Persistent.Streams and Persistent.Streams.Dump were added to implement streams backed by a fail-safe file; ELV/e-Q3 MAX! cube client was changed to work around cube firmware problems.
-
Changes to the version 3.25: A work around cube firmware problems added to prevent cube crashes when sending configuration commands.
-
No, it works only with the devices supporting MAX! ELV/eQ-3 protocol. P.S. "Smart technology" is a meaningless term. It is always a concrete communication protocol. There is a great number of proprietary protocols as vendors run to monopolize the market presenting poorly designed and ill-thought products. It will take time and market until some usable open standards evolve.
-
Changes to the version 3.24: The HTTP server response for get-status-json content type changed to application/json; The HTTP get-status-json response was extended with the offset value for the wall thermostats; The cube reboot via HTTP rest API fixed.
-
OK, thanks for reporting and testing. I will make a new release at the weekend.
-
The two are different because the first is hexadecimal and the JSON one is decimal (and an array). Here is the second attempt: http://www.dmitry-kazakov.de/ada/max-home-automation_3.25_amd64.deb
-
Here it is: http://www.dmitry-kazakov.de/ada/max-home-automation_3.25_amd64.deb
-
That looks like a bug. Which platform you use? I would prepare a test version with a fix.
-
Sure. I will change that in the next version. If you need it earlier let me know which platform you have. Send me a mail and I will prepare you a beta version with these changes to download and test.
-
Changes to the version 3.23: Configuration saving bug fixed.
-
Changes to the version 3.22: 24:00 made allowed in the syntax of thermostat day schedule; Schedule upload optimization added for MQTT and HTTP REST API; Offset and airing temperature were added for wall-mounted thermostats.
-
Changes to the version 3.23: 24:00 made allowed in the syntax of thermostat day schedule; Schedule upload optimization added for MQTT and HTTP REST API; Offset and airing temperature were added for wall-mounted thermostats.
-
Changes to the version 4.54: GNAT.Sockets.Connection_State_Machine.ELV_MAX_Cube_Client changed to support wall-mounted thermostat offset and airing temperature.
-
I see. Try this version: http://www.dmitry-kazakov.de/ada/max_home_automation_3_23.tgz I also changed the order of uploading to wait for a confirmation from the cube. Maybe it will work better than sending all commands at once.
-
That is even simpler. I uploaded the beta version sources here: http://www.dmitry-kazakov.de/ada/max_home_automation_3_23.tgz
-
Debian aarch64? Because I am building for armhf, which is 32-bit. So you must have multiarch or what they call it now.
-
What system are you using, Windows? I can upload a preliminary version and post a download link if you want.
-
I still do not understand the problem with syntax. Use 23:59 everywhere you wanted to say 24:00. I will add support of 24:00 meaning 23:59 in the next version, if that is so annoying.
-
The time be less than 24:00. The last interval is continued to the end. So 23:30=18, 24:00=18 (or 23:30=18, 24:59) is same as only 23:30=18.
-
Are you sure? Can you log both cases to compare? The check is always there, it is the same stack that performs communication. A day schedule is sent only if changed against to the actual schedule as reported by the cube upon the handshake. For clean test, you must restart the application each time you try.
-
Right. In the trace when all days are sent, it is 14 s-commands in total (2 per day) all sent, but only three responses are received back: S:13,0,2b%0D%0A S:13,0,29%0D%0A S:14,0,28%0D%0A The rest is ignored. This is why you get the time-out. It is possible that the cube accepted them all. you can check that by restarting the MAX! home automation an then verifying the actual schedule. (The sends all schedules once upon connection) It is also he method to verify why the behavior might be different...
-
The message about skipping means that this part of the schedule is same as reported by the cube. The implementation tries to limit exchange when possible. You can activate tracing MAX! cube protocol commands and trace in a file. Then you can compare exchanges in both cases. The command sent to the cube starts with small 's'. The response from the cube starts with big 'S'. It looks like S:00,0,31. Here the second 0 means the command was accepted by the cube. 1 means it was rejected. You get timeout...
-
These are different. In the first case you try to update the whole week. Another does only one day. It seems that some changes for Tu to Su were accepted and ones for Mo timed out. Thermostats can get non-responsible time to time. Especially if you send too many commands too fast. Check the thermostat status on the overview panel. It must be OK, otherwise all commands will be ignored. Another potential problem is RF traffic limit. When you send many commands you run out of quota very quickly. Check...
-
Changes to the version 3.21: Configuration save/load dialog fixed; Added set-temperature graphs to the monitor pane; Added is- and set-temperature indicators to the monitor pane; Minor bug fixes.
-
Changes to the version 4.53: The packages Universally_Unique_Identifiers and Universally_Unique_Identifiers.Edit were added to support UUID; Reboot procedure was added to the package GNAT.Sockets.Connection_State_Machine.ELV_MAX_Cube_Client.
-
Changes to the version 3.20: The number of preset buttons was increased to 10; MAX! cube exchange tracing enabling/disabling added; File saving dialog adds file extension from the selected file filter; The cube reboot button added; Reboot topic added to the MQTT server; Reboot REST API added to the HTTP server; Reboot method was added to the Python module.
-
Changes (to the version 3.20: The number of preset buttons was increased to 10; MAX! cube exchange tracing enabling/disabling added; File saving dialog adds file extension from the selected file filter; The cube reboot button added; Reboot topic added to the MQTT server; Reboot REST API added to the HTTP server; Reboot method was added to the Python module.
-
Changes to the version 3.19: Configurable preset buttons added on the overview pane. The buttons can be configured to set a selected number of thermostats into desired modes by pressing the button; Popup menu added on the mouse right click.
-
Changes to the version 4.52: Get_Reader_Timeout, Set_Reader_Timeout, Wait_For_Tasks were added to the package GNAT.Sockets.Server.Blocking; JSON parser fixed to accept empty objects {} and empty array []; GNAT.Sockets.Server.OpenSSL bindings were extended; The procedure Next_Unbiased was added to the package Generic_Random_Sequence.
-
Changes to the version 3.27: Procedure Delete was added to the package Gtk.Recent_Manager_Keys.
-
I see. No, I renamed the packages in order to have them conform to the Debian/Ubuntu naming policy. Prior to that the version number was a part of the package name, now it is just "max-home-automation." So the packages can be upgraded from the repository using the standard procedure. Remove the old version (otherwise they will conflict). Also do apt autoremove to remove all older packages it depended on. Then install max-home-automation. Do not worry about settings, they are kept in the user home...
-
Is there a reason why you do not use 3.19 on Raspberry Pi? Time zones were fixed relatively recently, e.g. for older Windows versions. In general any OS, if not updated, has time zone issues because zones are changed all the time. Especially when renamed the software cannot figure out your zone and adjust the cube's clock. For logging, go to the tracing tab and enable tracing into file. You can additionally enable HTTP, MQTT tracing on the settings page. All these, as well as crashes, will show in...
-
Changes to the version 3.18: Ubuntu MQTT server connection error fixed (per GCC 10.0.1 bug work-around).
-
Changes to the version 4.51: Memory leak fixed in the package Generic_Unbounded_Ptr_Array; Bug fix in data selector initialization (in the package GNAT.Sockets.Connection_State_Machine); An exception-free variant of Put was added to the Generic_Indefinite_FIFO package; ModBus TCP/IP implementation bug fix (the package GNAT.Sockets.Connection_State_Machine.MODBUS_Client); Code modified to work around GCC 10.0.1 optimization bug.
-
You are welcome.
-
You do not need to be root in order to build it. Then on a 64-bit target the parameter should rather be -XAtomic_Access=Pragma-atomic Although GCC-long-offsets should work too. [It is about how to deal with 64-bit values atomically. On a 64-bit you can use language primitives, on a 32-bit ones GCC built-ins are used.] If you want to rebuild, use grpclean, or simply delete all ali-flies and o-files. Anyway, that is it. You must have the executable max_home_automation now. Just start it. No special...
-
You still do not have GtkAda. The ads-files marked as missed are parts of the GtkAda developing package. If you think you installed it, search for the file gtkada.gpr. If you have it, you can add the path to the environmental variable GPR_PROJECT_PATH or ADA_PROJECT_PATH to force it. However, if it is not found automatically, it indicates that the installation of GtkAda was incorrect.
-
You need two more dev-packages: for unixODBC (provides libodbc.so) and for GNUTLS (provides libgnutls.so).
-
That is a binary (run-time) package. For compiling code, you need a "dev" package. Something named like libgtkada3.14.15-dev. You can build it from the sources, though. It is relatively straightforward: ./configure, make, make install should go.
-
First you need GtkAda (Ada bindings to GTK). You can download the sources from AdaCore, unless there already is a pre-built development version for your Linux distribution. Note that it must be for GTK 3. There is a lot of old GTK 2 stuff still out there.
-
Actually I considered it already for RPI 3, but never seriously. Where do you get an ARMv7 board with more than 4GB RAM for a resonable price? If you have up to 4GB, there is no gain, but likely some loss. 64-bit applications are larger and could turn slower due to memory access penalties, e.g. when storing/restoring 64-bit pointers and offsets instead of 32-bit ones. (However some other operations might go faster, so it is not settled.) I would go 64-bit at some point, definitely. Presently it is...
-
Changes to the version 3.17: Legacy configuration file loading bug fixed; Time zone handing under Windows 7 fixed to work around its dealing with RTZ (Russian Time Zone).
-
Changes to the version 4.50: The HTTP client behavior changed not to close connection when keep alive flag is set unless the server explicitly requests closing it; Non-standard request headers added to the HTTP implementation: X-Requested-By, X-Requested-With, X-XSRF-TOKEN, X-CSRF-TOKEN; The package IEEE_754.Decimal32 was added. The package implements IEEE 754-2008 decimal32 format; The package IEEE_754.Decimal64 was added. The package implements IEEE 754-2008 decimal64 format; The package IEEE_754.Decimal128...
1 >
