Lose the '/?!' line, and the '000' line, and the 'FF(0000)' line. Next, delete the '*255' part in the lines and replace [space] with a '*' i.e. your resulting message should look like this: /ISk5MT171-0133 0-0:C.1.0(47827401) 1-0:0.0.0(47827401) 1-0:0.2.0(V1.0) 1-0:1.8.0(035745*kWh) 1-0:1.8.1(019928 ...

Was actually looking at that piece of code myself as it appeared that the rest of the error reports were sort of bogus with several other (earlier) parts in the code using the exact same syntax. That array definition seems dodgy, to my knowledge you should not reference the indexes while ...

Looks like your syntax is interpreted as C++ lambda functions. Effectively this means that your syntax is wrong, even though it appears to be acceptable to the Gnu compiler.

I don't think it picks up the parameter that way...

The log line is a bit strange as well because it indicates a missing ID value for which you should have received an earlier error report.

i wouldn't really worry about the Pi breaking. It's the SD card that you run from and where you store your data that you should worry about.

Does the log still produce the same output? Try start Domoticz with debug enabled: `-debug hardware,normal`

vertol wrote: ↑Friday 10 January 2020 16:46 My Domoticz version is 4.11590

Seems like you are already on beta channel. You should simply run update.

Let's also not jump to conclusions until we know what the portal is actually responding.

similar problem https://www.domoticz.com/forum/viewtopic.php?f=34&t=30428&p=230450&hilit=evohome#p230450 Did I understood well it is Domocicz client fault ? It's a combination. The problem originates with the Evohome portal, but depending on your version of Domoticz it is the internal HTTP client ...

To start: Your first location is bound to be [0,0,0]. The documentation is not quite clear on what is possible or should be possible in future, but your second location will likely be addressable as [1,0,0], etc. The errors being logged appear to indicate some other issue though. If you enable debug ...

Sjonnie2017 wrote: ↑Wednesday 08 January 2020 20:28

If it ain't broken don't fix it

True, but what do you have in place to actually be able to fix it in the unexpected case that it does break?

You can't. The data is simply not there. What do you mean? I presume the the usage per Fase/Phase shows up as a device per Fase/Phase within your domoticz currently? No. The only per phase data that the P1 telegram will show you is current/instantaneous use, voltage and ampere, all as integer ...

You can't. The data is simply not there.

Any chance of getting that latest code? Assuming that your signature info is correct, upgrade to 4.xxxx? With respect to the script source code, you might want to notice that I archived the XMPP based project and I actually did that over a year ago as the protocol is officially not supported any ...

I received a PM but I seems to be unable to reply !?? What is going wrong? You're reputation is regarded as too low by the forum software because you are a new member. This is to protect us from being individually spammed by bots. With regard to your IP being blocked, this site is hosted through ...

Well, that's not a big mystery. It means that the rewrite is not processed (correctly) and thus it tries to find the file from the URI within the regular web root. Did you try create the internal vhost as suggested in the #3 example? This could help identify whether the issue is caused by some other ...

Is that a Debian derived system? It's possible that they custom patched the Apache source files to cause a somewhat different behaviour. May also want to double check that you have mod_rewrite included as well, but seeing that long list of proxy (sub)modules that will most likely be the case. One ...

I thought you said it was https?

Anyway, I think you may be missing mod_proxy in your configuration.

Change the http root of domoticz by adding command line option `-webroot domoticz` note: this will cause the Domoticz internal webserver to return an error when you call it without referencing that folder as part of the URI Add the following directive to your Apache ssl host configuration ...

Ah... Yes. If the zone is reported as offline then the until time is not populated and you must specify one when you want to issue a temporary override. In this particular use case the script will indeed fail.

No worries. Note worthy: your scripts should not have experienced issues since all the commands are being sent through the less fine grained interface.