Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
  1. Home
  2. Software
  3. Multi-System Reactor
  4. Host time is wrong
Requesting a proper ARM64/aarch64 Docker image (Pi 5 support)
M
Hi, I'm in the process of migrating from a Raspberry Pi 4 (ARMv7) to a Raspberry Pi 5 (ARMv8/aarch64), but I’ve run into an issue: there is no proper ARMv8/aarch64 image available. None of the existing images run on the Pi 5 - they all exit immediately with code 139 (segmentation fault), which typically indicates that the binaries inside the image are not compatible with the ARM64/aarch64 architecture used by the Pi 5. Would it be possible to publish a correct ARMv8/aarch64 (linux/arm64) image? Building one should be relatively straightforward using docker buildx with multi-arch support. For example, my own Node.js images are built this way: docker buildx build --push \ -t <localrepo>/<project>:<tag> \ --platform=linux/arm64,linux/amd64 \ --file ./apps/<project>/Dockerfile . This produces both the AMD64 and ARM64/v8 variants automatically. Also, as a side note, it may be best to avoid using Alpine as the base image for the ARM64 build, since musl-based builds often cause compatibility issues and unnecessary headaches. A glibc-based base image (e.g., Debian or Ubuntu) tends to work far more reliably on ARM64, especially for Node.js applications. @toggledbits - tagging you in case you missed this. Thanks, mgvra
Multi-System Reactor
Script action and custom timers
therealdbT
Sorry to write here without trying, but I’m flying today. Am I correct if i say that script action with alarm() makes it possible to execute a reaction in a given interval, lets say 15 seconds or 3.5 minutes? That sounds amazing, since I’ve used weird tricks, including a custom controller, just to do this.
Multi-System Reactor
Help resolve change in behaviour post update
CatmanV2C
Topic thumbnail image
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here. Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
Reactor w/HA 2025.11 error on set_datetime service call setting only time
CrilleC
@toggledbits Do you know if this is related to that PR or is it a change they made in 2025.11.1? [latest-25310]2025-11-11T13:16:24.319Z <HassController:INFO> HassController#hass perform x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_dag with { "time": "10:45" } [latest-25310]2025-11-11T13:16:24.320Z <HassController:INFO> HassController#hass: sending payload for x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_dag action: { "type": "call_service", "service_data": { "date": (null), "time": "10:45", "datetime": (null), "timestamp": (null) }, "domain": "input_datetime", "service": "set_datetime", "target": { "entity_id": "input_datetime.vvb_dag" } } [latest-25310]2025-11-11T13:16:24.321Z <HassController:ERR> HassController#hass request 1762866984320<2025-11-11 14:16:24> (call_service) failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.321Z <HassController:WARN> HassController#hass action x_hass_input_datetime.set_datetime({ "time": "10:45" }) on Entity#hass>input_datetime_vvb_dag failed! [latest-25310]2025-11-11T13:16:24.321Z <HassController:INFO> Service call payload: {"type":"call_service","service_data":{"date":null,"time":"10:45","datetime":null,"timestamp":null},"domain":"input_datetime","service":"set_datetime","target":{"entity_id":"input_datetime.vvb_dag"},"id":1762866984320} [latest-25310]2025-11-11T13:16:24.322Z <HassController:INFO> Service data: {"fields":{"date":{"example":"\"2019-04-20\"","selector":{"text":{"multiline":false,"multiple":false}}},"time":{"example":"\"05:04:20\"","selector":{"time":{}}},"datetime":{"example":"\"2019-04-20 05:04:20\"","selector":{"text":{"multiline":false,"multiple":false}}},"timestamp":{"selector":{"number":{"min":0,"max":9223372036854776000,"mode":"box","step":1}}}},"target":{"entity":[{"domain":["input_datetime"]}]}} [latest-25310]2025-11-11T13:16:24.322Z <Engine:ERR> Engine#1 reaction rule-mgb8pfhs:S step 0 perform x_hass_input_datetime.set_datetime failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.322Z <Engine:INFO> Engine#1 action args: { "time": "10:45" } [latest-25310]2025-11-11T13:16:24.322Z <Engine:INFO> Resuming reaction Sätt Schema VVB i Home Assistant<AKTIV> (rule-mgb8pfhs:S) from step 1 [latest-25310]2025-11-11T13:16:24.323Z <HassController:INFO> HassController#hass perform x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_natt with { "time": "03:00", "timestamp": 0 } [latest-25310]2025-11-11T13:16:24.323Z <HassController:INFO> HassController#hass: sending payload for x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_natt action: { "type": "call_service", "service_data": { "date": (null), "time": "03:00", "datetime": (null), "timestamp": 0 }, "domain": "input_datetime", "service": "set_datetime", "target": { "entity_id": "input_datetime.vvb_natt" } } [latest-25310]2025-11-11T13:16:24.324Z <HassController:ERR> HassController#hass request 1762866984323<2025-11-11 14:16:24> (call_service) failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.324Z <HassController:WARN> HassController#hass action x_hass_input_datetime.set_datetime({ "time": "03:00", "timestamp": 0 }) on Entity#hass>input_datetime_vvb_natt failed! [latest-25310]2025-11-11T13:16:24.324Z <HassController:INFO> Service call payload: {"type":"call_service","service_data":{"date":null,"time":"03:00","datetime":null,"timestamp":0},"domain":"input_datetime","service":"set_datetime","target":{"entity_id":"input_datetime.vvb_natt"},"id":1762866984323} [latest-25310]2025-11-11T13:16:24.324Z <HassController:INFO> Service data: {"fields":{"date":{"example":"\"2019-04-20\"","selector":{"text":{"multiline":false,"multiple":false}}},"time":{"example":"\"05:04:20\"","selector":{"time":{}}},"datetime":{"example":"\"2019-04-20 05:04:20\"","selector":{"text":{"multiline":false,"multiple":false}}},"timestamp":{"selector":{"number":{"min":0,"max":9223372036854776000,"mode":"box","step":1}}}},"target":{"entity":[{"domain":["input_datetime"]}]}} [latest-25310]2025-11-11T13:16:24.324Z <Engine:ERR> Engine#1 reaction rule-mgb8pfhs:S step 1 perform x_hass_input_datetime.set_datetime failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.324Z <Engine:INFO> Engine#1 action args: { "time": "03:00", "timestamp": 0 } [latest-25310]2025-11-11T13:16:24.325Z <Engine:INFO> Resuming reaction Sätt Schema VVB i Home Assistant<AKTIV> (rule-mgb8pfhs:S) from step 2 [latest-25310]2025-11-11T13:16:24.325Z <Engine:INFO> Sätt Schema VVB i Home Assistant<AKTIV> all actions completed.
Multi-System Reactor
Reactor Version 25310 : Office Light control via rule in reactor no longer working since last update.
P
Hello, I currently have an office light (connected via a Leviton Zwave Dimmer switch) controlled from a Gen5 Aeotech Zwave switch installed on my Synology 720+ NAS. I run HA(2025.11.10) in a virtual machine from my NAS and Reactor on the container manager of the same NAS. Prior to updating to 25304 the rule I had set to turn the light on to a specific dimming value worked correctly. Now the rule appears to follow the decision tree, however the reaction does not trigger setting the dimming or turning on the office light? Strangely I can still turn the light on and off as well as dim it directly from HASS..? I have tried using the ''try this action'' button in the rules reaction setting and it will not control the light and does not throw an error flagÉ Please help, P.S Reactor has been rock steady for me over the last few years and I'm a big fan of this solution.
Multi-System Reactor
[Solved] alarm() in global expression throws error in log.
CrilleC
Topic thumbnail image
Multi-System Reactor
[Solved] Define function issue in latest-25304
CrilleC
Topic thumbnail image
Multi-System Reactor
No Upgrade Notification for Build 25308?
CatmanV2C
FWIW I'm no longer getting a notification from MSR that there's an update. Just thought I'd mention it C
Multi-System Reactor
Strange behavior in MSR latest-25304 with disabled groups in Reaction
therealdbT
Topic thumbnail image
Multi-System Reactor
[Reactor] Variables not updating correctly in latest-25201-2aa18550
therealdbT
Topic thumbnail image
Multi-System Reactor
The reaction stopped working (Google Nest max playing a video)
F
Topic thumbnail image
Multi-System Reactor
Handling Dead Entities and Renamed Entities
PablaP
Hello all.. been a minute! I recently rebuilt my Z wave network and migrated to a new z wave stick. In order to prevent any downtime I kept my original z wave network up and ran a docker version of Z Wave JS UI with my new controller. This way I could add device by device without having any devices down. I finally moved all the devices over to my new stick today. The final step was to migrate everything from my Docker instance of Z Wave JS UI to the HA add-on of Z Wave JS UI. However during this migration some of the names didn't populate correctly which I later managed to import back into Z Wave JS UI. The issue was in Reactor it is stuck on the default names and the entities are not updating. I removed the controller from Reactor, restarted, hard refreshed, and added the controller back however the new entity names have not updated. Also it seems like the old entities from my previous instance of Z Wave JS UI are lingering and not being marked as dead (I believe a certain amount of time needs to lapse before they're marked as dead in Reactor). My goal is to basically purge all the entities for the 'ZWaveJS' controller in Reactor so it can pull all the updated entity names and only the entities that exist in Z Wave JS UI. I cannot find a quick way to do this, I know entities can be deleted one by one, but with over 100 entities this would take long I am guessing that if I added the controller with a new name in in the Reactor config it would pull the updated entities and names but I think that would break my rules since the entity IDs would change (I made sure to name all the entities the exact same as they were previously to prevent this issue).
Multi-System Reactor
Strange behavior for MQTT templates using payload and attributes
therealdbT
Topic thumbnail image
Multi-System Reactor
[MSR] reactor-mqtt-contrib package for additional MQTT templates
therealdbT
I'm slowly migrating all my stuff to MQTT under MSR, so I have a central place to integrate everything (and, in a not-so-distant future, to remove virtual devices from my Vera and leave it running zwave only). Anyway, here's my reactor-mqtt-contrib package: https://github.com/dbochicchio/reactor-mqtt-contrib Simply download yaml files (everything or just the ones you need) and you're good to go. I have mapped my most useful devices, but I'll add others soon. Feel free to ask for specific templates, since I've worked a lot in the last weeks to understand and operate them. The templates are supporting both init and query, so you have always up-to-date devices at startup, and the ability to poll them. Online status is supported as well, so you can get disconnected devices with a simple expression. Many-many thanks to @toggledbits for its dedication, support, and patience with me and my requests
Multi-System Reactor
HA 2025.9.4 Supported Yet?
CatmanV2C
Tangentially did I miss 2025.9.4 getting blessed in MSR? I've been holding off Cheers C
Multi-System Reactor
Rule Set UI bug - RESOLVED
3
Topic thumbnail image
Multi-System Reactor
[Reactor] Copy&Paste of Rules
therealdbT
I don't know if I'm the only one, but managing more than one Reactor installs, the need to have some sort of copy&paste for rules has grown on me. While I understand the technical challenges, I'm wondering if a "god mode" where I could copy the raw JSON rule and paste it into another rule could be an advanced, flag only feature that could benefit power users. I know I can copy the JSON file and proceed, but I must stop Reactor and when doing maintenance, it's more clicks to do. Just an idea
Multi-System Reactor
[Reactor] Help with scene controller cycling logic
therealdbT
I’ve added a couple of Shelly Wave i4 as scene controllers and I’m planning to add more, since I can just use standard buttons instead of battery-powered scene controllers, which also looks better aesthetically. That said, I’m struggling to figure out how to write a simple rule that cycles between states every time I press a button. Example: Light 1 ON → OFF, then Light 2 ON → OFF. The part I can’t get right is handling the case where Light 1 or Light 2 might already be ON independently of the rule. Maybe it’s just too much sun and relaxation clouding my brain, but any hint would be appreciated.
Multi-System Reactor
Stop the MSR by an external switch on Hubitat.
wmarcolinW
Use case: When performing home maintenance, such as air conditioning, I want all rules involving air conditioning to be disabled. To do this, to day, I have a virtual switch that I placed within all rules involving air conditioning, meaning that if I turn it off, none of them work. Then another situation: the water pump system and garden irrigation, another switch. In short, I had to create several virtual switches in Hubitat to disable rules in MSR. Unfortunately, however, I was unable to cover all scenarios, so I wondered if it would be possible for MSR to support a virtual MSR switch, which, when configured in the reactor settings, would function as a general on/off switch for MSR. If it is configured and turned off, the entire rules and actions in MSR stops working, except for the status change reading process, specifically for this switch, which, when turned on, would restart the MSR. Would it be possible to do something like this? Any recommendations from the experts?
Multi-System Reactor

Host time is wrong

Scheduled Pinned Locked Moved Multi-System Reactor
14 Posts 3 Posters 1.6k Views 3 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • wmarcolinW Offline
    wmarcolinW Offline
    wmarcolin
    wrote on last edited by
    #1

    @toggledbits

    After a prolonged power cut, the UPS was unable to cope with the weather and shut down the entire system.

    When I returned, I had the problem that the host time displayed in the browser and automatically used in the rules was not correct.

    I searched for a topic here on this forum that talked about it, but it referred to a container installation. There was a recommendation to go into the storage/states directory and delete the files and restart MSR, I did it and it didn't solve the problem.

    There was also a recommendation to go directly to the browser to check the time, and I did so and I see that the time is correct.

    8ad429c8-ea5f-45b4-8670-7d0353a50a0e-image.png

    As you can see on the screen above:

    • MSR browser shows the correct browser time 21:23, but host time 13:02;
    • In the browser below the direct query and the host time is correct 9:22:54 PM;
    • Setting the VM date command on the third screen, the time is 9:23:00 PM.

    I've opened the entire reactor.log file and searched for any errors, and there aren't any.

    ^L
    [latest-23242]2023-09-15T02:11:12.928Z <app:null> Reactor build latest-23242-5ee8e1d4 starting on v18.12.0
    [latest-23242]2023-09-15T02:11:12.929Z <app:null> Process ID 1807 user/group 1000/1000; bare-metal; platform linux/x64 #179-Ubuntu SMP Mo>
    [latest-23242]2023-09-15T02:11:12.929Z <app:null> Basedir /home/leonardo/reactor; data in /home/leonardo/reactor/storage
    [latest-23242]2023-09-15T02:11:12.929Z <app:null> NODE_PATH=/home/leonardo/reactor
    [latest-23242]2023-09-15T02:11:12.933Z <app:INFO> Configured locale (undefined); selected locale(s) en_US.UTF-8
    [latest-23242]2023-09-15T02:11:12.955Z <app:INFO> Loaded locale en-US for en-US
    [latest-23242]2023-09-15T02:11:12.958Z <Structure:null> Module Structure v23172
    [latest-23242]2023-09-15T02:11:12.959Z <Capabilities:null> Module Capabilities v22356
    [latest-23242]2023-09-15T02:11:12.969Z <Capabilities:NOTICE> System capabilities loaded from core distribution, data version 23914 revisi>
    [latest-23242]2023-09-15T02:11:12.978Z <Plugin:null> Module Plugin v22300
    [latest-23242]2023-09-15T02:11:12.981Z <TimerBroker:null> Module TimerBroker v22283
    [latest-23242]2023-09-15T02:11:12.983Z <Entity:null> Module Entity v22353
    [latest-23242]2023-09-15T02:11:12.986Z <Controller:null> Module Controller v23069
    [latest-23242]2023-09-15T02:11:12.992Z <default:null> Module Ruleset v22293
    [latest-23242]2023-09-15T02:11:12.992Z <default:null> Module Rulesets v22146
    [latest-23242]2023-09-15T02:11:12.996Z <GlobalExpression:null> Module GlobalExpression v23211
    [latest-23242]2023-09-15T02:11:13.003Z <Predicate:null> Module Predicate v23093
    [latest-23242]2023-09-15T02:11:13.005Z <AlertManager:null> Module AlertManager v22283
    [latest-23242]2023-09-15T02:11:13.007Z <Rule:null> Module Rule v23107
    [latest-23242]2023-09-15T02:11:13.009Z <GlobalReaction:null> Module GlobalReaction v22324
    [latest-23242]2023-09-15T02:11:13.010Z <Engine:null> Module Engine v23231
    [latest-23242]2023-09-15T02:11:13.012Z <httpapi:null> Module httpapi v23058
    [latest-23242]2023-09-15T02:11:13.019Z <wsapi:null> Module wsapi v23172
    [latest-23242]2023-09-15T02:11:13.019Z <app:NOTICE> Starting Structure...
    
    

    As you can see, the time in the log is 02:11, which is correct, because I'm in time zone -5, which means it's 09:11PM for me.

    I've restarted the VM, the computer hosting the VM, and the MSR a few times and the same difference remains. What do you recommend for the next step in understanding and solving the problem?

    Thanks.

    1 Reply Last reply
    0
    • wmarcolinW Offline
      wmarcolinW Offline
      wmarcolin
      wrote on last edited by
      #2

      Hi @toggledbits , any recommendations on how to align the two schedules? Thanks!

      1 Reply Last reply
      0
      • toggledbitsT Offline
        toggledbitsT Offline
        toggledbits
        wrote on last edited by
        #3

        No idea. I assume you hard-reloaded the browser? Is the TZ being set for some reason in your service configuration file?

        Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

        wmarcolinW 2 Replies Last reply
        0
        • toggledbitsT toggledbits

          No idea. I assume you hard-reloaded the browser? Is the TZ being set for some reason in your service configuration file?

          wmarcolinW Offline
          wmarcolinW Offline
          wmarcolin
          wrote on last edited by
          #4

          @toggledbits

          It really is rare.

          I haven't changed anything in the TZ configuration I had before, I compared the two installations I have in different environments, and they are identical. The rules even operate at the correct time. I've downloaded and restarted the VM, the computer, I've cleared the cash from the browser, and I'm still seeing this strange time.

          😞

          1 Reply Last reply
          0
          • toggledbitsT toggledbits

            No idea. I assume you hard-reloaded the browser? Is the TZ being set for some reason in your service configuration file?

            wmarcolinW Offline
            wmarcolinW Offline
            wmarcolin
            wrote on last edited by
            #5

            @toggledbits

            The strangest thing is that if I use the command

            http://192.168.50.8:8111/diag/sun
            

            shows the correct host time.

            Look at this screen to see the difference of 55 minutes, but note that the rules have the correct time.

            417ad15c-3e3c-4175-9a72-399248cf7a2e-image.png

            Thanks.

            1 Reply Last reply
            0
            • toggledbitsT Offline
              toggledbitsT Offline
              toggledbits
              wrote on last edited by
              #6

              So what's the odd wrapper around the browser?

              Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

              wmarcolinW 1 Reply Last reply
              0
              • toggledbitsT toggledbits

                So what's the odd wrapper around the browser?

                wmarcolinW Offline
                wmarcolinW Offline
                wmarcolin
                wrote on last edited by
                #7

                @toggledbits said in Host time is wrong:

                So what's the odd wrapper around the browser?

                The time difference that indicates that you have the browser, and the time that indicates the host.

                32a5b0ae-2161-4da6-a218-0267d836cd1b-image.png

                All the queries in the VM, on my computer that opens the browse, using the diag/sun query have a different time to the one that MSR points to as the host time.

                Thanks.

                1 Reply Last reply
                0
                • toggledbitsT Offline
                  toggledbitsT Offline
                  toggledbits
                  wrote on last edited by
                  #8

                  Not what I'm asking. Are you using some kind of remote access gateway?

                  Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                  G 1 Reply Last reply
                  0
                  • toggledbitsT toggledbits

                    Not what I'm asking. Are you using some kind of remote access gateway?

                    G Offline
                    G Offline
                    gwp1
                    wrote on last edited by
                    #9

                    @toggledbits Appears OP is using AnyDesk, a remote desktop application like Teamviewer, VNC, etc.

                    *Hubitat C-7 2.4.3.149
                    *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                    *HASS 2025.11.1
                    w/ ZST10-700 fw 7.18.3

                    *Prod MSR in docker/portainer
                    MSR: latest-25310-dc2bb580
                    MQTTController: 25139
                    ZWave Controller: 25139

                    toggledbitsT 1 Reply Last reply
                    0
                    • G gwp1

                      @toggledbits Appears OP is using AnyDesk, a remote desktop application like Teamviewer, VNC, etc.

                      toggledbitsT Offline
                      toggledbitsT Offline
                      toggledbits
                      wrote on last edited by toggledbits
                      #10

                      @gwp1 So it seems.

                      And if that's the case, then there are THREE computers involved here: the host/server on which MSR is running, the host on which the browser to running (i.e. the remote target of the AnyDesk connection), and the computer on which the AnyDesk client is being run.

                      I would venture to guess that the date/time is incorrect on the remote target (the system AnyDesk is connecting to, actually running the browser). I'm guessing the time displayed in the lower right corner is the time of the AnyDesk client machine, not the remote browser/host, and the client's time is irrelevant here. The browser is actually running on a remote target system, and it's the time on that remote target system that's in question here.

                      Beyond that, my suggestion is to connect to MSR locally from a local browser/computer, not using AnyDesk. But in all, this doesn't seem like an MSR issue, it seems like a (one of the many) host configuration issue.

                      Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                      G wmarcolinW 2 Replies Last reply
                      0
                      • toggledbitsT toggledbits

                        @gwp1 So it seems.

                        And if that's the case, then there are THREE computers involved here: the host/server on which MSR is running, the host on which the browser to running (i.e. the remote target of the AnyDesk connection), and the computer on which the AnyDesk client is being run.

                        I would venture to guess that the date/time is incorrect on the remote target (the system AnyDesk is connecting to, actually running the browser). I'm guessing the time displayed in the lower right corner is the time of the AnyDesk client machine, not the remote browser/host, and the client's time is irrelevant here. The browser is actually running on a remote target system, and it's the time on that remote target system that's in question here.

                        Beyond that, my suggestion is to connect to MSR locally from a local browser/computer, not using AnyDesk. But in all, this doesn't seem like an MSR issue, it seems like a (one of the many) host configuration issue.

                        G Offline
                        G Offline
                        gwp1
                        wrote on last edited by
                        #11

                        @wmarcolin see above response.

                        *Hubitat C-7 2.4.3.149
                        *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                        *HASS 2025.11.1
                        w/ ZST10-700 fw 7.18.3

                        *Prod MSR in docker/portainer
                        MSR: latest-25310-dc2bb580
                        MQTTController: 25139
                        ZWave Controller: 25139

                        1 Reply Last reply
                        0
                        • toggledbitsT toggledbits

                          @gwp1 So it seems.

                          And if that's the case, then there are THREE computers involved here: the host/server on which MSR is running, the host on which the browser to running (i.e. the remote target of the AnyDesk connection), and the computer on which the AnyDesk client is being run.

                          I would venture to guess that the date/time is incorrect on the remote target (the system AnyDesk is connecting to, actually running the browser). I'm guessing the time displayed in the lower right corner is the time of the AnyDesk client machine, not the remote browser/host, and the client's time is irrelevant here. The browser is actually running on a remote target system, and it's the time on that remote target system that's in question here.

                          Beyond that, my suggestion is to connect to MSR locally from a local browser/computer, not using AnyDesk. But in all, this doesn't seem like an MSR issue, it seems like a (one of the many) host configuration issue.

                          wmarcolinW Offline
                          wmarcolinW Offline
                          wmarcolin
                          wrote on last edited by
                          #12

                          @toggledbits

                          Hi, let's to align.

                          In my house, where everything works normally, or in my neighbor's house, which worked normally until two weeks ago, we have a separate computer, on which a Linux VM is mounted, where MSR is installed. This local computer is where I open the browser and we see in my friend's case the time difference from the host.

                          For ease of work, I have the AnyDesk application installed on the VM machine and on the computer I use to access it (not by browser), i.e. this application only opens a remote operating terminal, it would not be influencing this situation.

                          Anyway, I'm going to ask my friend to open MSR in browse at home and send me a picture of the screen, so we can resolve this doubt.

                          Thanks.

                          G 1 Reply Last reply
                          0
                          • wmarcolinW wmarcolin

                            @toggledbits

                            Hi, let's to align.

                            In my house, where everything works normally, or in my neighbor's house, which worked normally until two weeks ago, we have a separate computer, on which a Linux VM is mounted, where MSR is installed. This local computer is where I open the browser and we see in my friend's case the time difference from the host.

                            For ease of work, I have the AnyDesk application installed on the VM machine and on the computer I use to access it (not by browser), i.e. this application only opens a remote operating terminal, it would not be influencing this situation.

                            Anyway, I'm going to ask my friend to open MSR in browse at home and send me a picture of the screen, so we can resolve this doubt.

                            Thanks.

                            G Offline
                            G Offline
                            gwp1
                            wrote on last edited by
                            #13

                            @wmarcolin Have you checked that the host machine for MSR is properly syncing the date/time? This would not be MSR's job but the OS itself.

                            *Hubitat C-7 2.4.3.149
                            *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                            *HASS 2025.11.1
                            w/ ZST10-700 fw 7.18.3

                            *Prod MSR in docker/portainer
                            MSR: latest-25310-dc2bb580
                            MQTTController: 25139
                            ZWave Controller: 25139

                            1 Reply Last reply
                            0
                            • wmarcolinW Offline
                              wmarcolinW Offline
                              wmarcolin
                              wrote on last edited by
                              #14

                              Screen shot simultaneo:

                              screenLeo.png

                              1 Reply Last reply
                              0
                              • toggledbitsT toggledbits locked this topic on
                              Reply
                              • Reply as topic
                              Log in to reply
                              • Oldest to Newest
                              • Newest to Oldest
                              • Most Votes


                              Recent Topics

                              • Requesting a proper ARM64/aarch64 Docker image (Pi 5 support)
                                M
                                mgvra
                                1
                                3
                                65

                              • Script action and custom timers
                                toggledbitsT
                                toggledbits
                                0
                                4
                                85

                              • Help resolve change in behaviour post update
                                CatmanV2C
                                CatmanV2
                                0
                                12
                                239

                              • Reactor (Multi-System/Multi-Hub) Announcements
                                CatmanV2C
                                CatmanV2
                                5
                                128
                                72.9k

                              • There is an alternative to homebridge-mqttthing
                                akbooerA
                                akbooer
                                1
                                2
                                87

                              • Reactor w/HA 2025.11 error on set_datetime service call setting only time
                                CrilleC
                                Crille
                                0
                                6
                                88

                              • Reactor Version 25310 : Office Light control via rule in reactor no longer working since last update.
                                toggledbitsT
                                toggledbits
                                0
                                17
                                305

                              • Shelly Wall Display XL
                                akbooerA
                                akbooer
                                2
                                9
                                698

                              • [Solved] alarm() in global expression throws error in log.
                                toggledbitsT
                                toggledbits
                                0
                                26
                                533

                              • [Solved] Define function issue in latest-25304
                                CrilleC
                                Crille
                                0
                                12
                                382

                              • No Upgrade Notification for Build 25308?
                                toggledbitsT
                                toggledbits
                                0
                                2
                                89

                              • Strange behavior in MSR latest-25304 with disabled groups in Reaction
                                toggledbitsT
                                toggledbits
                                0
                                2
                                129
                              Powered by NodeBB | Contributors
                              Hosted freely by 10RUPTiV - Solutions Technologiques | Contact us
                              • Login

                              • Don't have an account? Register

                              • Login or register to search.
                              • First post
                                Last post
                              0
                              • Categories
                              • Recent
                              • Tags
                              • Popular
                              • Unsolved