Is anyone having issues with Message Puzzles (Email specifically) after upgrading to 1.1.38?

Alberto Macias shared this question ago

Need Answer

Hello Zipato and Community,

After upgrading to 1.1.38 I have been experiencing weird behaviour on my zipabox, it started with schedulers that uses astro function, then zwave devices that dissapear from network and now email messages that are not sent.

I got help from Zipato regarding schedulers and they adviced me to rebuild the schedulers, so I did and that problem seems to be resolved. Dissapearing devices is under investigation by zipato team but now one specific message is not being sent, I have rebuilt all of them and only this is not working. On this message I have many attributes included on it, don't know if that is the reason why.

Anyone else having this issue??

The same question

Replies (4)

Sven B. ●

Hi, please restart the box...

Reply URL

Alberto Macias ●

This was posted after several syncs, and restarts. I actually noticed due changes on my restart detect rule.

URL

HeroS - www.domotica-blog.nl ●

Are you sure that the sync is working? Use the API to sync.

URL

Alberto Macias ●

I tried with success (the sync), no luck, solution below.

URL

David Pritchard ●

I haven't noticed anything amiss yet.

Reply URL

Alberto Macias ●

Well after waiting for a few days Zipato helped me to resolve the issue. I have been having issues with some devices dissapearing completely from zwave network (separate issue) and also have a message puzzle (email) which sends all my devices status).

While the first issue deleted devices forcing me to rejoin, the message puzzle gets screwed up showing "unknown", this will cause the message puzzle to fail after 1.1.38. On previous firmware versions you got "unknown" but you did get the email.

This is an FYI in case you are deleting devices used on puzzle messages.

Reply URL

David Pritchard ●

Actually it's true that I've seen rules with all their devices marked "unknown", but that's not new to 1.1.38 - it's happened to me before. If I reload the problem tends to go away.

Reply URL

Alberto Macias ●

I don't mean on the rule editor. When you open a message puzzle, if you added an attribute of a device that has been deleted or reincluded, this attribute showed as "unknown" in the body of the message puzzle, when this message was triggered you did get a message, but you used to get a "unknown" as the attribute value. Now, if you have this same situation, message puzzle won't work at all.

URL