Domoticz

As said above, mine is still running, and i do not expect the problem to be with domoticz, rather in the thermostat itself as you have seen yourself now (mobile application was also not responding)
It is quite a difference for the thermostat, being 'polled' once in a very long while by a mobile application, or every 5 to 10 minutes
.. not drawing conclusions here

gizmocuz wrote:I dont, but i would think it will disappear in 10 seconds after you refresh.... if something goes wrong
For example (on your desktop), open the domoticz web gui, goto settings, set your dashboard style to 'mobile'
Refresh the dashboard
But here (version #5139+) no problem
The 'Ingestelde temperature' thats the setpoint device correct?

Yes it is the setpoint value. Just tried in chrome on my desktop, also here the button disappears indeed after about 10 seconds. Yesterday my nefit HTTP stopped to provide values (crashed I think) and during the non providing of values the button remained. So I think it has got to do with indeed an update of the value and in that case the removal of the button.

Any suggestions what I can check?

Marcel wrote:Hi, does anyone else have the issue that the button (ingestelde temperatuur) disappears after a couple of seconds on the favourite pages?

Yes, I have exactly the same issue, for already quite a while (always use the latest beta). I'm using the Opentherm Gateway to communicate with my Remeha Calenta.

is this also with the chrome browser ? (on a desktop, setting the dashboard to 'mobile' type?
Please provide me some steps (maybe creating virtual sensor) to replicate?

I've set my Domoticz to "mobile" type and in Safari on my Macbook Pro the same thing happens. Same happens in Google Chrome after the Browser Cache refresh and also in Firefox. All browsers are updated to the latest versions.

By the way: my Nefit is online again. Didn't do anything from here

Edit: except.....opening the Nefit app. But I don't think that will reset anything.

Same issue here, it occurs just after an update from the Nefit easy server/hardware was received


Verzonden vanaf mijn iPhone met Tapatalk

gizmocuz wrote:is this also with the chrome browser ? (on a desktop, setting the dashboard to 'mobile' type?
Please provide me some steps (maybe creating virtual sensor) to replicate?

It happens in all browsers that I use: mobile Safari (iOS), Chrome and Edge.
Wouldn't know how to replicate it. I assume both the Nefit and the OTGW plugin create a virtual thermostat that they update whenever a message comes in from the hardware. After the first update while on the mobile dashboard page, the code for displaying the UI seems to get confused for some reason, and it changes the type of the UI element to just a text rather than an action button.
If that's the case, it should probably happen with any thermostat on the dashboard that's updated from outside (rather than those that are only used as a UI element to set a temperature for some self-written code).

gizmocuz wrote:is this also with the chrome browser ? (on a desktop, setting the dashboard to 'mobile' type?
Please provide me some steps (maybe creating virtual sensor) to replicate?

Yes, used Ubuntu 14.04, latest domoticz (beta) and chrome on desktop. Just select mobile dashboard and refresh the browser, button appears,
wait 10 sec and button dissappears.

Hi All,

I am a newbe and exploring domoticz in comination with a Raspberry Pi 3.
Domoticz is running smoothly together with a RFXtrx433E but now I want to intergrate my Nefit Easy by following this forum but it is not that easy.
Can someone give me some good hints, I can install nefit easy http server but after this I get lost.

mvveelen wrote:True, but when I receive a notification by email or Prowl that there is no data received from the easy httpd server, that would be great. That way I would know to take the display off the wall for a few seconds to reset it. Is this something you could build into Domoticz you think?

@Gizmocuz: any chance you're going to make some warning / trigger for it? Been trying to get some warnings outside of Domoticz, but then I have to grep the logfile and I don't want a message when 1 or 2 log entries tell me that there wasn't any data received. It would be nice if I receive a message when there hasn't been a reading in the last 30 minutes or so. Or do I have to send in a request ?

Today it happened again, Nefit app stopped working, Error: NefitEasy: Request Timeout ! in domoticz and easy status also shows [Error: REQUEST_TIMEOUT], so something must be wrong with the Nefit backend at Bosch. After reset of the Easy connect adapter everything works again.

Same here. Since 18:43 today it stopped. Going to reseat the thermostat again.....

Yesterday I received a few messages about the Nefit not reporting data for a short while. I use this lua script:
It should report only within 600 seconds after the last update and 700 seconds after the last update. This works for me.
Next step is to make a relais which turns off the power of the thermostat for a few seconds to get the updates working again.
If someone can use this, be my guest. If someone could make updates to the script: even better

I did it a bit simpler.. Just have set a timer that switches off at 3.00 and back on at 3.01 I never noticed an outage within 24 hour after the reset so for now this will be fine.

What does it exactly switch off then? Do you have a relais for your Nefit Easy or something?

I had this 'problem' within 24 hours by the way. Most of the time it works for days (sometimes weeks) in a row, but last week I had 3 'stops'. I haven't had any time to put a relais to the Easy or a switch for the whole Nefit unit, so at the moment it only works as a notification

I don't think it's a Domoticz issue. Mine is running for weeks/months without any issue. Occasionally I get a malformed answer or a request time out, but that's no issue and works as designed.


Verzonden vanaf mijn iPhone met Tapatalk

I also don't think it's a Domoticz issue. The connection sometimes gets lost and normally you won't notice that. But with Domoticz, you see gaps in the logging and with this script you get notified of those (short) interruptions. So I'm not pointing fingers, I only try to suggest a solution for when you want continues logging / connection with the Bosch server

It's not about pointing fingers, it's about solving the issue on the right place
Did someone made contact Robert about these issues? The communication between the easy and Bosch servers has been reverse engineered so any additional info might give some very valuable information.


Verzonden vanaf mijn iPhone met Tapatalk

Even way before I used Domoticz, the Nefit app sometimes could not connect. Waiting some time always fixed it, as it does now.

jannl wrote:Even way before I used Domoticz, the Nefit app sometimes could not connect. Waiting some time always fixed it, as it does now.

That's what I said . Most users don't even notice it, but after using it with Domoticz, you are more aware of the rare disconnects. The solution are: waiting OR disconnecting and reconnecting the thermostat.